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
Describe the bug
We currently set the owner reference on the PVC template for the SS to the ArtemisCR, deleting the ArtemisCR deletes the PVC and release any PV, any PV with retain retain policy of Delete goes away as expected.
To persist data, a PV needs a retain policy.
However, leaving the PVC around allowed a non Retain PV to survive as in use.
There still needs to be some way to cleanup PVC's as the data retention is a function of the PV retention policy, however this gc/cleanup needs to be more carefully considered.
I will rollback the changes from #244
and verify that the PVC remains.
An owner reference may still be the best approach, lets see.
Additional context
If the ArtemisCR has persistenceEnabled=true, then it needs a PV with policy Retain to match its PVC.
The text was updated successfully, but these errors were encountered:
Describe the bug
We currently set the owner reference on the PVC template for the SS to the ArtemisCR, deleting the ArtemisCR deletes the PVC and release any PV, any PV with retain retain policy of Delete goes away as expected.
To persist data, a PV needs a retain policy.
However, leaving the PVC around allowed a non Retain PV to survive as in use.
There still needs to be some way to cleanup PVC's as the data retention is a function of the PV retention policy, however this gc/cleanup needs to be more carefully considered.
I will rollback the changes from #244
and verify that the PVC remains.
An owner reference may still be the best approach, lets see.
Additional context
If the ArtemisCR has persistenceEnabled=true, then it needs a PV with policy Retain to match its PVC.
The text was updated successfully, but these errors were encountered: