Merge pull request #549 from mwhooker/patch-1
mark node phase as deprecated
This commit is contained in:
+1
-13
@@ -36,19 +36,7 @@ The usage of these fields varies depending on your cloud provider or bare metal
|
|||||||
|
|
||||||
### Node Phase
|
### Node Phase
|
||||||
|
|
||||||
Node Phase is the current lifecycle phase of node, one of `Pending`,
|
Deprecated: Node Phase is no longer used
|
||||||
`Running` and `Terminated`.
|
|
||||||
|
|
||||||
* Pending: New nodes are created in this state. A node stays in this state until it is configured.
|
|
||||||
|
|
||||||
* Running: Node has been configured and the Kubernetes components are running
|
|
||||||
|
|
||||||
* Terminated: Node has been removed from the cluster. It will not receive any scheduling requests,
|
|
||||||
and any running pods will be removed from the node.
|
|
||||||
|
|
||||||
Node with `Running` phase is necessary but not sufficient requirement for
|
|
||||||
scheduling Pods. For a node to be considered a scheduling candidate, it
|
|
||||||
must have appropriate conditions, see below.
|
|
||||||
|
|
||||||
### Node Condition
|
### Node Condition
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user