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

Allow more granular Couchbase Server upgrades

    XMLWordPrintable

Details

    • 1 - 2024 A New Dawn, 2 - 2024 Midnight Horizon, 3 - Droids in Distress
    • 1

    Description

      Couchbase Server upgrades are triggered by updating the image name field (couchbaseclusters.spec.image). The single value applies to the entire cluster, and there is no way to only upgrade a subset of the nodes.

      If we allow the image name to be (optionally) specified in multiple places in the Cluster definition (e.g. Server Groups, Server Classes), or with some other kind of node selector (potentially via an annotation), this would allow fine-grained control of which nodes would be upgraded, and crucially, would allow the Operator to be in a reconciled state after each round of upgrades.

      Attachments

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

        Activity

          People

            usamah.jassat Usamah Jassat
            malarky Chris Malarky
            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