Open
Conversation
Member
|
@qawl987 Please help to check it! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change PersistentVolume Reclaim Policy from Retain to Delete
Problem
When using persistentVolumeReclaimPolicy: Retain, after the PVC is deleted (e.g., during helm uninstall), the PV remains in a Released state and retains a reference (claimRef) to the old PVC. This prevents the PV from being automatically bound to a new PVC on subsequent deployments.
As a result, every time before redeploying, we had to manually run:
kubectl patch pv free5gc-pv-cert --type json -p '[{"op": "remove", "path": "/spec/claimRef"}]'Solution
Change the reclaim policy to Delete. With this policy:
When the PVC is deleted, the PV will be automatically deleted as well
On the next deployment, a fresh PV will be created and bound to the new PVC
No manual intervention required between deployments
Note
This change is suitable for development and testing environments where data persistence across deployments is not required. For production environments where certificate data must be preserved, Retain policy should be used with proper operational procedures.