Kubernetes Helm AgentCopy Anchor Link

Deploy the Owlpane agent on any Kubernetes cluster to collect node/pod/container metrics, Kubernetes events, optional container logs, and application OTLP traces — then forward them to your Owlpane workspace.

Customers install from the public OCI Helm chart. The agent source repository is private; you do not clone GitHub to deploy.

PrerequisitesCopy Anchor Link

• A Kubernetes cluster (kind, EKS, GKE, AKS, or similar)
• Helm 3.x and kubectl configured for the cluster
• An Owlpane ingest key (owl_ing_…) from Setup (/observability/setup)
• Ingest URL (SaaS default: https://ingest.owlpane.com) and API URL (https://api.owlpane.com)

What the chart runsCopy Anchor Link

Telemetry RBAC is read-only by default (no Secret data, no exec, no write verbs). Enable ops.enabled only if you want console-driven scale/restart.

Install (OCI Helm)Copy Anchor Link

kubectl create namespace owlpane

kubectl -n owlpane create secret generic owlpane-ingest \
  --from-literal=key='owl_ing_YOUR_KEY'

helm upgrade --install owlpane oci://ghcr.io/owlpane/owlpane-agent \
  --version 0.3.6 \
  --namespace owlpane \
  --set endpoint=https://ingest.owlpane.com \
  --set apiEndpoint=https://api.owlpane.com \
  --set cluster.name=prod-us-east-1

Pin --version to a released chart version. Prefer creating the ingest Secret yourself so the key never lands in Helm values or git.

Minimal values.yaml overrideCopy Anchor Link

endpoint: https://ingest.owlpane.com
apiEndpoint: https://api.owlpane.com
cluster:
  name: prod-us-east-1

# Optional: container logs (off by default — often contains PII)
# logs:
#   enabled: true

# Optional: console-queued operations (scale/restart)
# ops:
#   enabled: true
#   scopeNamespaces: ["payments", "web"]

helm upgrade --install owlpane oci://ghcr.io/owlpane/owlpane-agent \
  --version 0.3.6 -n owlpane -f values.yaml

VerifyCopy Anchor Link

1. Pods healthy:

kubectl get pods -n owlpane
kubectl logs -n owlpane -l app.kubernetes.io/name=owlpane-agent --tail=50

2. In the Owlpane console, open Infrastructure → Kubernetes (or Metrics / Logs) and confirm series tagged with your cluster.name.
3. Install the Kubernetes (owlpane-otel-collector) pack from Dashboards → Library (/observability/dashboards/library).

Verify chart signature (optional)Copy Anchor Link

Releases are signed keylessly with cosign:

cosign verify ghcr.io/owlpane/owlpane-agent:0.3.6 \
  --certificate-identity-regexp 'https://github.com/.*/owlpane-agent/.*' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

Auto-instrumentation (optional)Copy Anchor Link

When enabled in values (and the OpenTelemetry Operator is installed in the cluster), annotate workloads so traces and runtime metrics flow to the node agent OTLP port — see Runtime telemetry.

TroubleshootingCopy Anchor Link

UninstallCopy Anchor Link

helm uninstall owlpane -n owlpane
kubectl delete namespace owlpane

RelatedCopy Anchor Link

• Host OpenTelemetry collector for VMs without Kubernetes
• IoT edge gateway
• Kubernetes integration packs