cri-o is unable to handle termination of containers and moves the node to NotReady
Issue
- If the containers are exiting with a SIGTERM or during app deployments when the previous versions are not terminated gracefully, the node is set to Notready status for a brief period.
- This happens when the container engine used is cri-o
Environment
- Openshift Container Platform v3.11.82
- crio version 1.11.11-1.rhaos3.11.git474f73d.el7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.