Skip to main content

Install OpsWorker Kubernetes Agent

Overview​

The OpsWorker Kubernetes Agent is a lightweight component that runs inside your cluster, collecting data for AI-powered investigations. It is installed with Helm from a public OCI registry (no helm repo add step).

Prerequisites​

  • Kubernetes 1.16 or later
  • Helm 3.x installed
  • kubectl configured for your target cluster
  • Cluster admin permissions (for creating the namespace and RBAC binding)
  • Outbound HTTPS (443) to AWS SQS, AWS STS, api.opsworker.ai, and onboarding.ow-saas-prod-ext.opsworker.ai
  • The install command from the OpsWorker portal (generated when you add a cluster); it includes the auto-filled cluster token and API key

Installation Steps​

1. Run the Install Command​

Use the command shown in the Add Cluster wizard. The portal generates and fills in both clusterToken and apiKey for you (you do not type them). Both are required.

helm install opsworker-agent oci://public.ecr.aws/k1v3l8a8/opsworker-agent \
  --version=v0.9.3 \
  --timeout=90s \
  --namespace opsworker-agent \
  --create-namespace \
  --set clusterToken=<auto-filled by portal> \
  --set apiKey=<auto-filled by portal>

2. Verify Installation​

Check that the agent pods are running:

kubectl get pods -n opsworker-agent

A default install creates three pods (the agent, kubernetes-mcp-server, and grafana-mcp):

NAME                                          READY   STATUS    RESTARTS   AGE
opsworker-agent-xxxxxxxxxx-xxxxx              1/1     Running   0          30s
opsworker-agent-kubernetes-mcp-server-...    1/1     Running   0          30s
opsworker-agent-grafana-mcp-...              1/1     Running   0          30s

3. Confirm Connection​

Return to the OpsWorker portal. The portal automatically polls the agent status, so your cluster moves from Pending to a connected state within a minute. No manual confirmation step is required.

Resource Requirements​

The agent has a minimal footprint:

ResourceDefault RequestDefault Limit
CPU100m200m
Memory256Mi512Mi

Custom Configuration​

You can customize the installation with Helm values:

helm install opsworker-agent oci://public.ecr.aws/k1v3l8a8/opsworker-agent \
  --version=v0.9.3 \
  --namespace opsworker-agent \
  --create-namespace \
  --set clusterToken=<auto-filled by portal> \
  --set apiKey=<auto-filled by portal> \
  --set resources.limits.memory=512Mi

See Agent Configuration for all available options.

Restricted Environments​

Behind a Proxy​

The chart has no proxy.* values. Set the standard proxy environment variables through the chart's env list:

helm install opsworker-agent oci://public.ecr.aws/k1v3l8a8/opsworker-agent \
  --version=v0.9.3 \
  --namespace opsworker-agent \
  --create-namespace \
  --set clusterToken=<auto-filled by portal> \
  --set apiKey=<auto-filled by portal> \
  --set env[0].name=HTTPS_PROXY --set env[0].value=http://proxy.example.com:3128

Namespace-Scoped Access​

To limit the agent to specific namespaces, see Agent RBAC. Namespace scoping is a manual workaround, not a chart toggle.

Upgrading​

To upgrade the agent:

helm upgrade opsworker-agent oci://public.ecr.aws/k1v3l8a8/opsworker-agent \
  --version=v0.9.3 \
  -n opsworker-agent \
  --reuse-values

Next Steps​