KlusterAlert

Quickstart

Coming SoonKlusterAlert is not yet available. This is a preview of the setup experience.

Connect your first cluster and receive a Teams or Slack notification in about 5 minutes.

5 min setup Helm 3 required Any Kubernetes distribution

Prerequisites

A running Kubernetes cluster (any distribution)
Helm 3 installed and configured to access your cluster
kubectl access with cluster-admin or equivalent
A KlusterAlert account (coming soon)

Step 1: Create a cluster & get your agent token

In the the KlusterAlert dashboard, go to Clusters → Add Cluster. Enter a name for your cluster and optionally a Teams webhook URL or notification email. Click Create cluster & get token. KlusterAlert generates a unique AGENT_TOKEN for this cluster. Copy it. You'll need it in the next step.

Each cluster gets its own agent token. The token authenticates the agent running inside that cluster. Keep it secret and store it as a Kubernetes Secret (see below).

Step 2: Add the Helm repo

Helm chart setup instructions will be available at launch.

Step 3: Install the agent

Install KlusterAlert agent

helm install klusteralert-agent klusteralert/agent \
  --namespace klusteralert-agent \
  --create-namespace \
  --set agentToken=$AGENT_TOKEN \
  --set clusterName=production

clusterName is how this cluster appears in the KlusterAlert dashboard. Use something descriptive like prod-eu-west-1 or staging.

Step 4: Verify the agent is running

kubectl get pods -n klusteralert-agent

# Expected output:
NAME                                         READY   STATUS    RESTARTS   AGE
klusteralert-agent-6d9f8b7c4d-xkp2j         1/1     Running   0          45s

In the the KlusterAlert dashboard, go to Clusters. Your cluster should appear as Connected within 60 seconds. The agent checks for pod issues every 60 seconds and pushes them to KlusterAlert automatically.

Step 5: Test the alert

Deploy a broken pod to trigger a real alert end-to-end:

Trigger a CrashLoopBackOff alert

kubectl run crasher --image=busybox -- /bin/sh -c "exit 1"

# Within ~60 seconds KlusterAlert detects the crash loop and fires the alert.
# Check your Teams channel or email for the notification.
kubectl delete pod crasher

What's next

Connecting Clusters

Multi-cluster setup and RBAC requirements

Notification Channels

Configure Teams, Slack, and email alerts