Does the autonomous operator support spec.authSecret change after cluster creation?
I tried the next approaches:
- Update secret data for the existing cluster → nothing happened.
- Create a new secret (with a new name) and modify the cluster manifest. Got an error from operator admission controller
error: couchbaseclusters.couchbase.com “XXX” could not be patched: admission webhook “couchbase-fabric-couchbase-admission-controller.couchbase-fabric.svc” denied the request: validation failure list:
spec.authSecret in body cannot be updated
with kubectl replace -f
:
Error from server: error when replacing “/tmp/kubectl-edit-yasey.yaml”: admission webhook “couchbase-fabric-couchbase-admission-controller.couchbase-fabric.svc” denied the request: validation failure list:
spec.authSecret in body cannot be updated
What do you think about providing an option that provides user management capabilities with an operator in a declarative way with CR?
PS. operator’s code isn’t open-sourced right? Is there any change to see the code in the future?