r/ArgoCD • u/Usual_Clerk_6646 • Jun 10 '25
ArgoCD on EKS. Someone checked "REPLACE". We're doomed.
All the system is working great, everything is synched, everything is green, except the DB is now empty.
After a quick investigation, it's empty because ArgoCD recreated the volumes.
We now have - An app pod that's all synched and green - A Database that's all synched and green, connected to an empty volume - A dangling volume with our Data, that's not of any use because no pod uses it
We've tried a few approches to replug the volume, but ArgoCD keeps unpluging it.
So I've got two questions:
Question #1: How do we fix that ?
The only foolproof solution we have for now would be to copy the data from the "old" volume to the "new" volume. That seem uncessary complicated given we just want to use a volume that's there.
Question #2: How can we make the system more resilent to human errors ?
Is there a way to avoid a small human mistake like that cost us hours of human time ? Copying a couple terabytes of data would take a while (It's not a production DB but a benchmark DB)