Skip to content
This repository has been archived by the owner on Jun 30, 2022. It is now read-only.

Volume created with wrong reclaim policy #2

Open
phertweck opened this issue Jul 19, 2018 · 0 comments
Open

Volume created with wrong reclaim policy #2

phertweck opened this issue Jul 19, 2018 · 0 comments

Comments

@phertweck
Copy link

Thank you very much for this provisioner. It's very helpful for us.

Unfortunately I've a problem with the reclaim policy. I've created two storage classes. One using reclaim policy delete and one retain. Getting the storage classes via kubectl shows the correct classes. After adding two volume claims (one for each class) both volumes use reclaim policy delete although the mapping to the storage class is correct.

To sum up: Storage classes are created using the correct reclaim policy. Creating Volumes from retain storage class always results in volumes with delete reclaim policy.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant