Gremlin Scenario: Container TLS/SSL certificate expiration

How it works

How this Scenario works

This Scenario advances the system clock within your containers forward by one day, one week, and one month. This triggers certificate validation logic and reveals any TLS/SSL certificates that will expire within those time windows—especially important for containers where certificates may be mounted as secrets or baked into images.

Use cases

Why run this Scenario?

Proactively identify expiring certificates in containerized services before they cause outages.
Test certificate rotation automation for certificates mounted as container secrets or volumes.
Verify that container-level monitoring detects upcoming certificate expirations.
Identify containers using baked-in certificates that won't benefit from automated rotation.

Result

What to expect when you run it

If a TLS certificate expires without renewal, the containerized service fails gracefully and alerts trigger immediately.

Keep going

More Scenarios to try

Kubernetes packet loss

Ensure your Kubernetes systems can detect and route around resources that fail health checks. This Scenario gradually increases packet loss to validate liveness/readiness probe and load balancer behavior.

Container packet loss

Ensure your containerized systems can detect and route around resources that fail health checks. This Scenario gradually increases packet loss to validate health check and load balancer behavior.

Windows packet loss

Ensure your Windows systems can detect and route around resources that fail health checks. This Scenario gradually increases packet loss to validate health check and load balancer behavior.

Container TLS/SSL certificate expiration