Kubernetes

Kubernetes persistent storage

Stateful applications on Kubernetes need storage that survives pod restarts and node failures. Cloud block storage is simple but single-zone; Longhorn and Ceph replicate across nodes; NFS is fine for shared read-mostly data.

We pick the storage class per workload, enable volume snapshots, and back up persistent data with Velero so a cluster rebuild does not mean data loss.

At a glance

CloudDO Block Storage, EBS, Azure Disk, GCE PD via CSI
On-premLonghorn, Rook-Ceph, TrueNAS CSI, NFS subdir provisioner, Proxmox CSI
DatabasesCloudNativePG, Percona operators, or managed database services
BackupVelero with CSI snapshots and object storage

What RackLedge does

How we work

Every cluster we build starts from Git. Infrastructure as code creates the cluster, Flux or Argo CD reconciles everything inside it, and no change reaches production without a pull request. That is what makes a rebuild after a bad day a matter of hours instead of weeks.

Operations are the product: monitoring with alerts that mean something, backups of cluster state and persistent volumes, upgrades on a quarterly cadence and an on-call engineer who already knows the environment. We run production Kubernetes for our own platforms, so the runbooks are ones we use ourselves.

We are honest about fit. A handful of stable services on a couple of VMs does not need Kubernetes, and we will say so. Teams that ship weekly, need to scale or run many services get real value from it.

Related services

More on kubernetes

Frequently asked questions

Should databases run in Kubernetes?

With a mature operator such as CloudNativePG, yes. Without one, a managed database service is less risk for most teams.

Need a hand with this?

Tell us what you are running and what is slowing you down. You get a straight assessment and a plan, with no obligation. Support desk is staffed 24/7.

Get in touch