Helm

When should I use this?

• You operate Helm-based releases and want AutoObserve installed as a chart.
• You completed the [Kubernetes overview](/docs/deploy/kubernetes) and need the install commands.
• You are onboarding as a design partner with guided Helm values.

Requirements

• Kubernetes cluster with Helm 3.xRequired
• Namespace and secrets for AutoObserve credentialsRequired
• Cluster RBAC for AutoObserve workloadsRequired
• OpenTelemetry pipelines ready to connect after installOptional

Steps

1. Add the chart repository

# Placeholder — chart coordinates ship with GA and design-partner install guides
# helm repo add autoobserve oci://registry.example.com/autoobserve
# helm repo update

2. Create values for your environment

Design-partner installs use reviewed values for resource limits, ingress, and secrets. At minimum, configure:

• OTLP ingress or internal service endpoints
• API credentials and TLS settings
• Resource requests for your expected telemetry volume

# values.yaml (example skeleton)
autoobserve:
  ingress:
    enabled: true
  resources:
    requests:
      cpu: "500m"
      memory: "1Gi"

3. Install the release

# helm upgrade --install autoobserve autoobserve/autoobserve \
#   --namespace autoobserve --create-namespace \
#   -f values.yaml

Until public chart coordinates ship, Design Partners receive guided Helm values reviewed against your cluster.

Did it work?

• Helm release reaches deployed state
• AutoObserve pods running in target namespace
• UI or API reachable from your network
• Ready to connect OpenTelemetry

Troubleshooting

What's next?