Merge pull request #32774 from miteshskj/daemonset-review
Remove stale information about pod selector.pull/33121/head
commit
1613606a16
|
@ -76,9 +76,9 @@ A Pod Template in a DaemonSet must have a [`RestartPolicy`](/docs/concepts/workl
|
||||||
The `.spec.selector` field is a pod selector. It works the same as the `.spec.selector` of
|
The `.spec.selector` field is a pod selector. It works the same as the `.spec.selector` of
|
||||||
a [Job](/docs/concepts/workloads/controllers/job/).
|
a [Job](/docs/concepts/workloads/controllers/job/).
|
||||||
|
|
||||||
As of Kubernetes 1.8, you must specify a pod selector that matches the labels of the
|
You must specify a pod selector that matches the labels of the
|
||||||
`.spec.template`. The pod selector will no longer be defaulted when left empty. Selector
|
`.spec.template`.
|
||||||
defaulting was not compatible with `kubectl apply`. Also, once a DaemonSet is created,
|
Also, once a DaemonSet is created,
|
||||||
its `.spec.selector` can not be mutated. Mutating the pod selector can lead to the
|
its `.spec.selector` can not be mutated. Mutating the pod selector can lead to the
|
||||||
unintentional orphaning of Pods, and it was found to be confusing to users.
|
unintentional orphaning of Pods, and it was found to be confusing to users.
|
||||||
|
|
||||||
|
@ -91,8 +91,8 @@ The `.spec.selector` is an object consisting of two fields:
|
||||||
|
|
||||||
When the two are specified the result is ANDed.
|
When the two are specified the result is ANDed.
|
||||||
|
|
||||||
If the `.spec.selector` is specified, it must match the `.spec.template.metadata.labels`.
|
The `.spec.selector` must match the `.spec.template.metadata.labels`.
|
||||||
Config with these not matching will be rejected by the API.
|
Config with these two not matching will be rejected by the API.
|
||||||
|
|
||||||
### Running Pods on select Nodes
|
### Running Pods on select Nodes
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue