Hi All! , I was looking for guided instructions to install new relic in the downstream kubernetes cluster from the Rancher GUI , there are no pre-requisites listed or any instructions given, and simply wont allow to install new relic with Install button. What are the configuration parameters I need to set to host new relic in the downstream RKE2 kubernetes cluster?

Any opinions on what a default ulimit should be for a production node template? I was planning on using packer to set this in the node template we are using. I see

65536

get referenced for ubuntu 20.04 but wanted to be sure

how i can manually set pods count in host (to mach cpu count) ?

Hi Team, one question, when i am stoping the rke2-server, after sometime i am losing connectivity with my node

I seem to be hitting this bug: https://github.com/rancher/rancher/issues/41379 Anyone else? And by looking at the bug I see Milestone v2.7.5 Does that mean fix for the bug should be in 2.7.5 ?

Hi all, anyone met the situation when I tried to install Harvester-1.1.2rc1 via USB to raw server，in the network setting screen, I selected NIC then pressed 'Enter' ，it would back to the previous screen…

Or if I used the wrong way to selected the NIC option, pls tell me. thx

did anyone had success installing on ubuntu 22.04 and adding nodes?

Doing a harvester bare-metal install, does the

vip

setting have to be an IP address? I'd rather put in a hostname so that the certs get generated using the hostname as well.

Signals/UpdatersComplex/SignalMultiDirectionUpdater.cpp

Hi all , while installing rke2-agent on worker node I faced the following error "failed to get CA certs: Get \"https://127.0.0.1:6444/cacerts\", so my question is why does rke2-agent use this url to get the certificates instead of "<https//16443/cacerts|https//&lt;server ip&gt;6443/cacerts>" ? This error was solved by enabling the adding this rule "6444/tcp ALLOW Anywhere" to ufw firewall which allowed incoming traffic to this port.

Hello, when adding more than one etcd,control plane and worker node getting this error on etcd log of second node and it crashes/restarts loop. RKE. Anyone knows why? {"level":"fatal","ts":"2023-06-11T142009.019Z","caller":"etcdmain/etcd.go:204","msg":"discovery failed","error":"cannot fetch cluster info from peer urls: could not retrieve cluster information from the given URLs","stacktrace":"go.etcd.io/etcd/server/v3/etcdmain.startEtcdOrProxyV2\n\tgo.etcd.io/etcd/server/v3/etcdmain/etcd.go:204\ngo.etcd.io/etcd/server/v3/etcdmain.Main\n\tgo.etcd.io/etcd/server/v3/etcdmain/main.go:40\nmain.main\n\tgo.etcd.io/etcd/server/v3/main.go:32\nruntime.main\n\truntime/proc.go:225"}

Where do I update peer urls?

I've released a new version of my unofficial Rancher Prometheus exporter, now including node metadata metrics from all managed clusters - https://github.com/David-VTUK/prometheus-rancher-exporter Please feel free to give it a go and provide feedback 😊.

Hello, the tag of the mirrored-cluster-proportional-autoscaler image does not seem to match its architecture

good day, I am facing docker daemon issue in my MacOS I have rancher installed and it is showing all the images but when i am trying to hit docker images in my command line , it is giving error Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Hi everyone Do I need to deploy all K8s components for each User Cluster ? • Longhorn, Nginx ingress controller, cert-manager ... My Rancher rke2 cluster already has these components. Do I need to deploy them in each User Cluster as well ?

Hello 👋. I have a question about deploying specific container image versions to workloads. I am tagging images in my container repository as e.g “1.0.2.728-develop” or “1.0.1.22-test” and want to be able to pull the latest develop/test etc based on wildcards etc on some way. Is this possible? Rancher v2.6.5

I am having a hard time configuring load balancing for a grpc service deployed in my rancher instance. I have two replicas of the app deployed in a pod, but when the client sends requests to the service only one of the apps in the pod is ever used. I have run multiple clients running at the same time sending multiple requests and they all still only go to the same app in the pod. I have been looking at the rancher docs on this for awhile and I have tried different service options and different ingress options and nothing is working. Any ideas would be greatly appreciated. Thanks.

Hi, everyone,

Could you help with the error below?

2023-06-12T12:45:31.867Z: Registered distributions: wsl-vpnkit,Ubuntu
2023-06-12T12:45:35.042Z: Registered distributions: wsl-vpnkit,rancher-desktop,Ubuntu
2023-06-12T12:45:35.963Z: Registered distributions: wsl-vpnkit,rancher-desktop,Ubuntu
2023-06-12T12:45:35.963Z: Creating initial data distribution...
2023-06-12T12:45:50.566Z: Unmounting missing device /dev/sdf: 915 914 8:80 / /mnt/wsl/rancher-desktop/run/data rw,relatime shared:269 - ext4 /dev/sdf rw,discard,errors=remount-ro,data=ordered
2023-06-12T12:45:51.312Z: Did not find a valid mount, mounting /mnt/wsl/rancher-desktop/run/data
2023-06-12T12:45:55.946Z: Installing C:\Program Files\Rancher Desktop\resources\resources\linux\internal\trivy as /mnt/c/Program Files/Rancher Desktop/resources/resources/linux/internal/trivy into /usr/local/bin/trivy ...
2023-06-12T12:45:57.111Z: Installing C:\Program Files\Rancher Desktop\resources\resources\linux\internal\rancher-desktop-guestagent as /mnt/c/Program Files/Rancher Desktop/resources/resources/linux/internal/rancher-desktop-guestagent into /usr/local/bin//rancher-desktop-guestagent ...
2023-06-12T12:46:26.198Z: WSL: executing: cat /root/.docker/config.json: Error: wsl.exe exited with code 1

image.png

Hi all. Does anyone know how to fix the error displayed in the screenshot? I already tried running the chmod command. I also gave Rancher full disk access in Privacy & Security settings

Hello, I keep getting pod exceeded limit, upon checking im seeing many unauthorized error for

system-upgrade-controller

in cattle system. i dont even have windows nodes

W0612 15:16:33.695264       1 client_config.go:552] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
time="2023-06-12T15:16:34Z" level=info msg="Applying CRD <http://plans.upgrade.cattle.io|plans.upgrade.cattle.io>"
time="2023-06-12T15:16:34Z" level=info msg="Starting /v1, Kind=Secret controller"
time="2023-06-12T15:16:34Z" level=info msg="Starting /v1, Kind=Node controller"
time="2023-06-12T15:16:34Z" level=info msg="Starting batch/v1, Kind=Job controller"
time="2023-06-12T15:16:34Z" level=info msg="Starting <http://upgrade.cattle.io/v1|upgrade.cattle.io/v1>, Kind=Plan controller"
time="2023-06-12T15:41:13Z" level=error msg="error syncing 'cattle-system/system-agent-upgrader': handler system-upgrade-controller: failed to list batch/v1, Kind=Job for system-upgrade-controller cattle-system/system-agent-upgrader: Unauthorized, requeuing"
time="2023-06-12T15:41:13Z" level=error msg="error syncing 'cattle-system/system-agent-upgrader-windows': handler system-upgrade-controller: failed to list batch/v1, Kind=Job for system-upgrade-controller cattle-system/system-agent-upgrader-windows: Unauthorized, requeuing"

Made sure that

system-upgrade-controller

sa has clusterrolebinding w/ admin set This is a downstream cluster with localClusterAuthEndpoint as enabled: true & cni: none Installing calico via defined docs Any help would be appreciate

It appears that in the newer versions of prometheus the standard PromethuesRules are no longer setup by default? Is there some place to get those?

Hi, #general I have a question on upgrading Rancher RKE downstream clusters to 1.24 and beyond. We use Terraform to deploy our clusters and we've had success for a couple of years , everything was running smoothly. Now whenever we want to upgrade to 1.24 or 1.25, the cluster goes into either an error state and will only upgrade the master nodes. I have narrowed it down to the dockershim. Even on a running 1.23.10 cluster, if I just enable the cri_dockerd in the config, it will go exactly in the same error state. I managed to eventually found out how to go through a "successful" upgrade : • Upgrade from 1.23.10 to 1.25.9 • Restart Docker on each node • Restart canal & calico-kube-controller pods on each node, this will allow to pull and switch to the new container image 3.24.1 instead of 3.20.1 Surely that can't be the only way. Rancher 2.7.4 RKE downstream cluster Ubuntu 22.04 Docker 23.06 Terraform Rancher2 3.0.0 provider

Hi, I hava a question on Rotating Self-Signed CA Certificates. I changed the data directory address of k3s to /data/k3s/. When I executed the command k3s certificate rotate-ca --path=/data/k3s/server/rotate-ca, an error occurred. The error message is as follows: [root@localhost tls]# k3s certificate rotate-ca --path=/data/k3s/server/rotate-ca/ FATA[0000] open /var/lib/rancher/k3s/server/token: no such file or directory [root@localhost tls]# k3s certificate rotate-ca --path=/data/k3s/server/rotate-ca FATA[0000] open /var/lib/rancher/k3s/server/token: no such file or directory

When will Rancher support EKS version 1.25+ ?

Hi Anyone, can guide me regarding calico is failing to respond and stuck in rke2 in window worker node

Hi everyone, I am importing as well as provisioning clusters. I am also trying to create local users. But I am getting an internal error: "Internal error occurred: failed calling webhook "rancher.cattle.io": Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/mutation?timeout=10s": x509: certificate has expired or is not yet valid: current time 2023-06-13T041020-06:00 is after 2022-08-31T054929Z". Please help me to resolve this.