-
Notifications
You must be signed in to change notification settings - Fork 157
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
Fix NodeConfigPod controller to exclusively enqueue and sync Scylla Pods #1131
Conversation
216d8b0
to
36dd2bc
Compare
892d225
to
dfe9b86
Compare
54f405b
to
e0dbb02
Compare
89fedb9
to
fea7b6c
Compare
ca5987f
to
977dc83
Compare
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, thanks
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.
I think we should also add the check to sync too. Handlers are more about optimization, which is good as well, but there should be a single point of enforcement.
6cf3570
to
456fc7a
Compare
f4a728f
to
0143df8
Compare
0779f18
to
9929ca6
Compare
62efd19
to
6893036
Compare
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.
/approve
/lgtm
6893036
to
dc5864c
Compare
rebased on current master, @zimnx please approve |
Description of your changes:
As described in #1119, currently the NodeConfigPod controller removes ownerReferences from any ConfigMap that has a controllerRef to any Pod. This is undesired as the controller shouldn't affect any resources that the operator doesn't manage. This PR adds a condition verifying whether the owner of the ConfigMap is a Scylla Pod.
Which issue is resolved by this Pull Request:
Resolves #1119