Deploy Self Healing, Highly Available Couchbase Clusters on Kubernetes Using Persistent Volumes

Kubernetes is a leading container orchestration tool, available on practically all the major cloud platforms. It’s also used as the foundational glue to design self-managed on-premises cloud solutions. But did you know that managing a stateful application like a database in the K8s environment requires more planning than a stateless app?

We’ll talk about some of the best practices for deploying a Couchbase cluster in a Kubernetes environment using:

• Pod affinity, node selection, and resource capping to deliver QoS
• Availability zone awareness to achieve over five-nines availability
• Persistent volumes to improve failover and rebalancing time
• Cross datacenter replication to enable an active-active, multi-master capability

[pnmanju]

Good demo. But you missed to show pvc (persistence volume claim) case

[patrickproctor]

My persistent volume claims are never created by the operator and are never attached to my pods. It would really help if you guys would publish a codebase with the persistent volume claim setup where you know it actually works for minikube, gke, etc..