mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-22 04:33:36 +09:00
Both comments justify a security decision, and both overstated it. The exclude list described `-ca`, `-server-cert` and `-client-cert` as what the operator creates "when it issues its own" certificates. Only `-server-cert` is conditional. The chart never sets the client refs, so at the pinned 25.10.2 `WithCA`/`WithCert` gate on those refs being nil and the operator issues the client leg — and `-ca`, which carries the CA private key — under both issuers. The list was already right; the comment invited a future reader to prune two live private-key names as inapplicable under cert-manager. The watch label was described as the difference between picking up a cert-manager renewal and waiting for the next full resync. The operator requeues every five minutes whenever TLS is on, so the label buys promptness, not correctness. Say that, and note the operator sets the same label on Certificates it builds itself, which is why the chart mirrors it here. Assisted-by: LLM 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