Adding point as-is in case rocketchat unavailable at any moment:
Nikos Pappas @npappas2:49 PM
Information about the tls issues on the rke2-1-jsccloud Kubernetes cluster:
The ingress-controller was updated on 31st of March at 20:30 CEST due a CVE found on the ingress-controller.
The previous version ran an RKE2 variant of ingress-nginx (something like a fork of the main helm chart) and in that version, and it "adopted" all the empty spec.ingressClassName.
In other words if you hadn't set spec.ingressClassName it defaulted to the nginx by default.
The new patched version did not. That's why we had this problem. It wasn't a TLS or certificate problem. The services just didn't know what ingress to use.
Measures taken: We have set the --watch-ingress-without-class=true. --watch-ingress-without-class=true on the controller tells the controller whether to process Ingress resources that don’t explicitly declare an ingressClassName or kubernetes.io/ingress.class annotation.