Introduction

Prevent your deployment from being down by having at least two pods or an automatic scaling via HorizontalPodAutoscaler. Otherwise, e.g., a single failure in a pod, crashing host, or availability zone being down would cause unavailability of a deployment.

Supported Advice States

Action Needed

The advice automatically discovers whether a Kubernetes deployment has at least two pods configured, e.g., via spec.replicas or HorizontalPodAutoscaler. The discovery is performed by the open-source library kube-score and integrated into this advice.

Validation Needed

Asks you to validate with an automatically created experiment that provided features work as expected when a container of a single pod is restarting.

If the target is associated with a service, the experiment automatically includes a service validation step. This makes it easy to judge whether the service behaves as expected from a user’s perspective.

If you do not use Steadybit’s service feature, you can require the user to provide additional validations via a wizard when creating the experiment. For that, you need to tag your Kubernetes targets with the label tags.steadybit.com/service-validation and one of the following values:

• http: Run an HTTP check on a GET endpoint
• k6: Run a k6 load test
• gatling: Run a Gatling load test
• jmeter: Run a JMeter load test

If none of these options apply, the experiment will include a TODO step prompting you to add custom validation logic for your service.

Implemented

Once you have configured Kubernetes to have at least two pods or the deployment is targeted by a HorizontalPodAutoscaler.

Disabling Advice

Every advice is automatically active as described in extension-kubernetes#configuration. You can also activate advice individually, using for this advice, the identifier com.steadybit.extension_kubernetes.advice.k8s-single-replica.