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

XDCR Remote Clusters should check for old names for persistence secret values

    XMLWordPrintable

Details

    • 5 - Forces of Destiny
    • 2

    Description

      {}In 2.5.0 we introduced a suffix for xdcr names that is "-operator-managed", However, it does not appear that we updated the persistence secret with the appropriate name.

      This causes reconciliation to fail, as it cannot access the appropriate keys in the persistence secret.

      We should:

      1) Check to see if the new keys are present, if so use them

      2) If new keys are not present, check for old keys that are missing the suffix, if so update them to the new keys

      3) If they keys do not exist at all, we should add them, or fail in a way that does not block reconciliation.

       

      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:

                PagerDuty