-
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
Selector on watches.yaml not honoured #31
Comments
@jberkhahn The thread regarding this issue: https://mail.google.com/mail/u/0/#search/ansible/FMfcgzGrcXtllNJlqSFwVfvsJVrwzQjw @anupchandak Could you please share your controller pod logs or the project, for us to able to run it locally and check the issue. The selectors should be working as expected by creating predicates, looking at the logs may help us dig into it more. |
@varshaprasad96 - I tried creating a sample project using the Memcached example but was not able to reproduce the above issue. I cannot share my work project for copyright restrictions. Any pointer on how I can check what is all coming on the operator's watch list when it starts? And selector it is applying. |
Any way to know what dependent resource was changed that triggered the operator's reconciliation loop? |
The other option is to add additional logs in ansible operator binary and try it out locally to see what is happening. Some pointers are:
You may have to build the binary locally to test it out. The steps are here: https://sdk.operatorframework.io/docs/contribution-guidelines/developer-guide/. Before all this, I would suggest to increase the log verbosity and check if there is anything suspicious indicating that labels haven't been set up as expected. Hope this helps! |
@varshaprasad96 - Thank you so much for your detailed reply above. Sorry for the late reply but I think I am able to reproduce the issue. I think it's because of the dependent resource CronJob created by the CR. Please use the attached project and follow the below steps to reproduce the issue.
I have also attached logs from my local execution. Please note that to restrict the logs to only testing namespaces, I had set memcached-operator.zip Thank you! |
Team - Any comment/update on this issue? |
Hi Team - Have you got a chance to look at this issue? |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
To control the scope of an operator in a multi-development environment, I have defined a selector at the
watches.yaml
level by referring hereThe selector is defined as something like the below (presented below with equivalent dummy values)
When I start my ansible runner then as expected, I see the following log at the start
and I expect that my Operator will still not worry (watch) about CR defined with the label
mytest.com/controller-namespace=your-test-na
. But it does and reconciles it.It is an ansible based operator and environment details are as below:
The text was updated successfully, but these errors were encountered: