-
Notifications
You must be signed in to change notification settings - Fork 13
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
ROX-19811: Set label selector to dogfooding secured cluster CR #1308
ROX-19811: Set label selector to dogfooding secured cluster CR #1308
Conversation
@@ -3,6 +3,8 @@ kind: SecuredCluster | |||
metadata: | |||
name: stackrox-secured-cluster-services | |||
namespace: {{ include "secured-cluster.namespace" . }} | |||
labels: | |||
rhacs.redhat.com/selector: dogfooding |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a comment specifying what this is for? So that other engs are aware etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, just minor about adding a comment on the label in the template
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kurlov, ludydoo, SimonBaeumer 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 |
New changes are detected. LGTM label has been removed. |
Description
Set label selector value to Dogfooding secured cluster CR. It's necessary to specify which operator should reconcile the instance
Checklist (Definition of Done)
- [ ] Unit and integration tests added- [ ] Added test description underTest manual
- [ ] Documentation added if necessary (i.e. changes to dev setup, test execution, ...)ROX-12345: ...
- [ ] Discussed security and business related topics privately. Will move any security and business related topics that arise to private communication channel.- [ ] Add secret to app-interface Vault or Secrets Manager if necessary- [ ] RDS changes were e2e tested manually- [ ] Check AWS limits are reasonable for changes provisioning new resourcesTest manual
N/A