Administration on Krkn

Cluster Management

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

Cluster Management Admin

Register target Kubernetes clusters that will be available for chaos scenario execution. The operator runs on a control plane cluster and executes scenarios against registered targets — it never runs chaos against itself.

This walkthrough is retained with v1.0.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.0.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.

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

Creating a Private Registry

Configure a private registry by providing its connection settings (URL, credentials, TLS configuration).

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.0.0 documentation and may show an earlier interface.

Supported Providers

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

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.

Your browser does not support the video tag.

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.

Your browser does not support the video tag.

Overview

Many krkn scenarios need cloud API access (for example node stop/start, zone outages, or power outages). Instead of asking every user to paste access keys into scenario parameters, admins can:

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
Provider 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.