Warning
The deployments provided here are purposely malfunctioning.
They should not be used in production and are meant to be used for demos.
We required a reliable way to create unhealthy states in our clusters to showcase Dynatrace's monitoring capabilities.
Feedback and contributions are welcome.
| Problem Pattern | Description |
|---|---|
| exceeded-quota | a deployment that violates a specified resource quota when scaled up |
| frequent-restarts | periodic restart of a ingress-nginx pod |
| kyverno | third party (policy) tool emmitting warning signals and prometheus metrics |
| node-pressure | allocate RAM on a specified node using stress-ng until the system is out-of-memory |
| pending-pod | pods in pending state due to insufficient resources |
| pvc-out-of-space | container registry that will be filled up over time to exceed the limit on the pvc |
| terminating-pod | pod in terminating state due to a misconfigured finalizer |
New problem-patterns will be added over time and we plan to improve and adjust all of them in the near future.
Feel free to share ideas with us!