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
Currently, each OVA provider has an attached PV and PVC with the owner reference set to the provider itself. When the provider is removed, the PVC is also deleted, but the PV only transitions to a 'released' state. This occurs because we are not using an underlying storage class for PV creation, which lacks a deletion policy. Therefore, we need to implement manual deletion of the PV in the backend once the provider is deleted
The text was updated successfully, but these errors were encountered:
Currently, each OVA provider has an attached PV and PVC with the owner reference set to the provider itself. When the provider is removed, the PVC is also deleted, but the PV only transitions to a 'released' state. This occurs because we are not using an underlying storage class for PV creation, which lacks a deletion policy. Therefore, we need to implement manual deletion of the PV in the backend once the provider is deleted
The text was updated successfully, but these errors were encountered: