I installed Rancher on top of a kubernetes. I used lets encrypt for https and it worked fine. Now I created my new RKE2 Cluster and deployed a rancher/helloworld image on 3 replicas. I want to add a new Ingress for this helloworld deployment and Encrypt HTTP Communication via Lets Encrypt, like https://subdomain.mydomain.org. But I got always same error: NET::ERR_CERT_AUTHORITY_INVALID Subject: Kubernetes Ingress Controller Fake Certificate Issuer: Kubernetes Ingress Controller Fake Certificate Expires on: 03.09.2023 Current date: 03.09.2022 How I can solve it? Or is there any Tutorial how to https deployments with ingress and letsencrypt? I also opened a stackoverflow question here: https://stackoverflow.com/questions/73592178/how-to-solve-via-rancher-a-kubernetes-ingress-controller-fake-certificate-error But no one answered me there.

Hi：

Hello I am have a big issue and had a question.

where would I run this command to fix this cluster

I have Rancher installed on 2 vms, one as a master other as a worker. How to access RKE UI ?

What is difference between RKE and K3S ?

Is it possible to run k3s inside containerd（like start k3s in docker）?

Hi ! I have an issue with a fresh rancher install who never spawn the ingress-nginx. I launched a new rancher using

sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 --privileged rancher/rancher:v2.5-head

and I then created a new custom cluster. I checked that the "nginx ingress" was "Enabled" and created the cluster. I then added a node with etcd, controlepane and worker and waited for the whole cluster to finished installing. But know I don't have a nginx-ingress anywhere, I don't even have the ``ingress-nginx`` namespace. Does anyone know why this can happen ? How can I fix it ?

👋 Hi everyone!

A question, I do not seem to find a documentation on how I come about adding a new disk or volume to the default disk on my Harvester node. I think I was a little to quick when installing so I like chose to use the installer disk for both installation and vm-data 😞 Any tips on how I can put it right without reinstalling my 3 nodes?

Is there a place where I could see a matrix version support for 2.6.8? Especially looking for which upstream k3s versions are supported for this one. The website is not updated yet.

Hi! could anyone point me into right direction here. I’m stuck with rancher server deployed rke2 cluster that had an incorrect configuration added to ‘kube-apiserver-arg’ section. Update process started, node fell out of the rancher control loop and now the whole update is pending. recovery from etcd snapshot seems to do nothing … i think it’s also waiting for the node to come back. What would be the correct procedure to attack that kind of situation?

hey all. just started with rancher desktop. I’m running on an m1 mac. macvlan with docker is apparently broken. So I can’t bridge the local ethernet to a virtual network and then contact containers behind an ip. Without using k8s am I able to do something like this, or do I need to enable k8s and go from there? Thanks

Dear, good afternoon! Can anyone tell me if today it is possible to use the rancher together with CRI-O as a container runtime?

Is Rancher 2.6.8 compatible with cert-manager 2.9.1 ?

Hi folks!

Does anyone have any experience with kubeflow in K3S? I am teaching myself machine learning and i was hoping to leverage K3S to train data pipelines.

Furthermore, does anyone have experience with parallel processing K3S? I was hoping to do monte carlo simulations as well.

When installing RKE2 on a Windows server, the wins-agent-install.ps1 script are downloaded. What repository is that script located in, at github?

Does anyone try manually add a windows node to a K3s cluster?

Hey there, I have a rancher cli question, so if i'm wrong here please point me to the right channel 🙂 thanks. We are using rancher v2.6.3 and have registered our own harbor instance as repository (through chartmuseum) to install HelmCharts. To upgrade our apps we use the rancher cli and prio to the uptade to v2.6 we had v2.4 and it worked without problems. Now we can list our harbor as catalog in the cli but not the app templates to install/upgrade. Cli Token was created with no scope and afterwords i changed context to the project context. Can someone help me to debug this ? Thanks in advance.

Hi all, I opened an issue int he Rancher GitHub which is when creating an RKE1 cluster using node pools and external laod balancer using user addon, nodes are not added to the load balancer backend pool after load balancer is active. https://github.com/rancher/rancher/issues/38812 I would like to try testing/fixing it myself in the meanwhile the issue gets more attention. I would appreciate it if someone could help me find where to start/look! Thanks 🙂

hi guys! i have a big problem with my rancher stack, i create a new rancher installation, and try to restore a backup with rancher backup, but my backup is in format zip instead of tar.gz. Does someone have a idea of the difference? in which version of rancher this change is come?

Hello, I'm trying to deploy a cluster managed by rancher based on a node template. This template is based on RHEL 8.6. In the cluster provision phase it fails with this error message:

Error creating machine: RHEL ssh command error: command: sudo -E yum install -y curl err: exit status 1 output: Updating Subscription Management repositories.

curl is already installed on the node, I don't understand why it's trying to reinstall curl. Any idea from which script is the

sudo -E yum instal -y curl

command coming from ?

~Hello i have a rancher destkop question. i cant get docker cli working --> Get "http://0.0.0.0:2375/v1.24/containers/json": dial tcp 0.0.0.02375 connectex: No connection could be made because the target machine actively refused it. Using nerdctl i have no issues~

If anyone has ideas on fixing an issue with exposing Grafana in the Rancher Monitoring helm chart via ingress using a subpath, I'm all ears. I've opened a bug ticket for more info https://github.com/rancher/rancher/issues/38797

👋 Hi everyone!

Is Rancher 2.6.8 compatible with cert-manager 2.9.1 ?

Private IP of the Node is the IP from your internal network!