Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

Deployment Rollout Status

Check

Check

Check the rollout status of the deployment. The check succeeds when no rollout is pending, i.e., kubectl rollout status exits with status code 0.
Install now

Deployment Rollout Status

Check the rollout status of the deployment. The check succeeds when no rollout is pending, i.e., kubectl rollout status exits with status code 0.
Check

Check

Install now

Deployment Rollout Status

Check

Check

Check the rollout status of the deployment. The check succeeds when no rollout is pending, i.e., kubectl rollout status exits with status code 0.
Install now

Deployment Rollout Status

Check the rollout status of the deployment. The check succeeds when no rollout is pending, i.e., kubectl rollout status exits with status code 0.
Check

Check

Install now
Go back to list
Experiment editor showing the rollout status check among an experiment to identify how a deployment copes with restarts.Experiment editor showing the rollout status check among an experiment to identify how a deployment copes with restarts.

Introduction

You can use the rollout status check to ensure, among others, that a Kubernetes deployment is ready and operational before injecting chaos. This check is helpful to ensure that the system is in a steady state to avoid false positives.

Use Cases

  • Check that there are no pending deployments before triggering chaos.
  • Verify that the deployment is ready again after injecting turbulent conditions.

Rollback

No rollback necessary.

Blog Posts

Parameters

NameRequiredDescription
TimeoutNoMaximum time to wait for the rollout to complete.
Statistics
-Stars
Tags
Kubernetes
Homepage
hub.steadybit.com/extension/com.steadybit.extension_kubernetes
License
MIT
MaintainerSteadybit
Install now

Useful Templates

See all
Faultless redundancy during rolling update

Kubernetes features a rolling update strategy to deploy new releases without downtime. When being under load, this only works reliably when your load balancer and the Kubernetes readiness probe are configured properly and DNS caches are up-to-date.

Motivation

The Kubernetes rolling update strategy ensures that a minimum number of pods remain available when a new release is deployed. This implies that a new pod with a new release is started and needs to be ready before an old pod is evicted. Even so, this process may result in degraded performance and user-facing errors, e.g., Kubernetes sending requests to pods indicated as ready but not able to respond properly or evicted pods are still retained in the load balancer.

Structure

Before performing the rolling update all desirable pods of the deployment need to be in the “ready”-state, and a load-balanced user-facing HTTP endpoint is expected to respond successfully while under load. As soon as the rolling update takes place, the HTTP endpoint under load may suffer from a degraded performance (e.g. lower success rate or higher response time). Even so, this should be within the boundaries of your SLA. After the rolling update, the number of desirable pods matches the actual pods of the deployment and the performance of the user-facing HTTP endpoint is similar to before the update.

Solution Sketch

  • Kubernetes liveness, readiness, and startup probes
  • Kubernetes deployment strategy
Rolling Update
Restart
Kubernetes

Kubernetes cluster

Kubernetes deployments

More Kubernetes Deployment Actions

See all
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
© 2024 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon