Details
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
- has to be done before
-
K8S-2821 Review node selector and server group tests
- Closed
For Gerrit Dashboard: K8S-2791 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
178847,25 | K8S-2791: Unable to add server groups with pre-existing nodeselectors | master | couchbase-operator | Status: MERGED | +2 | +1 |