From df4a93598e138e5ee2740bd83f886b076035f853 Mon Sep 17 00:00:00 2001 From: Matthew Hooker Date: Fri, 20 May 2016 15:19:35 -0700 Subject: [PATCH] mark node phase as deprecated I'm not sure on what the best wording for this should be, but `Node Phase` is no longer populated, and so the docs should say so. @random-liu on slack/#sig-node told me that they believed node phase was unused. cc @dawnchen --- docs/admin/node.md | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/docs/admin/node.md b/docs/admin/node.md index 13332012b8..2cdc96366c 100644 --- a/docs/admin/node.md +++ b/docs/admin/node.md @@ -31,19 +31,7 @@ The usage of these fields varies depending on your cloud provider or bare metal ### Node Phase -Node Phase is the current lifecycle phase of node, one of `Pending`, -`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. +Deprecated: Node Phase is no longer used ### Node Condition