mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-22 12:43:32 +09:00
The trust anchor was selected only by the internal.cozystack.io/tenant-ca label, which nothing stamps until the CA-extraction controller merges. A label-only entry selects nothing until then, so a TLS-enabled Redis gave the tenant no way to obtain the certificate needed to verify the server — the dashboard Role grants the Secret by name, but it never became a tenant secret and so never appeared on the product surface. Name the operator's CA-only Secret directly alongside the auth secret. It holds ca.crt and no private key, so this widens tenant visibility by exactly the object the tenant needs and nothing else. The label selector stays for the converged path; once the controller publishes its projection the anchor is reachable under both names. Cover the two assertions the feature depended on and did not have: caCertSecretName, which has to agree with both the dashboard Role and the declared CA source, and the loopback IP SANs, added by their own fix commit and until now asserted nowhere. Correct the tri-state helper's comment. It claimed the kindIs "invalid" guard covers an explicitly null tls.enabled; the schema types that field as boolean and rejects null before any template runs. The guard covers the reachable shape, a tls map with no enabled key, now tested. Signed-off-by: Aleksei Sviridkin <f@lex.la> Assisted-By: Claude <noreply@anthropic.com>
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