Showing Post From Kubernetes
Kubernetes admission policy in 2026: revisit Kyverno, Gatekeeper and ValidatingAdmissionPolicy before you add another policy engine
Picture a health insurance technology company in Chennai (an invented example, not a real client). Its platform team runs eleven Kubernetes clusters.
Read moreService mesh in 2026: revisit Istio ambient, Linkerd and Cilium before you add sidecars
A logistics company in Bengaluru runs a production Kubernetes cluster with 14 nodes and about 420 pods. Three requests landed in one sprint.
Read moreArgo CD and Flux: revisit your GitOps controller before you scale or migrate
A platform team in Pune looks after 14 Kubernetes clusters. Most of them are managed by one central Argo CD instance that the team set up in 2021.
Read moreIngress NGINX retirement: revisit your Kubernetes ingress before you migrate
A platform team plans its Kubernetes 1.37 upgrade for the next sprint. The cluster checklist is green, except one line nobody owns: the ingress-nginx Helm chart, pinned at 4.
Read more