You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 30, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 oneretain
. Getting the storage classes via kubectl shows the correct classes. After adding two volume claims (one for each class) both volumes use reclaim policydelete
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 withdelete
reclaim policy.The text was updated successfully, but these errors were encountered: