-
Notifications
You must be signed in to change notification settings - Fork 8
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
Set Suggested Namespace #114
Conversation
The suggested namespace is used to resolve a confusion of installing the operator from console or CLI. On console it uses openshift-operators which is common to other operators, and in CLI docs every operator is installed in its owns namespace
New annotation that will be used in order to make sure 'openshift.io/node-selector' annotation is set on the namespace.
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: razo7 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 |
/test 4.14-openshift-e2e |
1 similar comment
/test 4.14-openshift-e2e |
/lgtm |
/test 4.14-openshift-e2e |
The suggested namespace is used to resolve the confusion of installing the operator from the console vs CLI.
We use two new OCP annotations for this matter and to make sure that
"openshift.io/node-selector":""
annotation is set on the installed namespace.Similar to medik8s/self-node-remediation#165, medik8s/self-node-remediation#168, medik8s/node-maintenance-operator#107 and related to ECOPROJECT-1777