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

Always attempt to recreate persistence secret name for new cluster

    XMLWordPrintable

Details

    • 9 - Krakend, 10 - Krackeverlasting, 1 - Levianthanning, 2 - LeVIAthan or LeviaTHAN
    • 0

    Description

      Currently the persistence secrets have exact same name as the cluster.  This can cause problems if a cluster is quickly recreated as persistence secret from the previous instance could be reused resulting in unexpected behavior.

      Since we never want to delete/overwrite the persistence secret we will need to wait to see if it's being deleted, then recreate (with retry) until we are able to create a new one within cluster.newCluster (cluster.go). 

      Attachments

        Issue Links

          blocks

          Page - A new page either standalone or within a series of pages must be added K8S-3052 2.4.1 Release Notes

          • Major - Major loss of function.
          • Resolved
          For Gerrit Dashboard: K8S-2934
          # Subject Branch Project Status CR V
          185152,3 K8S-2934: check for existence of old persistence secret before creating a new one/avoid reuse master couchbase-operator Status: MERGED +2 +1

          Activity

            People

              abhi.bose Abhi Bose (Inactive)
              tommie Tommie McAfee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty