Document Pod lifecycle behavior edge-case when using a Recreate strategy. This should document the "unexpected" behavior discussed in kubernetes/kubernetes#58814
- 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
* Explain how to manage Kubernetes running on HUAWEI CLOUD provider.
* Update content/en/docs/concepts/cluster-administration/cloud-providers.md
Co-Authored-By: Kevin Wang <kevinwzf0126@gmail.com>
* Update content/en/docs/concepts/cluster-administration/cloud-providers.md
Co-Authored-By: Kevin Wang <kevinwzf0126@gmail.com>
Co-authored-by: Kevin Wang <kevinwzf0126@gmail.com>
- Note feature state for PodPreset
- Emphasize section on enabling PodPreset
- Omit version check
Assume that the reader has a supported version of Kubernetes that
includes PodPreset.
- List PodPreset as a task prerequisite
PodPreset is an alpha feature; you can't follow the task page unless
it's enabled.
* Reword resource limits section about ephemeral local storage
Co-Authored-By: Celeste Horgan <celeste@cncf.io>
* Move troubleshooting section to foot of page
It's OK to hyperlink to this section; in fact, I recommend it.
* Tweak section about monitoring key Pod resources
Monitoring reports memory use as well as CPU
* Fold 2 displayed headings into 1
Add a 2nd-level heading to cover two related headings, that I'm moving
to 3rd level. This change shortens the table of contents and still
leaves an entry there for readers to click on.
* Reword What's next section
* Revise punctuation
* Change page path to match title
Co-authored-by: Celeste Horgan <celeste@cncf.io>
Kevin Taylor