- 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
* Rename `docs/concepts/scheduling` to `docs/concepts/scheduling-eviction`
* Retitle concept header to "Scheduling and Eviction"
* Update redirects
* Update internal links (en only)
Part of proposal #19081
Signed-off-by: Adam Kaplan <adam.kaplan@redhat.com>
* Use Control Plane instead of Master
* improve image. The SVG was not matching the PNG, so I basically had to re-create it from scratch. I kept the visual similarities as mush as possible
* remove tautological phrase
* fix glossary references as well
* improve cluster glossary to move from Master to Control Plane
* improve english form
* Rename architecture section
"Kubernetes" goes without saying. This section is mainly talking about
cluster architecture, so make the title match that.
* Introduce “cluster” before Cluster Architecture section
Make sure the reader can learn what a cluster is before they read about
elements of cluster architecture.
* Add scheduler concept page
* Rename scheduling overview
* Fix non-ASCII colon symbols
* Reword scheduler concept page
* Move scheduler performance tuning into scheduling
* Signpost from overview to kube-scheduler, etc
* Add whatsnext section to scheduler concept
* Restructure scheduling concept
Now there's a concept page for scheduling, some of the details
in the performance tuning page can have a better home.
* Omit link to (unwritten) scheduling extensions page
* Drop deprecated / superseded filtering rules
This patch promotes re-use of the existing kube-proxy glossary
definition by referencing it from overview/components.md. Similarly, we
move the definition of Container Runtime into a new glossary definition
so that other pages may refer to it.
Kubernetes Prow Robot
Cristian Klein
slashr
Tim Bannister
Karen Bradshaw
Fabio Alessandro Locati
Adam Kaplan
Supriya Sirbi
Himanshu Pandey
Jay Pipes
王(Wang)
Zoltan
June Yi
hidekazuna
Jai
Takuya Tokuda
Bjørn Erik Pedersen