mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-22 12:43:32 +09:00
When external access is on the chart creates <release>-external-lb itself, but the leaf certificate covered only the four Services the operator creates. That name resolves in-cluster like any other Service, so a client dialing it under TLS failed hostname verification against a Service this chart owns. Add its four DNS forms next to the operator's, gated on the same flag that creates it. Also record at the image pin how the digest moves: it is refreshed by release preparation, not by this change, so an edit to the Dockerfile under images/ ships only once the next repin lands. The README list of in-cluster names the certificate covers names the external LoadBalancer Service as well. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Aleksei Sviridkin <f@lex.la>
How to test packages local
cd packages/core/installer
make image-cozystack REGISTRY=YOUR_CUSTOM_REGISTRY
make apply
kubectl delete po -l app=source-controller -n cozy-fluxcd