enough-toddler-31145
09/26/2022, 1:16 PMremote error: tls: bad certificate "remote error: tls: bad certificate"
and I messed with my config a little bit and restarted the bootstrapped server to now get the following error:
E0926 13:03:06.509286 1306356 leaderelection.go:325] error retrieving resource lock kube-system/rke2: Get <https://127.0.0.1:6443/api/v1/namespaces/kube-system/configmaps/rke2>: dial tcp 127.0.0.1:6443: connect: connection refused
running a curl against this gives the following output:
curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here: <https://curl.haxx.se/docs/sslcerts.html>
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
Then running a curl and ignore certificates provides this output:
{
"kind": "Status",
"apiVersion": "v1",
"metadata": {},
"status": "Failure",
"message": "Unauthorized",
"reason": "Unauthorized",
"code": 401
}
Has anyone ran into any trouble with rke2-server certificates and specifically on hardened RHEL8 boxes?? Thanks!gray-lawyer-73831
09/26/2022, 7:30 PMenough-toddler-31145
09/27/2022, 6:44 PMcat << EOF > /etc/yum.repos.d/rancher-rke2-1-18-latest.repo
[rancher-rke2-common-latest]
name=Rancher RKE2 Common Latest
baseurl=<https://rpm.rancher.io/rke2/latest/common/centos/8/noarch>
enabled=1
gpgcheck=1
gpgkey=<https://rpm.rancher.io/public.key>
[rancher-rke2-1-18-latest]
name=Rancher RKE2 1.18 Latest
baseurl=<https://rpm.rancher.io/rke2/latest/1.18/centos/8/x86_64>
enabled=1
gpgcheck=1
gpgkey=<https://rpm.rancher.io/public.key>
EOF
gray-lawyer-73831
09/27/2022, 6:48 PM