Upgrade the Kubernetes Agent

Upgrade the IncidentFlow Kubernetes Agent to receive reliability improvements, security updates, and new diagnostic capabilities.

Before upgrading

1. Check the currently running agent version.
2. Review the release notes for breaking configuration changes.
3. Export or review the current Helm values or GitOps configuration.
4. Confirm that the agent is connected and healthy.
5. Confirm that the target version supports your Kubernetes version.

Upgrade with Helm

Upgrade the existing release using the same OCI chart source, release name, and namespace.

helm upgrade incidentflow-k8s-agent \
  oci://ghcr.io/incidentflow-io/charts/incidentflow-k8s-agent \
  --namespace incidentflow-agent \
  --version "<target-chart-version>" \
  --reuse-values

Pin a specific chart or application version in production — avoid an unreviewed automatic upgrade to an unspecified latest version. After applying the upgrade, wait for the deployment rollout to complete.

Upgrade with GitOps

For Argo CD or Flux:

• update the pinned chart or image version in Git;
• review the generated manifest changes;
• merge the change;
• wait for reconciliation;
• verify the deployment rollout and agent connection.

Verify the upgrade

After upgrading:

• confirm the deployment is available;
• confirm all pods are ready;
• confirm the agent reconnects;
• check the reported agent version;
• inspect recent logs;
• call k8s_agent_status;
• verify that diagnostic tools still return the expected namespaces.

See Verification for the full checklist.

Rollback

If the upgraded agent cannot connect or becomes unhealthy, roll back to the previously known working version.

helm rollback incidentflow-k8s-agent \
  --namespace incidentflow-agent

After rollback, verify the deployment, connection, heartbeat, and reported version again.