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

Need info on how to handle existing CSIDriver kubernetes resources #81

Open
leelavg opened this issue Aug 2, 2024 · 5 comments
Open
Labels
documentation Improvements or additions to documentation

Comments

@leelavg
Copy link
Contributor

leelavg commented Aug 2, 2024

I see operator backing off from reconciling CSIDriver based on some heuristics, could those scenarios be mentioned and what is the expectation from code base which want to upgrade to using csi-operator.

@nb-ohad
Copy link
Collaborator

nb-ohad commented Aug 2, 2024

In order to make sure ceph-csi-operator takes ownership of an existing CSIDriver, you need to add an ceph.csi.io/ownerref annotation with the namespace name of the driver.csi.ceph.io resource (serialized as json) that will own it

@Madhu-1
Copy link
Collaborator

Madhu-1 commented Aug 5, 2024

@subhamkrai you can do this one as well, where you need to set the annotation instead of deleting the csidriver object

@subhamkrai
Copy link
Contributor

@subhamkrai you can do this one as well, where you need to set the annotation instead of deleting the csidriver object

added

@leelavg
Copy link
Contributor Author

leelavg commented Aug 13, 2024

Pls note correct label key is csi.ceph.io/ownerref

@subhamkrai
Copy link
Contributor

subhamkrai commented Aug 13, 2024

Pls note correct label key is csi.ceph.io/ownerref

I'm setting this value as only

@Madhu-1 Madhu-1 added the documentation Improvements or additions to documentation label Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants