Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

Reasonable Recovery Time when Losing a Pod

Use Template

Reasonable Recovery Time when Losing a Pod

Use Template

Reasonable Recovery Time when Losing a Pod

Use Template

Reasonable Recovery Time when Losing a Pod

Use Template
Go back to list

When deleting a pod, Kubernetes should bring up a new pod to ensure system stability.

Motivation

Deleting a pod simulates situations in which, for any reason, a pod stops working properly and needs to be rescheduled. This experiment makes sure that rescheduling works as expected and newly scheduled pods become ready within the expected timeframe.

Structure

All pods should be ready to accept traffic at the beginning of the experiment. Rescheduling should start as soon as a pod is deleted. Eventually, after the allotted time, all pods should be ready again.


Tags
Elasticity
Recoverability
Kubernetes
GitHub
steadybit/reliability-hub-db/tree/main/templates/kubernetes-deployment.time-to-readiness-pod-loss
License
MIT
MaintainerSteadybit
Use Template

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.

Import template

Are you on-prem?

This is how you import Templates

Import as Experiment

Simply download the template and upload it as an experiment to use it once. Perfect if you are no administrator in the platform and just want to use the template once.

.json (4KB)

Delete Pod

Deletes a pod

Attack

Attack

Kubernetes pods

>_ boost your chaos journey Connect Your Hub to Steadybit

Maximise Steadybit potential! Connect your own Hub to the platform and smoothly import your own templates: using them it’s never been this easy!

Steadybit logoResilience Hub
Try Steadybit
© 2024 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon