Truly Persistent Volume - Githubissues

rivernews / iriversland2-kubernetes

Terraform provisioning K8 infra for iriversland2, my personal website, as well as other projects.

0 stars 1 forks source link

Truly Persistent Volume #27

Open rivernews opened 3 years ago

rivernews commented 3 years ago

Currently when k8s cluster gets destroyed, volume will get deleted too.

This is problematic for code-server, where our projects and repos are stored.

Explore DigitalOcean way to reuse exiting volume.

Initial idea:

TF: Data volume - create the digitalocean volume, AND resource volume, so in case it's already there TF should just use it, otherwise create one
Then, let code-server deployment mount this volume / use PVC to refer to the existing volume
We may need to extend our micro service tf module.

rivernews commented 3 years ago

A way to do this - for example, volume for code-server.

Assume creating the volume in UI - use a fixed volume name
In tf, use data to retrieve this volume
Make the rest of the required change needed to point to the volume.