-
Notifications
You must be signed in to change notification settings - Fork 190
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
add: specific selector for operator #390
Conversation
Hi @codekow. Thanks for your PR. I'm waiting for a aws-controllers-k8s member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Addresses aws-controllers-k8s/community#1632 |
See https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels Considering above, I have updated the minimal labels to get basic selection functionality without removing any existing labels. |
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.
One tiny request otherwise I dig it. :)
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.
Also, one other thing, @codekow: we have corresponding Helm templates in templates/helm
too.
I'd like to see the The below will generate a file at
I don't think we have any |
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.
👍
Checking
|
FYI @acornett21 ^^ |
Do we want to leave the label: |
We don't need to, no. I put that on there originally when I copied some stuff from the node-termination-handler project. I think that label is no longer used by anything. |
I pretty sure no project that's dependent on ACK in OpenShift uses this label, so I'm fine removing it as well. |
Old label removed. I believe the merge is ready. Let me know if there is anything else to resolve with this PR. Thanks for your help! 😄 |
@codekow I just reopened a comment regarding the namespace annotation. I know there was some disagreement, but I feel relatively strongly that it's not the right move for now. I'd also rather leave it off, and add it later, than have an annotation that we need to support for backward compatibility sake. |
@jaypipes @a-hilaly @RedbackThomson I believe all discussed items have been addressed. The PR should be ready to test. |
/ok-to-test |
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.
++ Thank you @codekow !
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.
Nice stuff here, let's get this merged! :)
Great. Thank you! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: A-Hilaly, acornett21, codekow, jaypipes, RedbackThomson 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 |
Issue #, if available: #1632
Description of changes:
Improve label selection for service and deployment association with pods. When multiple operators are deployed you may get inconsistent results on the service.
Related s3-controller/pull/94
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.