Revise glossary entry for node #48688
Conversation
... and to clarify use regarding worker node, which is often used interchangeably with node, and the use of. the term control plane node within the documentation.
k8s-ci-robot
added
the
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
size/S
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
/retitle Revise glossary entry for node |
k8s-ci-robot
changed the title
| @@ -4,17 +4,19 @@ id: node | |||
| date: 2018-04-12 | |||
| full_link: /docs/concepts/architecture/nodes/ | |||
| short_description: > | |||
| A node is a worker machine in Kubernetes. | |||
| A node is a machine within a Kubernetes cluster that hosts pods. | |||
There was a problem hiding this comment.
Keeping it short:
| A node is a machine within a Kubernetes cluster that hosts pods. | |
| Machine within a Kubernetes cluster that hosts pods. |
|
|
||
| <!--more--> | ||
|
|
||
| A worker node may be a VM or physical machine, depending on the cluster. It has local daemons or services necessary to run {{< glossary_tooltip text="Pods" term_id="pod" >}} and is managed by the control plane. The daemons on a node include {{< glossary_tooltip text="kubelet" term_id="kubelet" >}}, {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}}, and a container runtime implementing the {{< glossary_tooltip text="CRI" term_id="cri" >}} such as {{< glossary_tooltip term_id="docker" >}}. | ||
| A node may be a VM or physical machine, depending on the cluster. The term *node* is often used as an abbreviation for the term *worker node*, given that most nodes host {{< glossary_tooltip text="workloads" term_id="workload" >}}. However it is possible for nodes to host control plane components within pods, and these nodes may be referred to as control plane nodes. Thus it's possible for a node to be both a worker node and a control plane node, though this is less likely in production environments, as having a machine co-host workloads and control plane components goes against best practices. |
There was a problem hiding this comment.
No; this would be misleading. A node can't be a worker node (defined as doesn't host any control plane components) and at the same time also be a control plane node (defined as runs the kubelet combined with hosts at least some control plane components).
There was a problem hiding this comment.
The typical way to identify worker nodes is to negatively select on node-role.kubernetes.io/control-plane="true".
| In early Kubernetes versions, Nodes were called "Minions". | ||
| Each node is managed by the {{< glossary_tooltip text="control plane" term_id="control-plane" >}} and has the local daemons or services necessary to run pods. The daemons on a node include {{< glossary_tooltip text="kubelet" term_id="kubelet" >}}, {{< glossary_tooltip text="kube-proxy" term_id="kube-proxy" >}}, and a container runtime implementing the {{< glossary_tooltip text="CRI" term_id="cri" >}} such as {{< glossary_tooltip term_id="docker" >}}. | ||
|
|
||
| In early Kubernetes versions, worker nodes were called "Minions". |
There was a problem hiding this comment.
(nit / optional tweak)
| In early Kubernetes versions, worker nodes were called "Minions". | |
| In early versions of Kubernetes, nodes were called _minions_. |
There was a problem hiding this comment.
The node concept (and Node API) superseded the Minion concept (and Minion API).
Around 9 years ago, kubectl get minions still worked.
|
@TransitivityPaul would you be willing to move this PR forward? A maintainer may close it if the PR is still waiting for feedback to be incorporated. |
... and to clarify use regarding worker node, which is often used interchangeably with node, and the use of. the term control plane node within the documentation.
Description
Issue
Closes: #