# Kubernetes incident handover

## Incident control
- Incident ID:
- Severity and customer impact:
- Commander and current operator:
- Handover from / to:
- Handover time in UTC:
- Incident channel and evidence location:

## Exact scope
- Cluster and context:
- Region / environment:
- Namespaces and workloads:
- Affected versions or deployment revisions:
- Dependencies currently implicated:

## Current state
- Confirmed healthy components:
- Confirmed failed or degraded components:
- Last known-good timestamp:
- Current traffic, error and saturation signals:
- Recovery or mitigation currently in effect:

## Evidence retained
- Kubernetes events and timestamps:
- Pod, node and controller observations:
- Relevant logs, metrics and traces:
- Recent deployments or infrastructure changes:

## Actions already taken
- Command or change:
- Operator and timestamp:
- Observed result:
- Was it reverted or left in place?:

## Decision boundary
- Confirmed facts:
- Active hypotheses:
- Actions that must not be repeated:
- Unsafe actions or unavailable rollback paths:
- Next validation step and expected signal:
- Escalation or rollback trigger:

## Ownership acknowledgement
- Receiving operator:
- Questions resolved before transfer:
- Accepted at UTC:
- Next update due: