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

Release note helm long names problem

    XMLWordPrintable

Details

    • Page
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.2.0, 2.3.0, 2.2.2
    • None
    • None
    • 5: Helm, backup, Marketplace, 7: ARM arch? CMOS?, 9: R&D, leftovers
    • 1

    Description

      Document that you should not upgrade clusters with long names (long being defined as >255 characters including the domain+namespace+hostname-template). Fix is in 6.6.4. In 7.0 the limit is enforced.

      Idea is that a user needs to upgrade to 6.6.4 before upgrade to 7.

      Workaround is new cluster, replicate or backup/restore.

      If additional information is needed, check with Tommie McAfee

      Attachments

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

        Activity

          Had some discussion with Marks Polakovs who points out that the limit enforcement may have made it into 6.6.4 and/or 6.6.5.

          See https://github.com/couchbase/kv_engine/commit/9db024b87a35a633fcce8991cde09c441fd3bb08 and
          https://issues.couchbase.com/browse/MB-34280?focusedCommentId=557745&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-557745

          If so, we should raise priority on documenting this, as an upgrade from 6.6.3 to 6.6.5 could fail?

          ingenthr Matt Ingenthron added a comment - Had some discussion with Marks Polakovs who points out that the limit enforcement may have made it into 6.6.4 and/or 6.6.5. See https://github.com/couchbase/kv_engine/commit/9db024b87a35a633fcce8991cde09c441fd3bb08 and https://issues.couchbase.com/browse/MB-34280?focusedCommentId=557745&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-557745 If so, we should raise priority on documenting this, as an upgrade from 6.6.3 to 6.6.5 could fail?

          Discussed this a bit this morning with Simon Murray. We came up with some (not great) options.

          One option would be to go back and ask Couchbase Server to fix this. These names are long, but they're not exceedingly long and the original restriction for stats was based on key size for backwards compatibility with memcached ASCII protocol.

          ingenthr Matt Ingenthron added a comment - Discussed this a bit this morning with Simon Murray . We came up with some (not great) options. One option would be to go back and ask Couchbase Server to fix this. These names are long, but they're not exceedingly long and the original restriction for stats was based on key size for backwards compatibility with memcached ASCII protocol.

          Build couchbase-operator-2.3.0-254 contains couchbase-operator commit 52535c7 with commit message:
          K8S-2534: Document risk of upgrading w/long names

          build-team Couchbase Build Team added a comment - Build couchbase-operator-2.3.0-254 contains couchbase-operator commit 52535c7 with commit message: K8S-2534 : Document risk of upgrading w/long names

          Build couchbase-operator-2.3.0-278 contains couchbase-operator commit 4143fd0 with commit message:
          K8S-2534: Release note helm long names problem

          build-team Couchbase Build Team added a comment - Build couchbase-operator-2.3.0-278 contains couchbase-operator commit 4143fd0 with commit message: K8S-2534 : Release note helm long names problem

          Roo Thorp please verify and close this

          arunkumar Arunkumar Senthilnathan added a comment - Roo Thorp please verify and close this

          People

            roo.thorp Roo Thorp
            ingenthr Matt Ingenthron
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty