Uploaded image for project: 'Couchbase Kubernetes'
  1. Couchbase Kubernetes
  2. K8S-3496

Operator should query K8S API to see if a pod is terminating before attempting to add back

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 2.6.4
    • None
    • None
    • None
    • 10 - Path of Vengeance
    • 3

    Description

      Because when a pod has been sigtermed, it can report itself as the same status as if it needs to be added back to the cluster, we should check with the k8s API and see if there is a terminating status. If so, we should skip the add back.

      Additionally, if we do not have a terminating status on the pod, we should allow 30 seconds (3 reconcile loops) in case the termination was facilitated outside of K8S control.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              usamah.jassat Usamah Jassat
              justin.ashworth Justin Ashworth
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty