Verify the Kubernetes Agent

Verify the installation from IncidentFlow, from Kubernetes, and from an MCP client.

Check the IncidentFlow application

Open IncidentFlow → Kubernetes Agents and select the cluster. The expected state is:

• connection status: Connected;
• agent status: Online;
• cluster identifier matches the installed cluster;
• the latest heartbeat is recent;
• the reported agent version is the expected version.

Check the Kubernetes workload

Confirm that the agent deployment is available:

kubectl get deployment,pods \
  --namespace incidentflow-agent

Inspect the rollout:

kubectl rollout status deployment/incidentflow-k8s-agent \
  --namespace incidentflow-agent

The deployment should complete successfully and the agent pod should be Running and Ready.

Check recent agent logs

kubectl logs \
  --namespace incidentflow-agent \
  deployment/incidentflow-k8s-agent \
  --tail=100

The logs should show a successful registration or gateway connection. They should not contain authentication loops, permission errors, or repeated connection failures.

Verify through MCP

Call k8s_agent_status. A healthy response contains:

{
"status": "connected",
"healthy": true
}

Then call k8s_connection_health to verify the end-to-end connection, and k8s_list_namespaces to confirm the expected read-only visibility.

Verification checklist

• The deployment rollout is complete.
• The agent pod is ready.
• IncidentFlow shows the agent as connected.
• The latest heartbeat is recent.
• The reported cluster and agent version are correct.
• MCP Kubernetes tools return the expected cluster context.
• The agent has no Kubernetes write permissions.