Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
K
k3s
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jacklull
k3s
Commits
fa10509a
Commit
fa10509a
authored
May 19, 2015
by
Chao Xu
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
update docs/node.md to v1beta3
parent
4cd424cf
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
15 additions
and
19 deletions
+15
-19
node.md
docs/node.md
+15
-19
No files found.
docs/node.md
View file @
fa10509a
...
@@ -62,28 +62,24 @@ After creation, Kubernetes will check whether the node is valid or not.
...
@@ -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
...
@@ -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": "v1beta
1
", "unschedulable": true}'
kubectl update nodes 10.1.2.3 --patch='{"apiVersion": "v1beta
3
", "unschedulable": true}'
```
```
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment