Persistent Volume for Postgres Database in Kubernetes Cluster

Question

I have created a Persistant Disk Claim for my Postgres Database.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  creationTimestamp: null
  labels:
    io.kompose.service: pgdata
  name: pgdata
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 100Mi
status: {}

Once I delete the cluster, the volume got deleted too. what's the best practice here? Should I save in some other Persistent Disk like GCEPersistentDisk? I dont want to lose the volume even If cluster is deleted and what are the best strategies for deployment?

Nicola Ben · Accepted Answer · 2018-07-10 08:36:45Z

2

In the PersistenVolume manifest you can set the reclaiming policy (Retain or Delete, there was a third option now deprecated - Recycle):

persistentVolumeReclaimPolicy: Retain

Reference: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#claims-as-volumes

answered Jul 10, 2018 at 8:36

Nicola Ben

11.5k9 gold badges46 silver badges71 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Alamgir Qazi Over a year ago

Is this the right way to use in Production? I cannot afford losing the postgres volume data so I'm just being careful.

Nicola Ben Over a year ago

I use Retain in production.

Collectives™ on Stack Overflow

Persistent Volume for Postgres Database in Kubernetes Cluster

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related