下面给出了两个部署，它们只在名称上推迟。

apiVersion: apps/v1
kind: Deployment
metadata:
  name: deployment-1
spec:
  replicas: 2
  selector:
    matchLabels:
      app: myapp
  template:
    metadata:
      labels:
        app: myapp
    spec:
      containers:
      - name: myapp
        image: nginx:1.11
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: deployment-2
spec:
  replicas: 2
  selector:
    matchLabels:
      app: myapp
  template:
    metadata:
      labels:
        app: myapp
    spec:
      containers:
      - name: myapp
        image: nginx:1.11

应用上述方法将生成两个部署和两个复制集。

kubectl get replicasets
NAME                      DESIRED   CURRENT   READY   AGE
deployment-1-8684779b48   2         2         2       34m
deployment-2-8684779b48   2         2         2       34m

复制集的描述如下-

kubectl describe replicaset deployment-1
Name:           deployment-1-8684779b48
Namespace:      default
Selector:       app=myapp,pod-template-hash=8684779b48
Labels:         app=myapp
                pod-template-hash=8684779b48
Annotations:    deployment.kubernetes.io/desired-replicas: 2
                deployment.kubernetes.io/max-replicas: 3
                deployment.kubernetes.io/revision: 1
Controlled By:  Deployment/deployment-1
Replicas:       2 current / 2 desired
Pods Status:    2 Running / 0 Waiting / 0 Succeeded / 0 Failed
Pod Template:
  Labels:  app=myapp
           pod-template-hash=8684779b48
  Containers:
   myapp:
    Image:        nginx:1.11
    Port:         <none>
    Host Port:    <none>
    Environment:  <none>
    Mounts:       <none>
  Volumes:        <none>
Events:
  Type    Reason            Age   From                   Message
  ----    ------            ----  ----                   -------
  Normal  SuccessfulCreate  35m   replicaset-controller  Created pod: deployment-1-8684779b48-ngm5l
  Normal  SuccessfulCreate  35m   replicaset-controller  Created pod: deployment-1-8684779b48-5fz94
  Normal  SuccessfulCreate  34m   replicaset-controller  Created pod: deployment-1-8684779b48-svphx
  Normal  SuccessfulCreate  33m   replicaset-controller  Created pod: deployment-1-8684779b48-q7lh5

还有-

kubectl describe replicaset deployment-2
Name:           deployment-2-8684779b48
Namespace:      default
Selector:       app=myapp,pod-template-hash=8684779b48
Labels:         app=myapp
                pod-template-hash=8684779b48
Annotations:    deployment.kubernetes.io/desired-replicas: 2
                deployment.kubernetes.io/max-replicas: 3
                deployment.kubernetes.io/revision: 1
Controlled By:  Deployment/deployment-2
Replicas:       2 current / 2 desired
Pods Status:    2 Running / 0 Waiting / 0 Succeeded / 0 Failed
Pod Template:
  Labels:  app=myapp
           pod-template-hash=8684779b48
  Containers:
   myapp:
    Image:        nginx:1.11
    Port:         <none>
    Host Port:    <none>
    Environment:  <none>
    Mounts:       <none>
  Volumes:        <none>
Events:
  Type    Reason            Age   From                   Message
  ----    ------            ----  ----                   -------
  Normal  SuccessfulCreate  36m   replicaset-controller  Created pod: deployment-2-8684779b48-w4zws
  Normal  SuccessfulCreate  36m   replicaset-controller  Created pod: deployment-2-8684779b48-nfzxb

在上面，两个副本集都有相同的选择器值Selector: app=myapp,pod-template-hash=8684779b48现在这两个副本集如何确定下面的哪些pod属于它们，因为它们都有相同的标签-

kubectl get pods -l app=myapp -l pod-template-hash=8684779b48
NAME                            READY   STATUS    RESTARTS   AGE
deployment-1-8684779b48-q7lh5   1/1     Running   0          38m
deployment-1-8684779b48-svphx   1/1     Running   0          39m
deployment-2-8684779b48-nfzxb   1/1     Running   0          40m
deployment-2-8684779b48-w4zws   1/1     Running   0          40m

复制集输出中的Events:信息是否会被使用。否则有人能提供一些信息吗？