Seems to work fine now. Either you fixed it (if using kubernetes and cert-manager I've seen this in real life going away restarting the k8s control plane) or was a small temporary glitch