Install the Kubernetes Agent

Connect a Kubernetes cluster to IncidentFlow by installing the read-only IncidentFlow Kubernetes Agent. The agent establishes an outbound encrypted connection to IncidentFlow — it does not require an inbound endpoint or direct access from IncidentFlow to the Kubernetes API.

Prerequisites

Before you begin, make sure you have:

• access to an IncidentFlow workspace;
• permission to create a Kubernetes Agent in IncidentFlow;
• kubectl configured for the target cluster;
• permission to create a namespace, ServiceAccount, Secret, and read-only RBAC resources;
• outbound HTTPS and secure WebSocket access to IncidentFlow;
• Helm 3, when using the Helm installation method.

Install

1. Create an agent registration

   Open IncidentFlow → Kubernetes Agents and select Install Agent. Enter a human-readable cluster display name and a unique cluster identifier.

   The cluster identifier is used to identify the cluster and cannot be changed after registration.

2. Copy the one-time registration token

   IncidentFlow creates a one-time registration token. It is shown only once, expires after 24 hours when unused, is consumed on the first successful registration, is exchanged for long-lived agent credentials, and cannot be recovered after you leave the installation screen.

3. Choose an installation method

   IncidentFlow supports Helm, Argo CD, Terraform, Flux, and Kubernetes YAML manifests. The application generates the installation command for the selected cluster, environment, endpoints, and registration token.

4. Run the generated command

   Run the command generated by the IncidentFlow installation screen. It configures the Helm chart, agent namespace, platform API URL, agent gateway URL, cluster identifier, and one-time token.

5. Continue to verification

   Return to IncidentFlow and wait for the agent to connect. A successful installation transitions from Waiting to Connected.

Installation methods

The application generates the exact command for your cluster. The examples below show the shape of each method — the values in angle brackets are filled in by IncidentFlow. The <registration-token> value is always supplied by the IncidentFlow installation screen. Never copy a real token from documentation.

Helm is recommended for an initial installation. Use Argo CD or Flux when the cluster is managed through GitOps.

# Template only — obtain your complete, one-time-token command from IncidentFlow.
helm upgrade --install incidentflow-k8s-agent \
  oci://ghcr.io/incidentflow-io/charts/incidentflow-k8s-agent \
  --namespace incidentflow-agent \
  --create-namespace \
  --set platformUrl="<platform-url>" \
  --set gatewayUrl="<gateway-url>" \
  --set clusterName="<cluster-name>" \
  --set registrationToken="<registration-token>"

Next steps