Steadybit logoReliability Hub
GitHubGitHub iconStart Free Trial
Steadybit logoReliability Hub

Deployment Pod Count

CheckCheck
Verifies Kubernetes Deployment pod counts
Targets:
Kubernetes Deployments
Install now

Deployment Pod Count

Verifies Kubernetes Deployment pod counts
CheckCheck
Install now

Deployment Pod Count

CheckCheck
Verifies Kubernetes Deployment pod counts
Install now

Deployment Pod Count

Verifies Kubernetes Deployment pod counts
CheckCheck
Install now
Go back to list
Experiment EditorExperiment Editor

Introduction

Check if the count of ready pods is matching your expectation

It counts the number of all pods in the ready-state and compares it with the desired replica count. It, therefore, assumes that the specified mode (see below) becomes true within the specified timeout.

Use Cases

  • Check if the ready count is equal to the desired count
  • Check if the ready count is below the desired count
  • Check if there is at least one ready pod
  • Check if the pod count increases if you add load
  • Check if the pod count decreased if there is no more load

Parameters

ParameterDescriptionDefault
TimeoutHow long should the check wait for the specified pod count?10s
Pod CountHow should the pod count change? (See values below)

Pod Count

You can use the pod count check in one of the following modes:

  • ready count = desired count: Can be used to assure that the amount of desired ready pods is equal to the actual amount in the cluster. Helpful to check e.g. after an attack whether every pod is recovering.
  • ready count > 0: To assure that for each pod in the cluster at least one pod is available to serve the traffic.
  • ready count < desired count: To make sure that all pods matching the check's query are below the specified ready count. This can be helpful in case you want to verify that e.g. exhausting memory leads to restarting the pods.
  • actual count increases: Check if the pod count increases compared to the actual number of pods when you started the action.
  • actual count decreases: Check if the pod count decreases compared to the actual number of pods when you started the action.

Useful Templates (4 of 28)

See all
Kubernetes deployment survives Redis latency

Verify that your application handles an increased latency in a Redis cache properly, allowing for increased processing time while maintaining throughput.

Motivation

Latency issues in Redis can lead to degraded system performance, longer response times, and potentially lost or delayed data. By testing your system's resilience to Redis latency, you can ensure that it can handle increased processing time and maintain its throughput during increased latency. Additionally, you can identify any potential bottlenecks or inefficiencies in your system and take appropriate measures to optimize its performance and reliability.

Structure

We will verify that a load-balanced user-facing endpoint fully works while having all pods ready. As soon as we simulate Redis latency, we expect the system to maintain its throughput and indicate unavailability appropriately. We can introduce delays in Redis operations to simulate latency. The experiment aims to ensure that your system can handle increased processing time and maintain its throughput during increased latency. The performance should return to normal after the latency has ended.

Redis
Recoverability
Datadog

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!

Statistics
-Stars
Tags
Kubernetes
Homepage
hub.steadybit.com/extension/com.steadybit.extension_kubernetes
License
MIT
MaintainerSteadybit
Install now
Steadybit logoReliability Hub
Start Free Trial
© 2025 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon