OCI Oracle Kubernetes - Cluster Autoscaler: Nodes not getting "ready", Node State is active but stays unavailable for Kubernetes Node Condition
(Doc ID 2788162.1)
Last updated on JANUARY 09, 2024
Applies to:
Oracle Cloud Infrastructure - Oracle Container Engine for Kubernetes - Version N/A to N/AInformation in this document applies to any platform.
Symptoms
We have several nodes which are in "Node State" "active" but stay in "unavailable" for "Kubernetes Node Condition". This behavior is switching between the nodes.
Furthermore, the instance behind the "unavailable" "active" node is sometimes in state "Terminated".
Re-creating of the node pool helps for a short time period only.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |