Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Set namespace for Cincinnati manifests #63

Merged
merged 1 commit into from
Sep 15, 2020

Conversation

wking
Copy link
Member

@wking wking commented Sep 14, 2020

Or in the oc -n ... create ... call that pushes them into the cluster. And also use the NAMESPACE variable when looking up the policy engine's route.

We could add an environment variable for the Cincinnati manifest's name, but I think example-name, which I'm pivoting to, is clear enough in pattern-matching that we don't need a formal environment variable.

Or in the 'oc -n ... create ...' call that pushes them into the
cluster.  And also use the NAMESPACE variable when looking up the
policy engine's route.

We could add an environment variable for the Cincinnati manifest's
name, but I think 'example-name', which I'm pivoting to, is clear
enough in pattern-matching that we don't need a formal environment
variable.
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 14, 2020
@openshift-merge-robot openshift-merge-robot merged commit 86d8de1 into openshift:master Sep 15, 2020
@wking wking deleted the example-namespace branch September 16, 2020 00:22
PratikMahajan pushed a commit to PratikMahajan/cincinnati-operator that referenced this pull request Mar 17, 2021
channels: Explain the lack of 4.2.3, 4.2.5, and 4.2.6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants