This article explains the two hard parts of backing up databases on Kubernetes: getting a consistent snapshot while writes continue, and patching what the app points at during a Velero restore.
More: https://ku.bz/9n8-wN5bD
Post #4050
248
- Sep 28, 2026This article explains why Ingress is being replaced by the Gateway API, what the new Gatew…
- Sep 28, 2026A dashboard can recommend lower requests and limit values, but the decision is still to be…
- Sep 28, 2026Heading to KubeCon + CloudNativeCon North America? Join us the day before for our first in…
- Sep 25, 2026This case study explains how Modelplane was built entirely as a Crossplane configuration,…
- Sep 25, 2026This case study shows how a team ran one Kafka cluster stretched across three separate Kub…
- Sep 24, 2026This case study shows how a payments company rebuilt deployments around GitOps with Argo C…