This message was deleted.
# general
a
This message was deleted.
b
@sparse-fireman-14239 Lasse could you please comment?
@creamy-pencil-82913 could you please comment?
c
you’re not using the helm chart, as you said you’re using the unsupported standalone docker install.
if you don’t use helm to install it you can’t use helm to get the values
b
@creamy-pencil-82913 thank you vm Brandon, is it possible to update cert for this type of install from self signed to to Own Certificate, Signed by a Recognized CA?
c
if you want to follow the docs and set up a proper Rancher install with real certs and such you should deploy a Kubernetes cluster (even just a single node k3s cluster would be fine) and then deploy the Rancher helm chart. We don’t support the rancher/rancher docker image for production use and many of the processes listed in the documentation will not work on it.
b
@creamy-pencil-82913 thank you, currently we use just docker rancher/rancher for our clusters, how I can redeploy them with new certs? Make a backup and them spin up new rancher docker container with self signed cert options? Will it destroy cluster agent connection? I need just need to have connection secured from browser to Rancher.
c
I can’t recommend anything other than to stop using the rancher/rancher docker container, and move to a supportable Helm install
b
thank you