Change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: Proposed Solution: Page to Update: <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--
The glossary does not contain a definition for Kubernetes object, or Kubernetes master.
Good point /priority backlog /language en We could possibly add a “master” for a synonym for “control plane”, and then in the entry for “control plane” explain the similarities and differences between the two terms.
/help
I'll work on that! /remove-help /assign
and What about creating a entry explaining the concept and listing and as most common values used on it?
Hmm. That term “master” has nuances (it's not as controversial as “slave”, but the implication is still there). Newer thinking seems to favor “control plane” rather than “master”. So you can have nodes that also run the control plane. Does that help guide how to approach this?
I understand your point, but may tools still uses and for the label (ex. ). Also, looks like we already have covered in the glossary (). What about to refactor entry, explaining that nodes can also have a role label, and these are the most common values (and linking to )?
the "master" node role is exclusive to deployers like kubeadm (+some others) and has been excluded from core k8s.

Discussion:
- fundamental --- The container orchestration layer that exposes the API and interfaces to define, deploy, and manage the lifecycle of containers. <ins> <!--more--> This layer is composed by many different components, such as (but not restricted to): * {{< glossary_tooltip text="etcd" term_id="etcd" >}} * {{< glossary_tooltip text="API Server" term_id="kube-apiserver" >}} * {{< glossary_tooltip text="Scheduler" term_id="kube-scheduler" >}} * {{< glossary_tooltip text="Controller Manager" term_id="kube-controller-manager" >}} * {{< glossary_tooltip text="Cloud Controller Manager" term_id="cloud-controller-manager" >}} These components can be run as traditional operating system services (daemons) or as containers. The hosts running these components were historically called {{< glossary_tooltip text="masters" term_id="master" >}}. </ins>  No newline at end of file

<ins> --- title: Master id: master date: 2020-04-16 short_description: > Legacy term, used as synonym for nodes running the control plane. aka: tags: - fundamental --- Legacy term, used as synonym for {{< glossary_tooltip text="nodes" term_id="node" >}} hosting the {{< glossary_tooltip text="control plane" term_id="control-plane" >}}. <!--more--> The term is still being used by some provisioning tools, such as {{< glossary_tooltip text="kubeadm" term_id="kubeadm" >}}, and managed services, to {{< glossary_tooltip text="label" term_id="label" >}} {{< glossary_tooltip text="nodes" term_id="node" >}} with `kubernetes.io/role` and control placement of {{< glossary_tooltip text="control plane" term_id="control-plane" >}} {{< glossary_tooltip text="pods" term_id="pod" >}}. </ins>  No newline at end of file