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

Must fix versioning situation for couchbase-operator-backup



    • Bug
    • Resolution: Fixed
    • Critical
    • None
    • None
    • operator-backup
    • None
    • 18: PE/Tasks/Docs
    • 1


      The current versioning scheme for couchbase-operator-backup is different than every other product in the company, and it is causing significant difficulties and confusion for product releases.

      • We have to have a different manifest for every Server base version we want to support. This won't scale.
      • The internal build numbers are exposed to customers as we have no other way of disambiguating different "6.6.0" etc builds. That is, the final customer image is eg. couchbase/operator-backup:6.6.0-102 where 102 is the internal build number. This is more difficult than it should be to keep track of.
      • Black Duck scans are nearly impossible because we cannot possibly scan every build number as a separate product. Our current solution is to scan all "6.6.0" builds as the same product/version, which matches every other product. But this doesn't actually make sense since multiple "6.6.0" releases are already GA and we get updated scans for each 6.6.0 build.

      My understanding is that the fundamental reason for this confused state is that cbbackupmgr is not guaranteed to work with any Server version other than the one it was built with. Is that accurate? Is there work underway to correct that situation?


        Issue Links

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



              ceej Chris Hillery
              ceej Chris Hillery
              0 Vote for this issue
              5 Start watching this issue



                Gerrit Reviews

                  There are no open Gerrit changes