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

Example operator.yaml does not disable upgrade

    XMLWordPrintable

Details

    • Task
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • None
    • 1.0.0
    • documentation
    • None

    Description

      Upgrade in the operator is controlled by a CLI flag.

      For some reason if the CLI flag isn't specified then upgrade defaults to enabled.
      That means everybody should be running with the upgrade disable flag.

      Unfortunately the operator.yaml file we've shipped with 1.0 does not have the flag set, so everybody who is deploying the operator will have the upgrade feature enabled.
      Clearly this is a big problem as it introduces a lot of risk of hitting issues in every customer deployment (at least those who follow our docs!).

      Attachments

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

        Activity

          People

            simon.murray Simon Murray
            matt.carabine Matt Carabine
            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