If you treat your cluster as ephemeral, how do you re-attach PVs and PVCs to your persistent storage?

• cluster-template

  63 1,540 9.9 Python

  A template for deploying a Kubernetes cluster with k3s or Talos

  

With docker-compose it's possible to treat the entire deployment as ephemeral. This means that one can throw away everything and redeploy from git+configuration almost instantly and it'll work basically right away. I want to achieve the same thing with a kubernetes cluster and a git-ops solution (currently considering this flux-based template though I am also considering something using ArgoCD). My question is, how can I reattach persistent storage to the new deployments on a new cluster? All the required information like storage location, secrets etc. would be setup through git and pulled automatically after initializing and connecting everything (which can be automated too) - the only thing I don't get is how can the new pods with their new unique-id's automatically reattach to their predecessors data?

• bootstrap-repo

  7 17 8.8 Shell

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project