Document all node conditions in k8s 1.2

This commit is contained in:
Rodrigo Campos 2016-06-12 15:11:20 -03:00
parent 73df8c3959
commit 6f26a1dcd5
1 changed files with 9 additions and 9 deletions

View File

@ -47,15 +47,15 @@ must have appropriate conditions, see below.
### Node Condition ### Node Condition
Node Condition describes the conditions of `Running` nodes. Currently the only The `conditions` field describes the status of all `Running` nodes.
node condition is Ready. The Status of this condition can be True, False, or
Unknown. True means the Kubelet is healthy and ready to accept pods. | Node Condition | Description |
False means the Kubelet is not healthy and is not accepting pods. Unknown |----------------|-------------|
means the Node Controller, which manages node lifecycle and is responsible for | `OutOfDisk` | `True` if insufficient free space on the node for adding new pods, otherwise `False` |
setting the Status of the condition, has not heard from the | `Ready` | `True` if the node is healthy ready to accept pods, `False` if the node is not healthy and is not accepting pods, and `Unknown` if the Node Controller has not heard from the node in the last 40 seconds |
node recently (currently 40 seconds).
Node condition is represented as a json object. For example, Node condition is represented as a JSON object. For example, the following response describes a healthy node:
the following conditions mean the node is in sane state: conditions mean the node is in sane state:
```json ```json
"conditions": [ "conditions": [