It should be `spec.template.spec.affinity` instead of `spec.template.affinity`.
```
$ explain deploy.spec.template.spec.affinity
GROUP: apps
KIND: Deployment
VERSION: v1
FIELD: affinity <Affinity>
...
```
```
$ k explain deploy.spec.template.affinity
GROUP: apps
KIND: Deployment
VERSION: v1
error: field "affinity" does not exist
```
* add: the doc for matchLabelKeys/mismatchLabelKeys in pod (anti)affinity
* fix based on reviews
* add the explanation for labelSelector
* address the review
* removes "tmpfs is cleared on node reboot"
I believe the statement is confusing since we are in the emptyDir section of the documentation.
If a Node is restarted then all pods that resided on that node will be rescheduled onto another Node. Rescheduled pods will have an empty volume whether you choose emptyDir.medium "Memory" or not.
* removes bad comma
* improves memory limit description
Co-authored-by: Tim Bannister <tim@scalefactory.com>
* removes incorrect explanation for topologyKey in an affinity or anti-affinity rule (#1)
The existing text does not make sense to me.
There is no zone "V" or "R" in the example.
I have changed the text to be consistent with top answer here which seems to make more sense: https://stackoverflow.com/questions/72240224/what-is-topologykey-in-pod-affinity
* gives more context to node label configuration
* manually wraps text and replaces absolute links with relative ones
* Update assign-pod-node.md
---------
Co-authored-by: Tim Bannister <tim@scalefactory.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Less visual space compared to the original approach, but still shows
which labels you can expect to find set on a node.
Co-authored-by: Ritikaa96 <ritika@india.nec.com>
* Added section in the docs about the behaviour of operator in the node and pod affinity docs
* Fixes from review
* Fixed podAffinity and added note about non-integer values
* Fixes from review
* Fixed review comments
* Fixes from review
* Fixed deprecated comment in scheduling-eviction/assign-pod-node.md regarding example pods/pod-with-affinity-anti-affinity.yaml
* Changed the example to a more appropriate one
Either we correct the code from pods/pod-with-node-affinity.yaml to match the description about the rules that apply or we correct the description in order to match the pods/pod-with-node-affinity.yaml
This PR updates the scheduler configuration YAML snippets to use the 'v1beta3' version API. 'v1beta1' is gone and not recommended. We don't have config API reference for 'v1beta1' now.