kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Remove selector from Deployment default values (#8802) 

In recent versions of Kubernetes, selector field in DeploymentSpec is required and it'll not be filled with values from pod template. simple_deployment.yaml was already corrected and selector was added, here in this commit the content of the docs corrected to match this change.
pull/8805/merge
Eqbal Sarjami 2018-05-30 09:22:53 +04:30 committed by k8s-ci-robot
parent 7f2d1b3bf4
commit 4c2e4f825b
1 changed files with 2 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/en/docs/concepts/overview/object-management-kubectl/declarative-config.md
View File

@ -691,7 +691,7 @@ is lost.
The API server sets certain fields to default values in the live configuration if they are The API server sets certain fields to default values in the live configuration if they are
not specified when the object is created. not specified when the object is created.
Here's a configuration file for a Deployment. The file does not specify `strategy` or `selector`: Here's a configuration file for a Deployment. The file does not specify `strategy`:
{{< code file="simple_deployment.yaml" >}} {{< code file="simple_deployment.yaml" >}}
@ -721,7 +721,7 @@ spec:
minReadySeconds: 5 minReadySeconds: 5
replicas: 1 # defaulted by apiserver replicas: 1 # defaulted by apiserver
selector: selector:
matchLabels: # defaulted by apiserver - derived from template.metadata.labels matchLabels:
app: nginx app: nginx
strategy: strategy:
rollingUpdate: # defaulted by apiserver - derived from strategy.type rollingUpdate: # defaulted by apiserver - derived from strategy.type
@ -750,10 +750,6 @@ spec:
# ... # ...
``` ```
**Note:** Some of the fields' default values have been derived from
the values of other fields that were specified in the configuration file,
such as the `selector` field.
In a patch request, defaulted fields are not re-defaulted unless they are explicitly cleared In a patch request, defaulted fields are not re-defaulted unless they are explicitly cleared
as part of a patch request. This can cause unexpected behavior for as part of a patch request. This can cause unexpected behavior for
fields that are defaulted based fields that are defaulted based