#Installation

Kagenti Operator is delivered as an OLM Operator and installed from the platform OperatorHub.

#Prerequisites

• ACP version: v4.0 or later (validated on v4.3).
• Target cluster architecture linux/amd64 or linux/arm64 (the operator ships multi-arch images).
• Operator Lifecycle Manager (OLM) available on the target cluster (provided by ACP).
• cert-manager installed on the target cluster. The operator's admission webhooks get their serving certificate from cert-manager.

#Upload Operator

Download the Kagenti Operator bundle from the Customer Portal / Marketplace, then publish it to the platform repository with the violet command-line tool:

violet push \
  --platform-address=<platform-access-address> \
  --platform-username=<platform-admin> \
  --platform-password=<platform-admin-password> \
  kagenti-operator.ALL.xxxx.tgz

#Install Operator

In the Administrator view:

1. Click Marketplace / OperatorHub.
2. At the top of the console, from the Cluster dropdown, select the destination cluster.
3. Search for and select Kagenti Operator, then click Install.
4. Leave Channel unchanged (stable).
5. Check that the Version matches the release you want to install.
6. Leave Installation Location unchanged — it defaults to the kagenti-system namespace.
7. Choose an Upgrade Strategy (Manual is recommended for production).
8. Click Install.

#Create the Kagenti operand

Installing the operator from OperatorHub runs the OLM operator. To deploy the agent controllers, CRDs, and webhooks, create a Kagenti custom resource. An empty spec selects the core profile:

kubectl apply -f - <<EOF
apiVersion: kagenti.alauda.io/v1alpha1
kind: Kagenti
metadata:
  name: kagenti
  namespace: kagenti-system
spec: {}
EOF

#Verification

Confirm the Kagenti Operator tile shows Installed, then verify on the cluster:

# the CSV reports Succeeded
kubectl get csv -n kagenti-system | grep kagenti

# the operator and agent controllers are Running
kubectl get pods -n kagenti-system

# the agent CRDs are registered
kubectl get crd | grep agent.kagenti.dev

You should see the agentruntimes, agentcards, and authorizationpolicies CRDs (group agent.kagenti.dev), the kagenti-controller-manager and kagenti-helm-operator-controller-manager pods Running, and the agent-label-protection ValidatingAdmissionPolicy.

The operator watches all namespaces, so you can enroll agents and tools in any namespace.