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

Unable to add server groups with pre-existing nodeselectors

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 2.4.0
    • None
    • operator
    • None
    • 30: Maintenance, CMOS, ARM, 31: Get Crackin on Kraken, 1 - Crack-a-lackin on Kraken, 2 - Uncle Kracken
    • 3

    Description

      The operator takes ServerGroup tags from the CouchbaseCluster spec and applies them as nodeSelectors on the Pod.  Under normal circumstances this simply results in multiple nodeSelectors being present on the Pod.  However in this case the 'example' selector is applied first like so:

        nodeSelector:
          node.example.com/role: couchbase

      Then when a new serverGroup is added, the Operator tries to convert this as yet another nodeSelector alongside this:

        nodeSelector:
          node.example.com/role: couchbase
          topology.kubernetes.io/zone: eu-central-1a 

      But we never get to this state because the Operator doesn't like that there is an existing nodeSelector(node.example) that was not created via serverGroup (bug). And so the fix is to not require pre-existing node selectors to conform to serverGroup style labels.

      Attachments

        Issue Links

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

          Activity

            People

              abhi.bose Abhi Bose (Inactive)
              tommie Tommie McAfee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty