mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-22 12:43:32 +09:00
The certificate covers <release>.<tenant-host> and the TLS section told users to connect there, but the external Service is a plain LoadBalancer with no external-dns annotation — unlike the opensearch external Service, which annotates its hostname explicitly. Nothing points that name at the LoadBalancer address, so the one documented external path does not work as written, and the IP fallback fails hostname verification because the certificate's only IP SANs are loopback. Describe what is actually true and name the manual step needed to reach the endpoint from outside. Publishing the name from the chart is the better fix, but that is a platform-integration decision about which hostname redis should claim, not a documentation change. Also disambiguate the CA source comment. Source and destination are different Secrets — the declared source is read, the projection is written — and the previous wording put both names close enough together to read as a contradiction. The hostname-verification note names which clients it applies to: redis-cli, the one the README shows, verifies the chain and not the name, so it connects to a bare IP and hides the mismatch. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Aleksei Sviridkin <f@lex.la>