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
Without this enabled, users will still face the issue described here: #361
Describe the solution you'd like
When delting a trench, the operator must delete the PVC assigned to the NSP and IPAM. Deleting the PVC will automatically delete the PV (so no API access needed for this).
This will require the operator to have access to another Kubernetes API function to detete the PVC (PVC is a namespaced resource).
Describe alternatives you've considered
/
Additional context
/
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
This issue is a follow-up to these:
#362
#361
The current implementation using the
persistentVolumeClaimRetentionPolicy
property in the StatefulSet specs requires the users to run on at least, Kubernetes v1.23 with the feature gateStatefulSetAutoDeletePVC
enabled. This feature, as of Kubernetes v1.26 is still in alpha and disabled by default. Here is a PR to move it to beta: kubernetes/kubernetes#111300. And here is the documentation: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#persistentvolumeclaim-retentionWithout this enabled, users will still face the issue described here: #361
Describe the solution you'd like
When delting a trench, the operator must delete the PVC assigned to the NSP and IPAM. Deleting the PVC will automatically delete the PV (so no API access needed for this).
This will require the operator to have access to another Kubernetes API function to detete the PVC (PVC is a namespaced resource).
Describe alternatives you've considered
/
Additional context
/
The text was updated successfully, but these errors were encountered: