Skip to content
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

Is it possible to exclude a specific ClusterOperator? #187

Open
stratus-ss opened this issue Oct 5, 2022 · 3 comments
Open

Is it possible to exclude a specific ClusterOperator? #187

stratus-ss opened this issue Oct 5, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request high priority This issue needs to be fixed ASAP

Comments

@stratus-ss
Copy link

I have a scenario where I have a specific cluster operator that I want to exclude. For example openshift-samples is it possible to ignore a specific operator?

I know you can disable all cluster operator watching, but there are scenarios where a few operators might fail, and that might be ok depending on the environment. For example, insights, marketplace, and openshift-samples are not required to have a functioning cluster.

Thanks

@sandrobonazzola sandrobonazzola added the question Further information is requested label Oct 17, 2022
@chaitanyaenr
Copy link
Collaborator

Hi @stratus-ss, thanks for creating the issue! The use case that you mentioned is very much valid, we will work on adding the functionality in Cerberus to filter/skip operators based on name/regex. Please feel free to let us know if you would like to add the enhancement. Thanks.

@chaitanyaenr chaitanyaenr added enhancement New feature or request and removed question Further information is requested labels Oct 17, 2022
@stratus-ss
Copy link
Author

I might be able to do a PR for this. I'd be starting from scratch for this code base. Any avenues to look at would be appreciated

@chaitanyaenr
Copy link
Collaborator

@stratus-ss sure thing. We need to tweak the config to accept a list with regex pattern(s) from user here - https://github.com/redhat-chaos/cerberus/blob/main/config/config.yaml#L6 and skip them from monitoring in the function here - https://github.com/redhat-chaos/cerberus/blob/main/cerberus/kubernetes/client.py#L350.

Here is a sample PR which does something similar for namespace monitoring - https://github.com/redhat-chaos/cerberus/pull/178.

Please feel free to let us know in case of any questions and we are more than happy to help!

@chaitanyaenr chaitanyaenr added the high priority This issue needs to be fixed ASAP label Apr 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request high priority This issue needs to be fixed ASAP
Projects
None yet
Development

No branches or pull requests

3 participants