Skip to main content

Add Kubernetes Cluster

Overview

Connect a Kubernetes cluster to OpsWorker so it can investigate alerts and answer questions about your infrastructure.

Prerequisites

  • An OpsWorker account with a workspace
  • A Kubernetes cluster (EKS, GKE, AKS, or self-hosted, version 1.24+)
  • Helm 3.x and kubectl access to the cluster

Steps

1. Start the Add Cluster Wizard

  1. In the OpsWorker portal, navigate to Configurations → Add Cluster
  2. The wizard guides you through the setup process

2. Name Your Cluster

  • Enter a descriptive name (e.g., production-us-east, staging-eu)
  • Select the workspace this cluster belongs to

3. Select Integrations

Choose which integrations to enable for this cluster:

IntegrationPurpose
Alert ManagerReceive alerts from Prometheus AlertManager
Grafana AlertingReceive alerts from Grafana via webhook
Grafana MCPEnable AI agents to query Grafana metrics, logs, and dashboards during investigations

Grafana Alerting and Grafana MCP are separate integrations. Alerting sends alerts to OpsWorker; MCP lets OpsWorker query Grafana. You can enable one or both. See the Grafana Integration guide for details on each.

You can add more integrations later from the cluster settings.

4. Get the Install Command

The wizard generates a Helm install command with your unique cluster token. If you enabled Grafana MCP, the command will include additional flags for the Grafana sidecar:

helm repo add opsworker https://charts.opsworker.ai
helm repo update
helm install opsworker-agent opsworker/opsworker-agent \
--namespace opsworker \
--create-namespace \
--set clusterToken=YOUR_CLUSTER_TOKEN

With Grafana MCP enabled, the command adds:

  --set grafana-mcp.enabled=true \
--set grafana-mcp.grafanaUrl=https://grafana.example.com \
--set grafana-mcp.grafanaToken=YOUR_GRAFANA_SERVICE_ACCOUNT_TOKEN

Copy this command — you'll run it in the next step.

5. Install the Agent

Run the Helm command in your terminal (with kubectl configured for your target cluster). See Install Kubernetes Agent for detailed instructions.

6. Verify Connection

After installation, return to the portal. Your cluster status should show Connected within a minute. See Verify Cluster Connection for validation steps.

Resuming Setup

If you leave the wizard before completing setup, you can resume from Configurations — look for clusters with Pending status.

Network Requirements

The agent requires outbound HTTPS access (port 443) to AWS SQS endpoints (*.amazonaws.com). No inbound ports need to be opened.

Next Steps