Pod Restarted During Node Maintenance

If a pod restarted without any change on your side, a planned node upgrade is the likely cause. This article explains why and how to avoid it.

When CTO2B performs node upgrades, nodes are drained gracefully — pods are
evicted and rescheduled onto other nodes. A Component running a single replica
will see a brief restart while that happens.

CTO2B notifies you at least 48 hours before a planned maintenance window. If a
workload cannot tolerate a restart, run at least two replicas and raise a
request about configuring a disruption budget for it.

Still having issues?

Raise a request with the namespace, the Component name, the pod status, and what
you have already tried.

Related articles

• Workload Management — resource requests, limits and health checks
• Troubleshooting Common Issues — find your symptom