Shutdown Host

Attack

Reboots or shuts down the host

Targets:

Hosts

Install now

Shutdown Host

Reboots or shuts down the host

Attack

Targets:

Hosts

Install now

Shutdown Host

Attack

Reboots or shuts down the host

Targets:

Hosts

Install now

Shutdown Host

Reboots or shuts down the host

Attack

Targets:

Hosts

Install now

Go back to list

The experiment editor showing a configured reboot attack.

Introduction

This action executes a shutdown on the host by issuing the shutdown command/syscall (depending on the operating system). You can instruct the action to issue a host restart when desired - in which case the command/syscall will be adapted as necessary.

Details

Kubernetes Nodes

If you're using the reboot option on Kubernetes nodes, it might be the case that the host finished rebooting and restarting the containers before the control plane takes notice. You can verify the behaviour of this attack for example by using the uptime command on the hosts.

Virtual Machines

Note that this action will not differentiate between bare-metal or virtual machines. It will always attempt to shut down/reboot a host using the above-mentioned strategy.

Parameters

Parameter	Description	Default
Reboot	Should the host reboot after shutting down?	true

Statistics

-Stars

Kubernetes node shutdown results in new node startup

A resilient Kubernetes cluster can cope with a crashing node and simply starts a new one.

Motivation

A changing number of nodes in your Kubernetes cluster is expected, as you may update your nodes from time to time or simply scale the cluster depending on traffic peaks. This is especially true when 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 a node that still has free resources.

Structure

Before restarting a node, we verify that the cluster is healthy and that the deployments are ready. Afterward, we trigger the shutdown of the node of a specific Kubernetes deployment and expect the deployment to be rescheduled on any other node and a new node to start up within a reasonable amount of time.

Solution Sketch

Kubernetes liveness, readiness, and startup probes

Warning

Please be aware that we will shut down a node. Please ensure this is fine and your node is either virtual or can somehow be started up afterward.

Elasticity

Kubernetes

Hosts

Kubernetes cluster

Kubernetes deployments

More Host Actions

See all

Block DNS

Blocks access to DNS servers

Attack

Hosts

Block Traffic

Drops network traffic (incoming and outgoing)

Attack

Hosts

Delay Traffic

Inject latency into network traffic.

Attack

Hosts

Drop Outgoing Traffic

Cause packet loss for outgoing network traffic (egress).

Attack

Hosts

Fill Disk

Writes data to the disk.

Attack

Hosts

Fill Memory

Allocates and holds memory.

Attack

Hosts

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!