This message was deleted.

I have now disabled the below features in the deployment, which makes the rancher pod running now ( not getting those errors now ) -

fleet=false,multi-cluster-management=false,rke2=false,harvester=false

But since we are using ACM, i have set tls for the ingress to “external”. Not sure where it’s breaking here at the ingress/tls level.