https://github.com/robusta-dev/kubernetes-demos
YAMLs for creating Kubernetes errors and other scenarios
https://github.com/robusta-dev/kubernetes-demos
devops k8s kubernetes kubernetes-demo
Last synced: 7 months ago
JSON representation
YAMLs for creating Kubernetes errors and other scenarios
- Host: GitHub
- URL: https://github.com/robusta-dev/kubernetes-demos
- Owner: robusta-dev
- License: mit
- Created: 2022-11-14T12:16:36.000Z (about 3 years ago)
- Default Branch: main
- Last Pushed: 2025-06-20T09:12:56.000Z (7 months ago)
- Last Synced: 2025-06-22T03:52:45.979Z (7 months ago)
- Topics: devops, k8s, kubernetes, kubernetes-demo
- Language: TypeScript
- Homepage:
- Size: 2.45 MB
- Stars: 29
- Watchers: 4
- Forks: 16
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Introduction
Practice Kubernetes troubleshooting with realistic error scenarios.
Each scenario is run with `kubectl apply` commands. To cleanup, run `kubectl delete` on the same.
# Simple Scenarios
Crashing Pod (CrashLoopBackoff)
```
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/crashpod/broken.yaml
```
To get notifications like below, install [Robusta](https://github.com/robusta-dev/robusta):
OOMKilled Pod (Out of Memory Kill)
```
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/oomkill/oomkill_job.yaml
```
To get notifications like below, install [Robusta](https://github.com/robusta-dev/robusta):
High CPU Throttling (CPUThrottlingHigh)
Apply the following YAML and wait **15 minutes**. (CPU throttling is only an issue if it occurs for a meaningful period of time. Less than 15 minutes of throttling typically does not trigger an alert.)
```
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/cpu_throttling/throttling.yaml
```
To get notifications like below, install [Robusta](https://github.com/robusta-dev/robusta):
Pending Pod (Unschedulable due to Node Selectors)
Apply the following YAML and wait **15 minutes**. (By default, most systems only alert after pods are pending for 15 minutes. This prevents false alarms on autoscaled clusters, where it's OK for pods to be temporarily pending.)
```
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/pending_pods/pending_pod_node_selector.yaml
```
To get notifications like below, install [Robusta](https://github.com/robusta-dev/robusta):
ImagePullBackOff
```
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/image_pull_backoff/no_such_image.yaml
```
To get notifications like below, install [Robusta](https://github.com/robusta-dev/robusta):
Liveness Probe Failure
```
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/liveness_probe_fail/failing_liveness_probe.yaml
```
To get notifications like below, install [Robusta](https://github.com/robusta-dev/robusta):
Readiness Probe Failure
```
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/readiness_probe_fail/failing_readiness_probe.yaml
```
Job Failure
The job will fail after 60 seconds, then attempt to run again. After two attempts, it will fail for good.
```
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/job_failure/job_crash.yaml
```
To get notifications like below, install [Robusta](https://github.com/robusta-dev/robusta):
Failed Helm Releases
Deliberately deploy a failing Helm release:
```shell
helm repo add robusta https://robusta-charts.storage.googleapis.com && helm repo update
helm install kubewatch robusta/kubewatch --set='rbac.create=true,updateStrategy.type=Error' --namespace demo-namespace
```
Upgrade the release so it succeeds:
```shell
helm upgrade kubewatch robusta/kubewatch --set='rbac.create=true' --namespace demo-namespace --create-namespace
```
Clean up by removing the release and deleting the namespace:
```shell
helm del kubewatch --namespace demo-namespace
kubectl delete namespace demo-namespace
```
To get notifications like below, install [Robusta](https://github.com/robusta-dev/robusta) and setup [Helm Releases Monitoring](https://docs.robusta.dev/master/playbook-reference/triggers/helm-releases-monitoring.html)
# Advanced Scenarios
Correlate Changes and Errors
Deploy a healthy pod. Then break it.
```shell
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/crashpod/healthy.yaml
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/crashpod/broken.yaml
```
If someone else made this change, would you be able to immediately pinpoint the change that broke the application?
To get notifications like below, install [Robusta](https://github.com/robusta-dev/robusta).
Track Deployment Changes
Create an nginx deployment. Then simulate multiple unexpected changes to this deployment.
```shell
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/deployment_image_change/before_image_change.yaml
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/deployment_image_change/after_image_change.yaml
```
To get notifications like below, install [Robusta](https://github.com/robusta-dev/robusta) and [setup Kubernetes change tracking](https://docs.robusta.dev/master/tutorials/playbook-track-changes.html)
Track Ingress Changes
Create an ingress. Then changes its path and secretName to simulate an unexpected ingress modification.
```shell
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/ingress_port_path_change/before_port_path_change.yaml
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/ingress_port_path_change/after_port_path_change.yaml
```
To get notifications like below, install [Robusta](https://github.com/robusta-dev/robusta) and [setup Kubernetes change tracking](https://docs.robusta.dev/master/tutorials/playbook-track-changes.html)
Drift Detection and Namespace Diff
Deploy two variants of the same application in different namespaces:
```shell
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/namespace_drift/example.yaml
```
Can you quickly tell the difference between the `compare1` and `compare2` namespaces? What is the drift between them?
To do so with Robusta, install [Robusta](https://github.com/robusta-dev/robusta) and enable the UI.
Inefficient GKE Nodes
On GKE, nodes can reserve more than 50% of CPU for themselves. Users pay for CPU that is unavailable to applications.
Reproduction:
1. Create a default GKE cluster with autopilot disabled. Don't change any other settings.
2. Deploy the following pod:
```
kubectl apply -f https://raw.githubusercontent.com/robusta-dev/kubernetes-demos/main/gke_node_allocatable/gke_issue.yaml
```
3. Run `kubectl get pods -o wide gke-node-allocatable-issue`
The pod will be Pending. **A Pod requesting 1 CPU cannot run on an empty node with 2 CPUs!**
To see problems like this with Robusta, install [Robusta](https://github.com/robusta-dev/robusta) and enable the UI.
