values.yaml that maps to the operator’s command-line flags and Kubernetes resource configuration.
Default values
Value reference
Image
Replicas and scheduling
Webhook
The webhook requires TLS certificates. In production, use cert-manager to provision certificates automatically. The Helm chart includes the necessary annotations when cert-manager is available.
Self-healing
When
healthCheck.enabled is false, the operator still validates personas and discovers the cluster — it just never opens incidents or proposes fixes. Setting metricsServer.enabled=false passes --enable-metrics-server=false; OOM and crash-loop detection read pod status and are unaffected, but usage and saturation signals go dark. See Self-healing.
AI
The key is always delivered to the pod as the
ANTHROPIC_API_KEY environment variable via secretKeyRef — the chart never passes it as a container argument. See AI setup for the full walkthrough and the caveat about llm.apiKey being visible in helm get values.
Bootstrap
Set
autoCreateClusterPersona: false if you manage ClusterPersonas through GitOps and do not want the operator creating one.
Validation
Metrics and probes
ArgoCD
The watcher auto-detects whether the ArgoCD CRD exists. If
enabled: true but the CRD is absent, the watcher silently skips.
Prometheus
Example:
http://prometheus-server.monitoring:9090
WebSocket
When enabled, the chart creates a Service on the specified port.
Resources
Service account
Example: AI self-healing
Create the Secret out of band, then:Example: Production deployment
Configuration overview
Feature matrix and CLI flags
AI setup
Key handling, verification, and turning AI off
Self-healing
What the health-check reconciler does once enabled
Installation
Install the operator with these values