github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-03 17:30:00 +00:00
Code Issues Projects Releases Wiki Activity

update docs/node.md to v1beta3

Browse Source
This commit is contained in:
Chao Xu 2015-05-19 10:01:41 -07:00
parent 4cd424cfb4
commit fa10509a7f
1 changed files with 15 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
docs/node.md
View File

@ -62,28 +62,24 @@ After creation, Kubernetes will check whether the node is valid or not.
For example, if you try to create a node from the following content: For example, if you try to create a node from the following content:
```json ```json
{ {
"id": "10.1.2.3", "kind": "Node",
"kind": "Minion", "apiVersion": "v1beta3",
"apiVersion": "v1beta1", "metadata": {
"resources": { "name": "10.240.79.157",
"capacity": { "labels": {
"cpu": 1000, "name": "my-first-k8s-node"
"memory": 1073741824 }
}, }
},
"labels": {
"name": "my-first-k8s-node",
},
} }
``` ```
Kubernetes will create a `Node` object internally (the representation), and Kubernetes will create a `Node` object internally (the representation), and
validate the node by health checking based on the `id` field: we assume `id` validate the node by health checking based on the `metadata.name` field: we
can be resolved. If the node is valid, i.e. all necessary services are running, assume `metadata.name` can be resolved. If the node is valid, i.e. all necessary
it is eligible to run a `Pod`; otherwise, it will be ignored for any cluster services are running, it is eligible to run a `Pod`; otherwise, it will be
activity, until it becomes valid. Note that Kubernetes will keep invalid node ignored for any cluster activity, until it becomes valid. Note that Kubernetes
unless explicitly deleted by client, and it will keep checking to see if it will keep invalid node unless explicitly deleted by client, and it will keep
becomes valid. checking to see if it becomes valid.
Currently, there are two agents that interacts with Kubernetes node interface: Currently, there are two agents that interacts with Kubernetes node interface:
Node Controller and Kube Admin. Node Controller and Kube Admin.
@ -123,7 +119,7 @@ Admin can choose to make the node unschedulable using `kubectl`. Unscheduling th
will not affect any existing pods on the node but it will disable creation of will not affect any existing pods on the node but it will disable creation of
any new pods on the node. Node unschedulable example: any new pods on the node. Node unschedulable example:
``` ```
kubectl update nodes 10.1.2.3 --patch='{"apiVersion": "v1beta1", "unschedulable": true}' kubectl update nodes 10.1.2.3 --patch='{"apiVersion": "v1beta3", "unschedulable": true}'
``` ```