chaosd vs Krkn

Chaosd is free Apache-2.0 software for injecting and recovering faults on physical machines. It can create process, network, CPU or memory pressure, disk, and host faults. Use it as a command-line tool or run it as a background service controlled through HTTP requests. Chaosd is deployed separately from Chaos Mesh; PhysicalMachineChaos experiments require service mode on each targeted physical or virtual machine. The documented environment requires glibc 2.17 or later, and the binary download described is a Linux amd64 tarball. Network experiments using tc or iptables require sudo or root privileges. Deployment prerequisites include tc, ipset, and iptables; source builds additionally list stress-ng and byteman. Experiments can be searched and recovered by UID. TLS certificates are shown for service security, and running without generated certificates is not recommended.

Krkn injects deliberate failures into Kubernetes clusters so teams can examine resilience under disruption. Its 20-plus scenarios cover pods, containers, nodes, networks, applications, resources, storage and time. The recommended krknctl command-line tool discovers, runs and coordinates scenarios; other choices include pre-built containers, a browser dashboard and a standalone Python program. Krkn evaluates Prometheus metrics against SLO pass/fail criteria and can review metrics during and after scenarios. Dashboard integrations include Elasticsearch and Grafana, and telemetry can be sent to S3 or Elasticsearch. Cerberus monitors Kubernetes and OpenShift health, providing a go/no-go signal, reports and a metrics API; it can also report failures in Slack. Krkn-AI uses evolutionary algorithms against user-defined objectives to identify experiments. Krkn says it saves recovery state and can restore a cluster, but some disruptive scenarios may leave the target unrecoverable. It is intended for resilience measurement, not security provision, and does not currently adhere to compliance standards. Requirements include Kubernetes or OpenShift 1.21+, cluster-admin kubeconfig access, and Docker 20.10+ or Podman 4.0+.