Details
-
Improvement
-
Resolution: Duplicate
-
Major
-
None
-
16: Autoscaling/PE/Docs
-
1
Description
We are creating custom_server_tls_secret & custom_operator_tls_secret as part of helm chart which requests CouchbaseCluster.
Since the requests are triggered together and secret creation might take some milliseconds, admission controller fails the CouchbaseCluster request, complaining custom_server_tls_secret & custom_operator_tls_secret does not exists.
It is expected from the admission controller to behave the way other kubernetes objects work and should it wait for the secrets to get created.
—
apiVersion: "couchbase.com/v1"
kind: "CouchbaseCluster"
metadata:
...
spec:
...
tls:
static:
member:
serverSecret: custom_server_tls_secret
operatorSecret: {
}
Attachments
Issue Links
- relates to
-
K8S-2012 CouchbaseCluster request should wait for k8s objects creation - testing
- Closed