High Availability Deployment by Pod Topology Spread Constraints in K8s Cluster
In the modern world, running a high-availability service is the most important thing for the users. As Kubernetes is getting more common, it's essential to know how to achieve a robust deployment across all the Applications. Assuming the network unreliability is handled by the Application retry and idempotency mechanism, what's left is to make sure the Applications are running well. The only threat is some "real-world" damage to the server. so we are always told to spread our application across different server-rack, data center zones, or geography regions.
In this article, we will share:
- Related K8s labels to be used
- How to use the Pod Topology Spread Constraints
- How would it work