问题原文
原帖链接 · Paddy · CC BY-SA 4.0
From Kubernetes documentation:
The selector field defines how the Deployment finds which Pods to manage.
But, when creating deployment, I already specify the pod template as part of the deployment. So, why will I need the selectors as well?
Is it supposed to be used like services, where pods are already being started separately, but later brought under the umbrella of Deployment to be managed together?
已采纳解答
原帖链接 · alexander.polomodov · CC BY-SA 4.0
Answer for this question we can find in section Deployments from kubernetes.io
So, why will I need the selectors as well?
Quotes below from documentation for k8s v 1.14
.spec.selectoris an required field that specifies a label selector for the Pods targeted by this deployment.
.spec.selectormust match.spec.template.metadata.labels, or it will be rejected by the API.In API version apps/v1, .spec.selector and .metadata.labels do not default to .spec.template.metadata.labels if not set. So they must be set explicitly. Also note that .spec.selector is immutable after creation of the Deployment in apps/v1.
A Deployment may terminate Pods whose labels match the selector if their template is different from .spec.template or if the total number of such Pods exceeds .spec.replicas. It brings up new Pods with .spec.template if the number of Pods is less than the desired number.
Pods are already being started separately, but later brought under the umbrella of Deployment to be managed together?
Simply speaking, No
Note: You should not create other pods whose labels match this selector, either directly, by creating another
Deployment, or by creating another controller such as aReplicaSetor aReplicationController. If you do so, the firstDeploymentthinks that it created these other pods.Kubernetesdoes not stop you from doing this. If you have multiple controllers that have overlapping selectors, the controllers will fight with each other and won’t behave correctly.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
