helm template. These tools change
what koperator can check at install time and whether its uninstall hook runs, so read the
differences below before you hand koperator to one of them.
Install-time checks that do not run
These tools render the chart without access to the cluster, so three install-time checks do not run: the check that names the holder of a namespace claim, the check that each namespace exists, and the check for an existing KEDA. The claim hook Job still refuses a claimed namespace, and its log names the holder. Do not setkeda.enabled if
the cluster already runs KEDA.
-
Argo CD runs the claim hook as a PreSync hook. It cannot release a namespace you remove from
namespaces; the hook log prints thekubectl delete leasecommand to run. - These tools can skip the uninstall hook when you remove the app. Then no policy is applied, the agents keep running, the claims stay, and the Komodor Agentic Operation Platform (KAOP) shows the deploy target as disconnected. Delete the claims with the commands in Uninstall without the hook.
-
To delete an agent’s objects by hand, select them by the agent’s label.
<agent>is the name of the agent’s Deployment. Its revisions carryagentops.komodor.io/revision-of=<agent>instead:
Keep the install key out of git
Create thekoperator-<name>-credential Secret with Sealed Secrets, External Secrets Operator or
SOPS, and pass only its name in credential.existingSecret.
When something else changes an agent
Koperator watches the objects it applied. Whenkubectl edit, kubectl scale, or an Argo CD or
Flux sync changes a field that koperator applied, koperator applies its version again. After three
reverts in ten minutes it stops, leaves the agent as the other tool set it, and KAOP shows
drift_conflict with the name of that tool. To resolve it, remove the agent from the other tool,
then choose Retry on the agent’s Deployment panel. Any new change, a Stop included, also ends
the conflict.
A change to a field koperator does not set is not drift, for example the annotation that
kubectl rollout restart adds, or KEDA scaling a scale-to-zero agent.
Next steps
Adopt agents installed with Helm
Remove an agent from your GitOps tool before you adopt it.
Upgrade koperator
Move to a new koperator version.