Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

Verify Cluster Elasticity when Restarting a Node

A resilient Kubernetes cluster is able to cope with a changing number of hosts and avoid user-facing reliability issues.
Targets:

Hosts

Kubernetes deployments

Download now

Verify Cluster Elasticity when Restarting a Node

A resilient Kubernetes cluster is able to cope with a changing number of hosts and avoid user-facing reliability issues.
Targets:

Hosts

Kubernetes deployments

Download now

Verify Cluster Elasticity when Restarting a Node

A resilient Kubernetes cluster is able to cope with a changing number of hosts and avoid user-facing reliability issues.
Targets:

Hosts

Kubernetes deployments

Download now

Verify Cluster Elasticity when Restarting a Node

A resilient Kubernetes cluster is able to cope with a changing number of hosts and avoid user-facing reliability issues.
Targets:

Hosts

Kubernetes deployments

Download now
Go back to list
The experiment editor showing the visual structure of the experiment.The experiment editor showing the visual structure of the experiment.

Intent

A resilient Kubernetes cluster is able to cope with a changing number of nodes and avoid user-facing reliability issues.

Motivation

A changing amount of nodes in your Kubernetes cluster is an expected behavior as you may update your nodes from time to time or simply scale the cluster depending on traffic peaks. This is especially true in the case of using spot instances in a Cloud environment. This requires the deployments to be node-independent and properly configured to be rescheduled on a newly started node or on a node that still has free resources.

Structure

Before restarting a node we verify that the cluster is in a healthy state and deployments are ready. Afterward, we trigger a restart of the node of a specific Kubernetes deployment and expect that the deployment will be rescheduled within 15 minutes. This assumes that the related node needs to be fully restarted and not a new one will kick in.

Environment Example

The Kubernetes deployment gateway consists of two pods which are expected to be scheduled on two different nodes.

Solution Sketch


Download now

.json (3 kB)

It's quick and easy

  1. 1.

    Download .json file
  2. 2.

    Upload it inside Steadybit
  3. 3.

    Start your experiment!
Screenshot showing the Steadybit UI elements to import the experiment.json file into the Steadybit platform.
Tags
Kubernetes
Recoverability
Scalability
Elasticity
GitHub
steadybit/reliability-hub-db/tree/main/recipes/kubernetes-nodes.node-restart
License
MIT
MaintainerSteadybit

Used Actions

See all
Pod Count

Verifies Kubernetes pod counts

Check

Check

Kubernetes deployments

Start Using Steadybit Today

Get started with Steadybit, and you’ll get access to all of our features to discover the full power of Steadybit. Available for SaaS and on-prem!

Are you unsure where to begin?

No worries, our reliability experts are here to help: book a demo with them!

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