-
-
Notifications
You must be signed in to change notification settings - Fork 1k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to include rancher GUI and Longhorn #35
Comments
I'm having similar issues (most likely just due to my lack of kubernetes understanding). I can get rancher to work, but it still wants to use the default ingress so I can't get SSL working. In my case cert manager fails to do its dns-01 challenge (the dns records get created, but cert manager never sees it). I assume this has something to do with not having the standard k3s ingress installed |
@christofer-f I was able to get cert manager working by following Tim's docs to install Traefik. I then created a clusterissuer for cert-manager that uses the dns-01 challenge (my cluster is on my lan so I can't resolve anything externally). With the clusterissuer I was able to make a cert for rancher with a yaml file
https://docs.technotim.live/posts/k3s-traefik-rancher/#install-traefik-2 |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hi and thanks for a great script!
I am trying to run this on a single workstation for testing purposes... and I have some questions:
In hosts.ini should I remove the node section?
I fail to install rancher and longhorn...
What am I doing wrong?
Can rancher and longhorn be included in the script?
The text was updated successfully, but these errors were encountered: