-
Notifications
You must be signed in to change notification settings - Fork 22
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
Instead of adding our own label, reuse Statefulset selector #18
base: main
Are you sure you want to change the base?
Conversation
7cfab9a
to
e174379
Compare
This removes the need for the mostly redundant "name" label. Signed-off-by: György Krajcsovits <[email protected]>
Signed-off-by: György Krajcsovits <[email protected]>
e174379
to
d236af4
Compare
This change will use all label matchers from statefulset selector to find pods. This is possibly a breaking change. It's not clear to me why it wasn't done before (perhaps due to a scenario when deploying rollout-operator to existing cluster?). |
I am wondering why this is not merged into master. |
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.
LGTM
We need to better investigate this before merging this PR. |
is there any help or anything I can help to confirm in order to merge this PR? In my understanding this would not be a breaking change. |
We need to test it at Grafana Labs to make sure it's not a breaking change for our use cases. |
@pracucci, how's testing going at Grafana Labs re: this change? |
Priorities changed and we never tested this change. |
This removes the need for the mostly redundant "name" label.
Fixes: #15
Signed-off-by: György Krajcsovits [email protected]