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

Maintenance mode for the cephcsi resources #75

Open
Madhu-1 opened this issue Aug 1, 2024 · 2 comments
Open

Maintenance mode for the cephcsi resources #75

Madhu-1 opened this issue Aug 1, 2024 · 2 comments
Assignees

Comments

@Madhu-1
Copy link
Collaborator

Madhu-1 commented Aug 1, 2024

Describe the feature you'd like to have

If there is a change in the cephcsi artifacts like deployment/daemonset/service/csidriver object, the operator should not reconcile it if certain annotation is set

Who is the end user and what is the use case where this feature will be valuable?

This is useful for development and also useful for the customers whey they want to make changes to the deployment in some cases but want operator not to revert it back

How will we know we have a good solution? (acceptance criteria)

Add a list of criteria that should be met for this feature to be useful

Additional context

Add any other context or screenshots about the feature request here.

@travisn
Copy link
Member

travisn commented Aug 1, 2024

Would it be sufficient to just scale down the csi operator during maintenance?

@Madhu-1
Copy link
Collaborator Author

Madhu-1 commented Aug 5, 2024

Would it be sufficient to just scale down the csi operator during maintenance?

@travisn yes that work but not for all the cases like the admin wants to make one manual changes to the deployment (tuning certain configurations which are not configurable) but wants to keep the operator running to ensure that all the operator functionality works (like csi configmap update etc)

@Madhu-1 Madhu-1 self-assigned this Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants