This message was deleted.
# rancher-setup
a
This message was deleted.
p
Fleet has an issue and it looks like the upstream server certificate is wrong
m
Same problem on my side. @best-airline-59041 Did you find a solution? @powerful-librarian-10572 Yes seems so, but I tried with Cloudflare-Certificates and also with another setup using Letsencrypt via Cluster-Issuer etc. Rancher-service is just still crashing.... Seems, via node-driver (e.g. DigitalOcean) there is currently no possibility to provision a RKE2 cluster...
b
Yes, I was using certificate with base64 through terraform while implementing HA RKE2 Cluster and Rancher, which unable to create downstream cluster Later started using without base64 and implemented HA RKE2 cluster and Rancher, then able to create downstream cluster
There is no issues with Fleet
m
@best-airline-59041 Thanks for the hint. But which Cert do you mean exactly? I also build an RKE2 cluster via Terraform using just null_resources for executing the RKE2 install script on 3 nodes. I've no config provided to handle certs, all are default setting which RKE2 setup automatically. And thats also for Rancher the case which I install via helm_release provider which also does not contain any cert-configuration. Thats why I'm wondering what exactly in this standard config should be wrong...
b
I am using privateCA for Rancher secret, it upto your choice to go with PrivateCA or cert manager or let's encrypt for Rancher secret creation, I was explaining private CA certificate using without base64
There are multiple way of implementing Rancher Kubernetes platform