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

How to pause operator watch? #350

Closed
rhrytskiv opened this issue Oct 12, 2022 · 3 comments · Fixed by #353
Closed

How to pause operator watch? #350

rhrytskiv opened this issue Oct 12, 2022 · 3 comments · Fixed by #353
Labels
enhancement New feature or request

Comments

@rhrytskiv
Copy link

Is your feature request related to a problem? Please describe.
I can't find in documentation how to pause operator from watching specific or all redis resources.

Describe the solution you'd like
Pause operator from watching specific or all redis resources

Describe alternatives you've considered

What version of redis-operator are you using?

redis-operator version: redis-operator-0.11.2

Additional context

@rhrytskiv rhrytskiv added the enhancement New feature or request label Oct 12, 2022
@devkmsg
Copy link
Contributor

devkmsg commented Oct 13, 2022

What is your usecase for this feature? #325 may be related depending on your usecase.

@rhrytskiv
Copy link
Author

@devkmsg I'm using Mayastor as my storage backend, and to update Mayastor it's essential to scale down every statefulset that is using PVs.
If you just scale down statefulset operator will scale it back down. For example rabbitmq operator has this feature .
I've though worked-around this lack of feature by just scaling down redis operator to 0 before scaling down statefulsets.

@iamabhishek-dubey
Copy link
Member

It can be used now like this:

annotations:
    redis.opstreelabs.in/skip-reconcile: "true"
    rediscluster.opstreelabs.in/skip-reconcile: "true"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants