Skip to content

Latest commit

 

History

5 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 

Repository files navigation

nudgebee-demo

Kubernetes failure scenarios you can apply to a cluster to see Nudgebee's event detection, evidence collection, and AI-generated root cause analysis in action.

Each scenario produces a well-known, deterministic failure (e.g. ImagePullBackOff, OOMKilled, CrashLoopBackOff) so the resulting event and RCA are predictable and easy to reason about.

Prerequisites

  • A Kubernetes cluster (any distribution — GKE, EKS, AKS, k3s, kind, minikube).
  • The Nudgebee Kubernetes collector installed and the cluster onboarded to your Nudgebee account. See docs.nudgebee.com.
  • kubectl configured against the target cluster.

Quick start

# Create the demo namespace
kubectl apply -f namespace.yaml

# Apply any single scenario
kubectl apply -f scenarios/01-image-pull-backoff/manifest.yaml

# Or apply all scenarios at once
kubectl apply -f namespace.yaml
for d in scenarios/*/; do kubectl apply -f "$d/manifest.yaml"; done

Once a scenario is applied, open the Nudgebee UI and filter events by namespace nudgebee-demo. Expected wait times and what to look for are documented in each scenario's README.md.

Scenarios

# Scenario Failure Time to event Event priority
1 Image Pull BackOff Container image cannot be pulled ~2–3 min HIGH
2 CrashLoopBackOff Container exits with non-zero code ~2–3 min HIGH
3 OOMKilled Container killed for exceeding memory limit ~2–3 min HIGH
4 Readiness probe failure Readiness probe keeps failing (HTTP 404) immediate DEBUG
5 PVC Pending PersistentVolumeClaim cannot bind ~15 min MEDIUM

Scenarios 1–3 produce HIGH-priority events within a few minutes via dedicated Kubernetes reporters. Scenario 5 relies on a Prometheus alert (KubePodNotReady) which fires after ~15 minutes. Scenario 4 only produces a lower-priority Kubernetes warning event — see its README for details.

Cleanup

# Remove a single scenario
kubectl delete -f scenarios/01-image-pull-backoff/manifest.yaml

# Remove everything including the namespace
kubectl delete namespace nudgebee-demo

Labels

Every workload in this repo carries the following labels for easy filtering:

  • app.kubernetes.io/part-of: nudgebee-demo
  • nudgebee.io/demo-scenario: <scenario-name>

License

MIT

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors