Minimal GKE Autopilot Design for Stateless Web Services
A practical architecture note for deploying a stateless web service on GKE Autopilot, covering requirements, smallest design, trust boundaries, operational checks, and failure modes.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A practical architecture note for deploying a stateless web service on GKE Autopilot, covering requirements, smallest design, trust boundaries, operational checks, and failure modes.
I am currently using the following to attempt to spread Kubernetes pods in a given deployment across all Kubernetes nodes evenly: spec: affinity: podAntiAffinity: preferredDuringSchedulingIgnoredDuringExecution: - weight: 100 podAffinityTerm: topologyKey: kubernetes.io/hostname labelSelector: matchExpressions: - key: app operator: In values: - api However, I
A small application is being migrated with a Kubernetes Deployment using RollingUpdate. The goal is to keep the Service available during the rollout while the cluster has a fixed capacity ceiling that cannot be exceeded. With maxSurge=0 the controller must terminate an old pod before a new one can be scheduled, which respects the resource ceiling but tempora