Critical Description
Attempting to use exporter with a TLS configured cluster fails because the appropriate cert/key/ca's aren't being mounted into the side car and passed along to the exporter application.
The fix for this is straightforward, although there is room for nuance with the Native TLS style of secrets as we may have multiple Root CA's and so questions remain as to how would this should work in conjunction with the exporter.
Attachments
| For Gerrit Dashboard: K8S-2795 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 178070,6 | K8S-2795: Adds generic tls cert for sidecar use | 2.3.x | couchbase-operator | Status: MERGED | +2 | +1 |
Activity
Build couchbase-operator-2.3.1-120 contains couchbase-operator commit 95d2add with commit message:
K8S-2795: Adds generic tls cert for sidecar use
Build couchbase-operator-2.4.0-110 contains couchbase-operator commit 95d2add with commit message:
K8S-2795: Adds generic tls cert for sidecar use
Some notion of default_client_secret then and some future notion of related secrets. That said, if someone wants very specific mTLS, then we should probably just specify the secret (standardized) to the operator provisioning the sidecar.