Keep Deployment's Pods Down
Keep Deployment's Pods Down
Keep Deployment's Pods Down
Keep Deployment's Pods Down
Go back to listCheck what happens when all pods of a Kubernetes deployment aren't coming up again.
Motivation
Typically, Kubernetes tries to keep as many pods running as desired for a Kubernetes deployment. However, some circumstances may prevent Kubernetes from achieving this, like missing resources in the cluster, problems with the deployment's probes, or a CrashLoopBackOff. You should validate what happens to your overall provided service when a given deployment is directly affected by this or one of the upstream services used by your deployment.
Structure
To keep the pods down for a given deployment, we first kill all the pods in the deployment. Simultaneously, we will scale down the Kubernetes deployment to 0 to simulate that these pods can't be scheduled again. At the of the experiment, we automatically roll back the deployment's scale to the initial value.
How to use this template?
Import via Hub Connection
Steadybit’s Reliability Hub is already connected to your platform. If you are an admin, you can just easily import templates with just one click.
Are you on-prem?
This is how you import Templates
