<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Administration on Krkn</title><link>https://krkn-chaos.dev/docs/krkn-operator/administration/</link><description>Recent content in Administration on Krkn</description><generator>Hugo</generator><language>en</language><atom:link href="https://krkn-chaos.dev/docs/krkn-operator/administration/index.xml" rel="self" type="application/rss+xml"/><item><title>Cluster Management</title><link>https://krkn-chaos.dev/docs/krkn-operator/administration/cluster-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://krkn-chaos.dev/docs/krkn-operator/administration/cluster-management/</guid><description>&lt;h1 id="cluster-management-admin">
 Cluster Management &lt;a href="https://krkn-chaos.dev/docs/krkn-operator/#permission-model">&lt;span class="krkn-badge krkn-badge--admin">Admin&lt;/span>&lt;/a>
 &lt;a class="td-heading-self-link" href="#cluster-management-admin" aria-label="Heading self-link">&lt;/a>
&lt;/h1>
&lt;p>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.&lt;/p>
&lt;div class="krkn-video">
 &lt;iframe src="https://www.youtube.com/embed/dSaA1BTQQBc" title="Cluster Management Walkthrough" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen>&lt;/iframe>
&lt;/div>
&lt;hr>
&lt;h2 id="operations">
 Operations
 &lt;a class="td-heading-self-link" href="#operations" aria-label="Heading self-link">&lt;/a>
&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Operation&lt;/th>
 &lt;th>Description&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&lt;strong>Add Cluster&lt;/strong>&lt;/td>
 &lt;td>Register a new target cluster by providing its name and kubeconfig&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>View Clusters&lt;/strong>&lt;/td>
 &lt;td>Browse all registered clusters and their status&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Delete Cluster&lt;/strong>&lt;/td>
 &lt;td>Remove a cluster from the platform&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>Once registered, clusters become available for assignment to groups through &lt;a href="../user-management/">User Management&lt;/a>.&lt;/p></description></item><item><title>User Management</title><link>https://krkn-chaos.dev/docs/krkn-operator/administration/user-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://krkn-chaos.dev/docs/krkn-operator/administration/user-management/</guid><description>&lt;h1 id="user-management-admin">
 User Management &lt;a href="https://krkn-chaos.dev/docs/krkn-operator/#permission-model">&lt;span class="krkn-badge krkn-badge--admin">Admin&lt;/span>&lt;/a>
 &lt;a class="td-heading-self-link" href="#user-management-admin" aria-label="Heading self-link">&lt;/a>
&lt;/h1>
&lt;p>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.&lt;/p>
&lt;div class="krkn-video">
 &lt;iframe src="https://www.youtube.com/embed/gCh4xj8KmP8" title="User &amp; Group Management Walkthrough" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen>&lt;/iframe>
&lt;/div>
&lt;hr>
&lt;h2 id="groups">
 Groups
 &lt;a class="td-heading-self-link" href="#groups" aria-label="Heading self-link">&lt;/a>
&lt;/h2>
&lt;p>A group defines what its members can access and do on the platform.&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Field&lt;/th>
 &lt;th>Description&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&lt;strong>Name&lt;/strong>&lt;/td>
 &lt;td>Group identifier&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Description&lt;/strong>&lt;/td>
 &lt;td>Purpose of the group&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Cluster Permissions&lt;/strong>&lt;/td>
 &lt;td>Which registered clusters this group can target&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>Groups also receive permission flags that control what operations their members can perform:&lt;/p></description></item><item><title>Registry Management</title><link>https://krkn-chaos.dev/docs/krkn-operator/administration/registry-management/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://krkn-chaos.dev/docs/krkn-operator/administration/registry-management/</guid><description>&lt;h1 id="registry-management-admin">
 Registry Management &lt;a href="https://krkn-chaos.dev/docs/krkn-operator/#permission-model">&lt;span class="krkn-badge krkn-badge--admin">Admin&lt;/span>&lt;/a>
 &lt;a class="td-heading-self-link" href="#registry-management-admin" aria-label="Heading self-link">&lt;/a>
&lt;/h1>
&lt;p>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.&lt;/p>
&lt;div class="krkn-video">
 &lt;iframe src="https://www.youtube.com/embed/3j9uQ475jv0" title="Registry Management Walkthrough" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen>&lt;/iframe>
&lt;/div>
&lt;hr>
&lt;h2 id="creating-a-private-registry">
 Creating a Private Registry
 &lt;a class="td-heading-self-link" href="#creating-a-private-registry" aria-label="Heading self-link">&lt;/a>
&lt;/h2>
&lt;p>Configure a private registry by providing its connection settings (URL, credentials, TLS configuration).&lt;/p></description></item><item><title>Provider Configuration</title><link>https://krkn-chaos.dev/docs/krkn-operator/administration/provider-configuration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://krkn-chaos.dev/docs/krkn-operator/administration/provider-configuration/</guid><description>&lt;h1 id="provider-configuration-admin">
 Provider Configuration &lt;a href="https://krkn-chaos.dev/docs/krkn-operator/#permission-model">&lt;span class="krkn-badge krkn-badge--admin">Admin&lt;/span>&lt;/a>
 &lt;a class="td-heading-self-link" href="#provider-configuration-admin" aria-label="Heading self-link">&lt;/a>
&lt;/h1>
&lt;p>Configure target providers that integrate with external cluster management platforms. The provider configuration interface adapts dynamically based on the selected provider.&lt;/p>
&lt;div class="krkn-video">
 &lt;iframe src="https://www.youtube.com/embed/MPd9beJWrzY" title="Provider Configuration Walkthrough" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen>&lt;/iframe>
&lt;/div>
&lt;hr>
&lt;h2 id="supported-providers">
 Supported Providers
 &lt;a class="td-heading-self-link" href="#supported-providers" aria-label="Heading self-link">&lt;/a>
&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Provider&lt;/th>
 &lt;th>Description&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&lt;strong>ACM / OCM&lt;/strong>&lt;/td>
 &lt;td>Automatically discover and synchronize managed Kubernetes clusters through Red Hat Advanced Cluster Management or Open Cluster Management&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>&lt;img src="https://krkn-chaos.dev/images/krkn-operator/provider-configuration-acm.png" alt="ACM Provider Configuration">&lt;/p>
&lt;div class="alert alert-info" role="alert"> &lt;div class="alert-header">
 &lt;i class="fas fa-circle-info text-info">&lt;/i> &lt;span class="alert-title">INFO&lt;/span>
 &lt;/div>
 &lt;div class="alert-content">
 The provider configuration interface is designed to be extensible. As new integration operators are developed, their configuration panels will appear automatically in this section.
 &lt;/div>
&lt;/div></description></item></channel></rss>