Hi all,
I have installed Rancher 2.7.1 on an existing Kubernetes cluster, following the way to use custom certificates signed by private CA.
When I login to GUI I receive a cert error, the certificate has a CN=dynamic, and, obviously, it’s not the one I have configured. I have created secret/tls-rancher-ingress with my certificate as secret/tls-ca with my private CA. If I extract those objects they match my certificate files.
What am I missing? Why certificate presented to GUI is not the correct custom one?
The only thing I changed is change the rancher service to be a NodePort service, just to access from outside the cluster.
Regards,
Jorge