Administration on Krkn

Cluster Management

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

Cluster Management Admin

Register target Kubernetes clusters for chaos scenario execution. Krkn Operator runs on a management cluster and executes scenarios against registered targets; it does not run scenarios against itself.

This walkthrough is retained with v1.1.0 documentation and may show an earlier interface.

Operations

Operation	Description
Add Cluster	Register a new target cluster by providing its name and kubeconfig
View Clusters	Browse all registered clusters and their status
Delete Cluster	Remove a cluster from the platform

Once registered, clusters become available for assignment to groups through User Management.

User Management

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

User Management Admin

Organize users through groups that define cluster access and permissions. The group is the central unit of the permission model — users inherit all capabilities from their assigned group.

This walkthrough is retained with v1.1.0 documentation and may show an earlier interface.

Groups

A group defines what its members can access and do on the platform.

Registry Management

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

Registry Management Admin

Configure private container registries for chaos scenario images and control which groups can access them. By default, scenarios are pulled from the public Quay.io registry. Private registries enable air-gapped deployments and custom scenario images.

INFO

Before running scenarios from a private registry, follow Mirror Signed Images to copy the scenario and its Cosign signature. Mirror any helper workload image too, and override the scenario’s IMAGE parameter with its private registry URL. An image-only mirror is insufficient for signed scenario execution.

This walkthrough is retained with v1.1.0 documentation and may show an earlier interface.

Mirror Signed Images

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

Mirror Signed Images Admin

For a private or disconnected environment, mirror both the scenario image and any helper workload image it launches. Copy their Cosign signatures with the images. A normal docker pull/docker push, podman pull/podman push, or image-only mirror can leave the signatures behind.

INFO

Image signature verification is enabled by default. The Operator checks the scenario image against the Krkn public key before creating its pod. If the mirrored scenario has no valid signature, the run is rejected. A mirrored workload image also needs its signature when your cluster enforces signed images; the scenario must point to its private registry URL or the workload pod will try to pull from Quay.io.

The source repository is quay.io/krkn-chaos/krkn-hub-multiarch. Its tags include scenarios such as node-cpu-hog and pod-scenarios, and helper images such as workload-krkn-hog and workload-krkn-tools. Choose the tags required by the scenarios you plan to run.

Provider Configuration

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

Provider Configuration Admin

Configure target providers that integrate with external cluster management platforms. The provider configuration interface adapts dynamically based on the selected provider.

This walkthrough is retained with v1.1.0 documentation and may show an earlier interface.

Supported Providers

Provider	Description
ACM / OCM	Discover and synchronize managed Kubernetes clusters through Red Hat Advanced Cluster Management or Open Cluster Management

INFO

The provider configuration interface is extensible. New integration operators can add their configuration panels here. Cloud credentials are managed separately; see the section below.

Cloud Provider Configuration

Krkn Operator supports cloud scenarios that use saved provider credentials. Administrators create and manage these credentials through Cloud Credentials Management. Users can select credentials their group is allowed to access.

Elasticsearch Management

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

Elasticsearch Management Admin

Administrators can configure and save Elasticsearch endpoints that users can reference when executing chaos scenarios. This enables centralized observability configuration without requiring users to manually enter connection details.

This walkthrough is retained with v1.1.0 documentation and may show an earlier interface.

Overview

Elasticsearch integration allows krkn scenarios to index execution metrics, logs, and telemetry data for analysis and historical tracking. Instead of requiring each user to configure Elasticsearch details manually, admins can:

Cloud Credentials Management

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

Cloud Credentials Management Admin

Administrators can configure and save cloud provider credentials that users select when running cloud-dependent chaos scenarios. Credentials are stored as Kubernetes Secrets and injected into scenario pods via SecretKeyRef — plaintext cloud secrets never appear in the Custom Resource or pod environment values.

This walkthrough is retained with v1.1.0 documentation and may show an earlier interface.

Backup and Restore

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

Backup and Restore Admin

The Krkn Operator includes a built-in backup and restore feature accessible from the web console. Backups contain portable operator configuration for:

Admin settings
Cluster targets
Users and groups
Private registries
Elasticsearch configuration

The backup also includes the operator-managed secrets required for these settings.

This feature is not a complete Kubernetes or cluster backup. It does not include runtime registration objects, ACM integration data, uploaded files, file metadata, or the JWT signing key.