Describe the bug
Exact same thing as in #2456 but not commenting there as it was requested to open new issue in this comment.
All our PV and PVC are reserved using claimerf and volumename according to the docs:
https://kubernetes.io/docs/concepts/storage/persistent-volumes/#reserving-a-persistentvolume
This is not working anymore after we upgraded to new flux version. Probably because claimref uuid value is lost somehow when applied by flux (or perhaps more precise by the api/tool flux uses to do apply) as mentioned in #2250.
Conclusion seems to be to remove claimref from all pv and that is also working for us but official docs says that it should be there if we want to reserve the pv for a specific pvc.
Steps to reproduce
See #2456
Expected behavior
See #2456
Screenshots and recordings
See #2456
OS / Distro
See #2456
Flux version
kustomize-controller:v0.26.1
Flux check
N/A
Git provider
No response
Container Registry provider
No response
Additional context
No response
Code of Conduct
Describe the bug
Exact same thing as in #2456 but not commenting there as it was requested to open new issue in this comment.
All our PV and PVC are reserved using
claimerfandvolumenameaccording to the docs:https://kubernetes.io/docs/concepts/storage/persistent-volumes/#reserving-a-persistentvolume
This is not working anymore after we upgraded to new flux version. Probably because claimref uuid value is lost somehow when applied by flux (or perhaps more precise by the api/tool flux uses to do apply) as mentioned in #2250.
Conclusion seems to be to remove
claimreffrom all pv and that is also working for us but official docs says that it should be there if we want to reserve the pv for a specific pvc.Steps to reproduce
See #2456
Expected behavior
See #2456
Screenshots and recordings
See #2456
OS / Distro
See #2456
Flux version
kustomize-controller:v0.26.1
Flux check
N/A
Git provider
No response
Container Registry provider
No response
Additional context
No response
Code of Conduct