Details
-
Page
-
Resolution: Fixed
-
Minor
-
None
-
1
Description
https://docs.couchbase.com/operator/1.2/tls.html
In that paragraph
Create a server wildcard certificate and key to be used on Couchbase Server pods. The Operator/clients will access the pods via Kubernetes services (cb-example-0000.cb-example.default.svc, for example) so this needs to be in the SAN list in order for a client to verify the certificate belongs to the host that is being connected to. To this end, we add in a --subject-alt-name, this can be specified multiple times in case your client uses a different method of addressing. The key/certificate pair can be found in pki/private/couchbase-server.key and pki/issued/couchbase-server.crt and used as pkey.pem and chain.pem, respectively, in the serverSecret.
it mentioned the pkey.pem as a rename of cochbase-server.key.
It seems like it is supposed to be pkey.key, and not as written
Attachments
Issue Links
- has to be started together with
-
K8S-1925 Incorrect mention of pkey.pem in the K8s TLS configuration docs
- Closed