Kubernetes 当我编辑l7默认后端部署时,它将被还原

Kubernetes 当我编辑l7默认后端部署时,它将被还原,kubernetes,google-cloud-platform,google-kubernetes-engine,Kubernetes,Google Cloud Platform,Google Kubernetes Engine,几天前,我将我的GKE集群升级到Kubernetes 1.5.6。我过去能够将l7默认后端部署扩展到3个副本,并增加CPU资源限制,但现在我的更改似乎恢复为默认的1个副本和10m CPU限制 有趣的是,当我添加以下内容时: nodeSelector: cloud.google.com/gke-nodepool: default-pool 没问题 以下是当前部署清单: apiVersion: extensions/v1beta1 kind: Deployment metadata:

几天前,我将我的GKE集群升级到Kubernetes 1.5.6。我过去能够将
l7默认后端部署扩展到3个副本,并增加CPU资源限制,但现在我的更改似乎恢复为默认的1个副本和10m CPU限制

有趣的是,当我添加以下内容时:

nodeSelector:
    cloud.google.com/gke-nodepool: default-pool
没问题

以下是当前部署清单:

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "4"
    kubectl.kubernetes.io/last-applied-configuration: '{"kind":"Deployment","apiVersion":"extensions/v1beta1","metadata":{"name":"l7-default-backend","namespace":"kube-system","creationTimestamp":null,"labels":{"k8s-app":"glbc","kubernetes.io/cluster-service":"true","kubernetes.io/name":"GLBC"}},"spec":{"replicas":1,"selector":{"matchLabels":{"k8s-app":"glbc"}},"template":{"metadata":{"creationTimestamp":null,"labels":{"k8s-app":"glbc","name":"glbc"}},"spec":{"containers":[{"name":"default-http-backend","image":"gcr.io/google_containers/defaultbackend:1.0","ports":[{"containerPort":8080}],"resources":{"limits":{"cpu":"10m","memory":"20Mi"},"requests":{"cpu":"10m","memory":"20Mi"}},"livenessProbe":{"httpGet":{"path":"/healthz","port":8080,"scheme":"HTTP"},"initialDelaySeconds":30,"timeoutSeconds":5}}]}},"strategy":{}},"status":{}}'
  creationTimestamp: 2017-03-23T23:30:12Z
  generation: 9
  labels:
    k8s-app: glbc
    kubernetes.io/cluster-service: "true"
    kubernetes.io/name: GLBC
  name: l7-default-backend
  namespace: kube-system
  resourceVersion: "40149922"
  selfLink: /apis/extensions/v1beta1/namespaces/kube-system/deployments/l7-default-backend
  uid: a9772d26-1020-11e7-b9a8-42010af001d0
spec:
  replicas: 1
  selector:
    matchLabels:
      k8s-app: glbc
  strategy:
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 1
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        k8s-app: glbc
        name: glbc
    spec:
      containers:
      - image: gcr.io/google_containers/defaultbackend:1.0
        imagePullPolicy: IfNotPresent
        livenessProbe:
          failureThreshold: 3
          httpGet:
            path: /healthz
            port: 8080
            scheme: HTTP
          initialDelaySeconds: 30
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 5
        name: default-http-backend
        ports:
        - containerPort: 8080
          protocol: TCP
        resources:
          limits:
            cpu: 10m
            memory: 20Mi
          requests:
            cpu: 10m
            memory: 20Mi
        terminationMessagePath: /dev/termination-log
      dnsPolicy: ClusterFirst
      nodeSelector:
        cloud.google.com/gke-nodepool: default-pool
      restartPolicy: Always
      securityContext: {}
      terminationGracePeriodSeconds: 30
status:
  availableReplicas: 1
  conditions:
  - lastTransitionTime: 2017-04-13T19:19:35Z
    lastUpdateTime: 2017-04-13T19:19:35Z
    message: Deployment has minimum availability.
    reason: MinimumReplicasAvailable
    status: "True"
    type: Available
  observedGeneration: 9
  replicas: 1
  updatedReplicas: 1

如何成功扩展
l7默认后端