The "Assigning Pods to Nodes" page did not mention nodeName, which, if
specified, takes priority over the methods discussed in the page. Add
description of nodeName and an example using it.
Address reviewer comments from @bsalamat and @liggitt, thanks!
* Official documentation on Poseidon/Firmament, a new multi-scheduler support for K8S. (#11752)
* Added documentation about Poseidon-Firmament scheduler
* Fixed some style issues.
* Udpated the document as per the review comments.
* Fixed some typos and updated the document
* Updated the document as per the review comments.
* Updated the document as per review comments. Added config details.
* Updated the document as per the latest review comments. Fixed nits
* Made changes as per latest suggestions.
* Some more changes added.
* Updated as per suggestions.
* Changed the release process section.
* SIG Docs edits
Small edits to match style guidelines.
* add plus to feature state
* capitalization
* revert feature state shortcode
since this is a Kubernetes extension, not a direct feature, it shouldn't use the regular feature state tagging.
* Update assign-pod-node.md
Use `kubectl get nodes --show-labels` to show the labels will not show the compelte labels like this:
```
root@master:/home# kubectl get nodes --show-labels
NAME STATUS ROLES AGE VERSION LABELS
master Ready master 41h v1.13.1 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=master,node-role.kubernetes.io/master=
server01 Ready <none> 41h v1.13.1 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,func=database,kubernetes.io/hostname=moon-server01
```
and the command `kubectl describe node "nodename" ` will show all labels the node have.
* Update assign-pod-node.md
* Update assign-pod-node.md
add a space before the new sentence
The LimitedResource type has the field "MatchScopes" as a sibling to
the field "Resource," but the YAML document in the example showed the
"MatchScopes" field as a child of the top-level Configuration
type. Correct the example to match the actual schema.
While we're here, swap the order of the "scopeName" and "operator"
fields used in the YAML, to make it clearer in infix style that the
operator binds the scope name to a (possibly empty) set of values.
* Update storage-classes.md
Fixed the formatting issues that were incorrectly showing the variables as hyperlink texts that resulted in 404 errors
* Update storage-classes.md
Incorporated the changes
* Update storage-classes.md
removed the </strong tag that was not required.
* Update storage-classes.md
replaced <em> with `.
* Remove old kube-dns note
* ExternalName IP clarification
* Add minor edits for clarity
* corrections
Co-Authored-By: nikopen <42466421+nikopen@users.noreply.github.com>
* OpenContrail -> Tungsten Fabric
OpenContrail has joined the Linux Foundation Networking Fund and rebranded as Tungsten Fabric to better reflect its open community engagement separate from its Juniper Network roots.
This edit updates the doc to reflect the name change and that Tungsten Fabric is a separate entity from Juniper's Contrail product.
* Include TF in the header
To further reinforce that Contrail and TF are different things.
Jai
Kenichi Omichi
joao brito junior
Suraj Deshmukh
Jintao Zhang
David Dooling
Chiradeep Vittal
Christian Posta
suratwant
Anvith KS
Jordan Liggitt
Marco Palladino
shibataka000
houjun
Namhoon Lee
Yaoyang
Roy Lenferink
zero
tuanvcw
sashaPM
j-u-e-f
Steven E. Harris
Maciej Szulik
Fladrif
Rajakavitha1
yanghaichao12
wangyamei
Becca Powell
DrmagicE
nuistzyw
Tim Hockin
Karen Bradshaw
Rajakavitha1
kohei
Niko Pen
Joseph Irving
Zefool
VM Brasseur
Babak "Bobby" Salamat
Louis
Yuexiao Wang
Nikhita Raghunath
Ismail Alidzhikov