The spec specified a "plain integer or as a fixed-point integer", but a fixed-point number is the correct terminology.
As such, 1.7Gi and 1Gi should both work.
* Revise Pod concept
Adapt the existing Pod documentation to suit the Docsy theme, by
promoting the Pod concept itself to /docs/concepts/workloads/pods/
Following on from this, update the Pod Lifecycle page to cover the
lifecycle of a Pod and follow on directly from the Pod concept,
for readers keen to understand things in detail.
This change also removes the automatic contents list from the Pod
overview page. Instead, the new page links to all the pages
inside the Pod section.
* Update links to Pod concept
Link to updated content
* Incorporate Pod concept suggestions
Co-authored-by: Celeste Horgan <celeste@cncf.io>
* Revise StatefulSet suggestion for Pod concept
Co-authored-by: Celeste Horgan <celeste@cncf.io>
Co-authored-by: Celeste Horgan <celeste@cncf.io>
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>
Savitha Raghunathan
Kubernetes Prow Robot
Alec Lombardo
zionwu
Jerry Park
Eric Briand
Qiming Teng
Tim Bannister
Oleg Atamanenko
Wei Huang
wojtekt
Maciej Szulik
Behzad
merishlalla
Richard Mokua
Artsiom Kaval
jqmichael
Karen Bradshaw
Soumith Kumar Mudugonda
Alex Wang
Adam
wawa0210
WangYun
Sylvain COULOMBEL
Adam Kaplan