Basic Run

Run a chaos scenario and observe what happens — no metrics, no scoring, no pipeline.

What you need

Install krknctl — follow the installation guide.
List available scenarios to find one that fits your target:
```
krknctl list
```
Run a scenario — for example, to kill pods matching a label:
```
krknctl run pod-scenarios
```
krknctl will prompt you for required inputs interactively, or you can pass them as flags.
Observe results in your cluster using kubectl or your existing monitoring tools. Krkn logs pass/fail and recovery status to stdout.
For pod scenarios specifically, you can confirm the pod was killed and recovered by checking its age. A restarted pod will show a much shorter uptime than its neighbours:
```
kubectl get pods -A
```
Example output after a pod scenario targeting the my-app namespace:
```
NAMESPACE     NAME                          READY   STATUS    RESTARTS   AGE
my-app        frontend-7d9f8b6c4-xk2pq      1/1     Running   0          8s
my-app        backend-5c6d7f8b9-lm3rt        1/1     Running   0          4d2h
kube-system   coredns-787d4945fb-nqpzj       1/1     Running   0          4d2h
```
The 8s age on frontend shows it was recently restarted by the scenario while all other pods remain unaffected.

Read each scenario’s documentation to understand what inputs are available.
When you’re ready to add automatic metric evaluation, continue to Metrics Validation.