Kubernetes integration
Kubernetes Agent
Connect a Kubernetes cluster to IncidentFlow with a read-only agent that opens an outbound connection — no inbound endpoint and no direct access from IncidentFlow to your Kubernetes API.
The Kubernetes Agent gives IncidentFlow investigations read-only access to cluster diagnostics — namespaces, pods, deployments, services, events, rollout status, and bounded pod logs — through workspace-scoped MCP tools.
How it connects
- The agent runs inside your cluster and establishes an outbound encrypted connection to IncidentFlow.
- IncidentFlow does not require an inbound endpoint or direct access to the Kubernetes API.
- Access is read-only diagnostics — the agent never mutates cluster resources.
Supported context
- Namespaces, pods, deployments, services, and events.
- Rollout status and recent pod failures.
- Bounded pod logs for approved namespaces.
Guides
Step 1
Installation
Register the agent, get a one-time token, and install with Helm, Argo CD, Terraform, Flux, or YAML.
Open guide ->Step 2
Configuration
Supported settings, namespace access, network requirements, and credential handling.
Open guide ->Step 3
Verification
Confirm the agent is connected from IncidentFlow, Kubernetes, and an MCP client.
Open guide ->Maintenance
Upgrade
Move to a new agent version safely — without a new registration token.
Open guide ->Support
Troubleshooting
Diagnose registration, connection, and permission problems by symptom.
Open guide ->