title: NEG is not attached to any BackendService with health checking
body: <p>I have a downtime on my app running on GKE when I deploy it using rolling update.</p>
  <pre><code>rollingUpdate:
        maxSurge: 25%
        maxUnavailable: 0
      type: RollingUpdate
  </code></pre>
  <p>I've checked the events on my pod and the last event is this one:</p>
  <pre><code>NEG is not attached to any Backend Service with health checking. Marking condition &quot;cloud.google.com/load-balancer-neg-ready&quot; to True.
  </code></pre>
  <p>On my pod I have a <code>livenessProbe</code> like this:</p>
  <pre><code>livenessProbe:
        failureThreshold: 1
        httpGet:
          path: /healthz
          port: http
          scheme: HTTP
        periodSeconds: 10
        successThreshold: 1
        timeoutSeconds: 1
  
  startupProbe:
            failureThreshold: 30
            httpGet:
              path: /healthz
              port: http
              scheme: HTTP
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 1
  </code></pre>
  <p>Checked my LB logs and found this:</p>
  <pre><code>{
  httpRequest: {
  latency: &quot;0.002246s&quot;
  remoteIp: &quot;myIP&quot;
  requestMethod: &quot;GET&quot;
  requestSize: &quot;37&quot;
  requestUrl: &quot;https://www.myurl/&quot;
  responseSize: &quot;447&quot;
  status: 502
  userAgent: &quot;curl/7.77.0&quot;
  }
  insertId: &quot;1mk&quot;
  jsonPayload: {3}
  logName: &quot;myproject/logs/requests&quot;
  receiveTimestamp: &quot;2022-02-15T15:30:52.085256523Z&quot;
  resource: {
  labels: {6}
  type: &quot;http_load_balancer&quot;
  }
  severity: &quot;WARNING&quot;
  spanId: &quot;b75e2f583a0e9e25&quot;
  timestamp: &quot;2022-02-15T15:30:51.270776Z&quot;
  trace: &quot;myproject/traces/32c488f48a392ac42358be0f&quot;
  }
  </code></pre>
  <p>And this is my deployment spec as asked:</p>
  <pre><code>spec:
    progressDeadlineSeconds: 600
    replicas: 1
    revisionHistoryLimit: 10
    selector:
      matchLabels:
        app.kubernetes.io/instance: app
        app.kubernetes.io/name: myname
    strategy:
      rollingUpdate:
        maxSurge: 25%
        maxUnavailable: 0
      type: RollingUpdate
    template:
      metadata:
        annotations:
          checksum/config: 4920135cd08336150d3184cc1af
        creationTimestamp: null
        labels:
          app.kubernetes.io/instance: app
          app.kubernetes.io/managed-by: Helm
          app.kubernetes.io/name: webapp-server
          app.kubernetes.io/part-of: webapp
          helm.sh/chart: myapp-1.0.0
      spec:
        containers:
        - env:
          - name: ENV VAR
            value: Hello
          envFrom:
          - configMapRef:
              name: myapp
          - secretRef:
              name: myapp-credentials
          image: imagelink
          imagePullPolicy: IfNotPresent
          livenessProbe:
            failureThreshold: 1
            httpGet:
              path: /healthz
              port: http
              scheme: HTTP
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 1
          name: node
          ports:
          - containerPort: 3000
            name: http
            protocol: TCP
          resources:
            limits:
              cpu: 500m
              memory: 512Mi
            requests:
              cpu: 250m
              memory: 256Mi
          startupProbe:
            failureThreshold: 30
            httpGet:
              path: /healthz
              port: http
              scheme: HTTP
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 1
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
        dnsPolicy: ClusterFirst
  </code></pre>
  <p>What can I change to avoid this downtime when performing a <code>rollingUpdate</code>?</p>