Installation on Krkn

Krkn

Thu, 05 Jan 2017 00:00:00 +0000

Installation

Clone the Repository

To clone and use the latest krkn version follow the directions below. If you’re wanting to contribute back to krkn in anyway in the future we recommend forking the repository first before cloning.

See the latest release version here

$ git clone https://github.com/krkn-chaos/krkn.git --branch <release version>
$ cd krkn

Fork and Clone the Repository

Fork the repository

krkn-hub

Thu, 05 Jan 2017 00:00:00 +0000

Hosts container images and wrapper for running scenarios supported by Krkn, a chaos testing tool for Kubernetes clusters to ensure it is resilient to failures. All we need to do is run the containers with the respective environment variables defined as supported by the scenarios without having to maintain and tweak files!

Set Up

You can use docker or podman to run kraken-hub

krknctl

Mon, 01 Jan 0001 00:00:00 +0000

Install krknctl (Recommended)

Use the official install script as the primary installation method:

Install using the official script

curl -fsSL https://raw.githubusercontent.com/krkn-chaos/krknctl/refs/heads/main/install.sh | bash

Verify installation:

krknctl --version

Alternative installation methods

Binary distribution

The krknctl binary is available for download from GitHub releases for supported operating systems and architectures. Extract the tarball and add the binary to your $PATH.

Build from source

Fork and clone the repository

Fork the repository:

Setting Up Disconnected Enviornment

Mon, 01 Jan 0001 00:00:00 +0000

Getting Started Running Chaos Scenarios in a Disconnected Enviornment

Mirror following images on the bastion host

quay.io/krkn-chaos/krkn-hub:node-scenarios-bm - Master/worker node disruptions on baremetal
quay.io/krkn-chaos/krkn-hub:network-chaos - Network disruptions/traffic shaping
quay.io/krkn-chaos/krkn-hub:pod-scenarios - Pod level disruptions and evaluating recovery time/availability
quay.io/krkn-chaos/krkn-hub:syn-flood - Generates substantial amount of traffic/half open connections targeting a service
quay.io/krkn-chaos/krkn-hub:node-cpu-hog - Hogs CPU on the target nodes
quay.io/krkn-chaos/krkn-hub:node-io-hog - Hogs IO on the target nodes
quay.io/krkn-chaos/krkn-hub:node-memory-hog - Hogs memory on the target nodes
quay.io/krkn-chaos/krkn-hub:pvc-scenarios - Fills up a given PersistentVolumeClaim
quay.io/krkn-chaos/krkn-hub:service-hijacking - Simulates fake HTTP response for a service
quay.io/krkn-chaos/krkn-hub:power-outages - Shuts down the cluster and turns it back on
quay.io/krkn-chaos/krkn-hub:container-scenarios - Kills a container via provided kill signal
quay.io/krkn-chaos/krkn-hub:application-outages - Isolates application Ingress/Egress traffic
quay.io/krkn-chaos/krkn-hub:time-scenarios - Tweaks time/date on the nodes
quay.io/krkn-chaos/krkn-hub:pod-network-chaos - Introduces network chaos at pod level
quay.io/krkn-chaos/krkn-hub:node-network-filter - Node ip traffic filtering
quay.io/krkn-chaos/krkn-hub:pod-network-filter - DNS, internal/external service outages

Will also need these mirrored images inside the cluster

Network disruptions - quay.io/krkn-chaos/krkn:tools
Hog scenarios ( CPU, Memory and IO ) - quay.io/krkn-chaos/krkn-hog
SYN flood - quay.io/krkn-chaos/krkn-syn-flood:latest
Pod network filter scenarios - quay.io/krkn-chaos/krkn-network-chaos:latest
Service hijacking scenarios - quay.io/krkn-chaos/krkn-service-hijacking:v0.1.3

How to Mirror

The strategy is simple:

Krkn-AI

Mon, 01 Jan 0001 00:00:00 +0000

Installation

Prerequisites

Python 3.11+
Podman or Docker Container Runtime
krknctl
uv package manager (recommended) or pip

Clone the Repository

To clone and use the latest krkn version follow the directions below. If you’re wanting to contribute back to Krkn-AI in anyway in the future we recommend forking the repository first before cloning.

$ git clone https://github.com/krkn-chaos/krkn-ai.git
$ cd krkn-ai

Fork and Clone the Repository

Fork the repository

Krkn Dashboard

Mon, 01 Jan 0001 00:00:00 +0000

The Krkn Dashboard is a web UI for running and observing Krkn chaos scenarios. You can run it locally (Node.js on your machine) or containerized (Podman/Docker).

Prerequisites (both methods)

Kubernetes cluster — You need a cluster and a kubeconfig so that the dashboard can target it for chaos runs. If you don’t have one, see Kubernetes, minikube, K3s, or OpenShift.
Podman or Docker — The dashboard starts chaos runs by launching krkn-hub containers; the host must have Podman (or Docker) installed and available.

Local installation

Run the dashboard on your machine with Node.js.