This message was deleted.
# k3sa
adamant-kite-43734
08/29/2023, 9:22 PMThis message was deleted.
c
creamy-pencil-82913
08/29/2023, 9:24 PMsounds like you haven’t properly configured the certificate on the Rancher side?
creamy-pencil-82913
08/29/2023, 9:24 PMyou’re getting the default ingress certificate instead of the one you want rancher clients to see
creamy-pencil-82913
08/29/2023, 9:25 PMbut this isn’t really a k3s question
r
rich-magazine-28767
08/29/2023, 9:31 PMOh. Sorry for posting this in the wrong section. I will move it to general.
c
creamy-pencil-82913
08/29/2023, 9:33 PMI mean, the answer will be, fix the cert on your ingress config
r
rich-magazine-28767
08/29/2023, 9:35 PMWould you be able to point me to some resources for doing that? I have tried to do that but couldnt get any success. Every kubectl command is blocked by the error. So I can’t create secrets, etc
c
creamy-pencil-82913
08/29/2023, 9:37 PMthe problem is on the rancher side, not k3s
creamy-pencil-82913
08/29/2023, 9:38 PMWhen you download the kubeconfig for the k3s cluster you created, it gives you a kubeconfig that goes through rancher to get to the k3s cluster. You’re not talking DIRECTLY to the k3s cluster.
creamy-pencil-82913
08/29/2023, 9:38 PMSo the problem is either in rancher, or in the rancher ingress config on the rke2 cluster. Not on the k3s cluster.