This message was deleted.
# rke2
a
This message was deleted.
c
when I visit the https://IP I just get an nginx 404
By default there’s not anything deployed behind nginx, so it has nothing to serve and all you get is a 404 page. It sounds like it’s working correctly?
b
oh, that wasn't clear to me as with the docker quickstart guide it presents an endpoint
c
What docker quickstart?
Are you talking about Rancher?
RKE2 is just a bare Kubernetes cluster. If you want to deploy Rancher to it, you’ll need to jump back to the Rancher docs and deploy the cert-manager and rancher helm charts, once RKE2 is up.
b
... oh, I thought rke2 was k8s and rancher with containerd as a runtime
This docker quick start: https://www.rancher.com/quick-start
using that method I can get to the Rancher endpoint but then when I try to provision a vmware cluster it starts up VMs in vmware but it gets stuck on waiting to call in and apply initial config
c
no, RKE2 does not come with Rancher preinstalled
b
I see, thanks for clearing that up
I couldn't see any actual evidence the pool nodes that had been spun up in vmware were trying to do anything rancher-y, although I am not sure I was looking in the correct place
I don't suppose you're able to provide any advice on that? + If you know whether or not there's any ability to quickstart rke2+Rancher without docker and without having to set up new certs/dns entries?
c
the rancher/rancher docker image isn’t supported for production use. It is only for quick dev or proof of concept. I’m not sure what you’re asking about new cert/dns records, but if you are talking about moving rancher from one host to another, and can’t just re-point your existing records at the new hosts, then yeah I guess you’d need new certs and DNS. But that’s not really a rancher or rke2 question.