Improve Node, Taints, and Tolerations concepts

- Use glossary shortcodes in Node concept
  Add glossary tooltips to help new readers take in unfamiliar concepts.
- Move minion hint to glossary
  The page about Node need not mention the former name (minion): it has
  been many releases since the name change.
  Instead, add a hint to the full glossary definition.
- Use note shortcodes where appropriate
- Order node management section first in concept page
- Drop list of components that act on Nodes
  With Operators and CustomResourceDefinitions now common, plus the
  cluster API, it's less easy to give a definitive list of components that
  interacr with Node objects.
- Tidy old mentions of GA features for Node
- Give node tainting by condition its own section
- Introduce toleration concept before using it
- Mention version in TopologyManager feature state
- Other rewording
- Tidy Node condition table
- Explain SchedulingDisabled synthesized condition
- Drop details of supported versions for NodeRestriction
  Assume that cluster version is v1.13 or later

This commit is contained in:

Tim Bannister

2019-11-09 15:37:02 +00:00

parent ad4505dade

commit c5abd7704a

4 changed files with 212 additions and 185 deletions

content/en/docs/concepts/overview/components.md

+1 -1

View File

@@ -83,7 +83,7 @@ Node components run on every node, maintaining running pods and providing the Ku
 {{< glossary_definition term_id="kube-proxy" length="all" >}}
 ### Container Runtime
 ### Container runtime
 {{< glossary_definition term_id="container-runtime" length="all" >}}