Helm

Connect Helm to the Pagerly SRE Agent to check release history and deploy status.

What the Agent Can Do

• List all Helm releases across the cluster — chart name, version, status, namespace

• Get revision history — when each version was deployed and its status

How It Works

Helm stores release metadata as Kubernetes Secrets (labeled owner=helm). The agent queries these secrets to reconstruct your release history — no Helm binary needed.

Setup Instructions

1. Uses your existing Kubernetes credentials

2. Provide the same K8s API URL and service account token used for your Kubernetes integration

3. The service account needs get and list permissions on Secrets with label owner=helm

Required Credentials

Field	Description	Example
Service Account Token	K8s service account token	eyJhbGciOiJSUzI1NiIs...
Kubernetes API URL	Same K8s API URL as your K8s integration	https://kubernetes.example.com:6443

Context Prompt Tips

"Our Helm releases are in the production namespace. Main charts: api, worker, cron."

Docs

• Helm Documentation