siatel/cloud
4
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases Wiki Activity

Cloud/harbor: nfs volumes migration #14

New Issue
Open
opened 2024-10-28 09:04:10 +00:00 by victorc · 2 comments
victorc commented 2024-10-28 09:04:10 +00:00
Owner
Copy Link
No description provided.
victorc commented 2024-11-27 13:35:56 +00:00
Author
Owner
Copy Link

registry,jobservice migrated

registry,jobservice migrated
victorc commented 2024-11-27 15:56:09 +00:00
Author
Owner
Copy Link

planned approch for the other 'Volume Claim Template' based (database, redis, trivy):

  • ensure each dynamically provisioned volume has reclaimPolicy set to Retain
  • create corresponding nfs persistent volume
  • scale in deployment/statefulset referring the existing claim to prevent writes
  • create a 'migration' pod mounting the existing volume via the existing claim and the new volume in any method of your choice
  • in the 'migration' pod copy the old volume to the new volume recursively, preserving ownership and mode ('cp -r -p -v /old/* /new' or 'rsync -av /old/ /new/' etc)
  • make note of the existing volume claim name, delete it and then to re-create it with exactly the same name ensuring the claim is on the new volume
  • scale out the deployment/stateful set
  • if all well and when correct funcionality confirmed old persisten volumes can be effectively deleted
planned approch for the other 'Volume Claim Template' based (database, redis, trivy): - ensure each dynamically provisioned volume has reclaimPolicy set to Retain - create corresponding nfs persistent volume - scale in deployment/statefulset referring the existing claim to prevent writes - create a 'migration' pod mounting the existing volume via the existing claim and the new volume in any method of your choice - in the 'migration' pod copy the old volume to the new volume recursively, preserving ownership and mode ('cp -r -p -v /old/* /new' or 'rsync -av /old/ /new/' etc) - make note of the existing volume claim name, delete it and then to re-create it with exactly the same name ensuring the claim is on the new volume - scale out the deployment/stateful set - if all well and when correct funcionality confirmed old persisten volumes can be effectively deleted
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: siatel/cloud#14
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?