kubectl run starting from 1.18 is creating only Pods and there is no option to
create any other resource. Users should be using kubectl create
commands instead. This update the documentation in all those places
where kubectl create should be used instead or changes description to
reflect the situation.
The existing ConfigMap concept incorrectly states that you must use
different ConfigMap objects if you want to configure both environment
variables and file-like configuration items at the same time.
Reword to give the correct advice.
Add quotation marks around the value of the key "player_initial_lives" in configuration file of the ConfigMap called "game-demo". Otherwise, kubectl version 1.18 gives the following error with the command "kubectl apply -f game-demo-configMap.yaml"
Error from server (BadRequest): error when creating "game-demo-configMap.yaml": ConfigMap in version "v1" cannot be handled as a ConfigMap: v1.ConfigMap.Data: ReadString: expects " or n, but found 3, error found in #10 byte of ...|l_lives":3,"ui_prope|..., bigger context ...|player.maximum-lives=5\n","player_initial_lives":3,"ui_properties_file_name":"user-interface.propert|...
1. The example is using YAML which supports octal notation. Updated the corresponding doc.
2. Clarified we need to follow the symlink to find the correct file mode.
* Moved "Assigning Pods to Nodes" article to Concepts -> Scheduling and Eviction
* Moved "Taints and Tolerations" article to Concepts -> Scheduling and Eviction
* Updated weight of the "Kubernetes Scheduler" article so it appears first
* Updated redirects
* Replaced links to "Assigning Pods to Nodes" and "Taints and Tolerations" articles
to avoid redirects.
Signed-off-by: Adam Kaplan <adam.kaplan@redhat.com>
- 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
Kubernetes Prow Robot
Wei Huang
Savitha Raghunathan
Jerry Park
wojtekt
Tim Bannister
Maciej Szulik
Behzad
merishlalla
Richard Mokua
Artsiom Kaval
jqmichael
Karen Bradshaw
Soumith Kumar Mudugonda
Alex Wang
Adam
wawa0210
WangYun
Sylvain COULOMBEL
Adam Kaplan
willise
Joel
ViBiOh
Cristobal Dabed
Cristobal Dabed
Chris Friesen
colstuwjx