> ## Documentation Index
> Fetch the complete documentation index at: https://docs.komodor.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Koperator

> The operator that runs your self-hosted agents in your own Kubernetes cluster, so developers deploy and change agents from KAOP without cluster access.

Koperator is the operator that runs your self-hosted agents in your own Kubernetes cluster. You
install it once, with one Helm command, and the Komodor Agentic Operation Platform (KAOP) shows the
install as a **deploy target**. Developers then deploy, update, scale, stop and delete agents on
that deploy target from KAOP, with no `kubectl` or `helm` of their own.

Deploy targets are under **Settings → Deploy targets** when your account has them. If you do not
see the page, ask your account team to turn it on.

## Who owns what

Devops owns koperator: the install, the upgrades, and the guardrails it enforces in the cluster.
Those guardrails live in your Helm values, so KAOP cannot change them. Developers own the agents.
Who may deploy to which deploy target is an ordinary KAOP permission on that deploy target, so a
grant on `staging` does not allow a deploy to `production`. The [change
policy](https://docs.komodor.com/manage-your-agents/build/koperator/deploy-agents.md#change-policy) of a deploy target is a KAOP
setting that an owner or admin sets, and only an owner or admin approves a revision there.

## How koperator works

* **It only dials out.** Koperator registers with KAOP, sends a heartbeat, and holds a long-poll
  open for changes. Nothing connects in to your cluster.
* **A change applies in full or not at all.** Koperator checks each agent spec against your
  guardrails first. If one check fails, it applies no part of the spec, the agent keeps its last
  applied state, and the developer sees the reason in KAOP.
* **It reports what happened.** For each change, KAOP shows whether koperator applied it or why it
  failed.
* **It pins each image to its digest** when the registry lets it read the digest, so a pod that
  restarts runs the same image.
* **It keeps the agents as it applied them.** When another tool changes a field that koperator
  set, koperator applies its version again. See [When something else changes an
  agent](https://docs.komodor.com/manage-your-agents/build/koperator/gitops.md#when-something-else-changes-an-agent).
* **It runs two replicas.** One is the leader and does the work; the other takes over if the leader
  stops. See [High availability](https://docs.komodor.com/manage-your-agents/build/koperator/configure.md#high-availability).
* **Running agents do not depend on it.** When koperator is disconnected or stopped, the agents keep
  running and serving. A change in KAOP stays pending until koperator connects again.

## What koperator lets you do

> [card] [Install koperator](https://docs.komodor.com/manage-your-agents/build/koperator/install.md)
>
> Create a deploy target and run the install command.

> [card] [Configure koperator](https://docs.komodor.com/manage-your-agents/build/koperator/configure.md)
>
> Namespaces, guardrails, Secrets, network, proxy and KEDA.

> [card] [Deploy agents to a deploy target](https://docs.komodor.com/manage-your-agents/build/koperator/deploy-agents.md)
>
> Deploy, update, revise, stop and delete agents from KAOP.

> [card] [Adopt agents installed with Helm](https://docs.komodor.com/manage-your-agents/build/koperator/adopt-helm-agents.md)
>
> Let KAOP manage agents you already run from a Helm release.

> [card] [Upgrade koperator](https://docs.komodor.com/manage-your-agents/build/koperator/upgrade.md)
>
> Move to a new koperator version.

> [card] [Uninstall koperator](https://docs.komodor.com/manage-your-agents/build/koperator/uninstall.md)
>
> Choose what happens to the agents when koperator goes away.

> [card] [Argo CD and Flux](https://docs.komodor.com/manage-your-agents/build/koperator/gitops.md)
>
> Run koperator under a GitOps tool, and handle drift.

To run an agent with no replica while it is idle, see [Scale agents to
zero](https://docs.komodor.com/manage-your-agents/build/scale-to-zero.md).

## Image security

Each koperator image is built for `linux/amd64` and `linux/arm64`, scanned before it is published,
and published only when the scan finds no fixable high or critical vulnerability. Each image carries
an SPDX SBOM per architecture. The image and the chart are signed with keyless cosign, so you can
verify them without a credential:

```sh theme={null}
cosign verify \
  --certificate-identity "https://github.com/komodorio/agentops/.github/workflows/koperator-image.yml@refs/heads/master" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  ghcr.io/komodorio/agentops-koperator@sha256:<digest>
```

Run the same command against `ghcr.io/komodorio/charts/koperator@sha256:<digest>` for the chart.
Report a vulnerability to [security@komodor.io](mailto:security@komodor.io).


## Related topics

- [Configure koperator](https://docs.komodor.com/manage-your-agents/build/koperator/configure.md)
- [Upgrade koperator](https://docs.komodor.com/manage-your-agents/build/koperator/upgrade.md)
- [Uninstall koperator](https://docs.komodor.com/manage-your-agents/build/koperator/uninstall.md)
- [Install koperator on a deploy target](https://docs.komodor.com/manage-your-agents/build/koperator/install.md)
- [Adopt agents installed with Helm](https://docs.komodor.com/manage-your-agents/build/koperator/adopt-helm-agents.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.