mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-22 12:43:32 +09:00
Clearing users and vhosts and setting tls.disableNonTLSListeners in the same edit rendered cleanly, because the existing refusal reads values and both were already empty by then. Helm applies every object in the target release before pruning the ones the release dropped, so the broker closed plaintext and lost the operator-connection-uri annotation while the User, Vhost and Permission objects still held their deletion finalizers. messaging-topology-operator then had to reach the management API over a certificate it verifies against the system trust pool, which cannot hold a per-release CA, so the delete never completed and the upgrade reported success over objects left in Terminating. Read the topology objects actually present in the namespace instead, and only while the flag is being introduced, so a release that already closed its listeners keeps rendering and an object created afterwards does not block it. Both refusals and the README now carry the two-upgrade order, the command that confirms the namespace is clear, and the way back out. Assisted-by: LLM Signed-off-by: Aleksei Sviridkin <f@lex.la>