Hi All, Is there anyway to get the list of rancher projects from the cluster being managed using kubectl ?

Hey, I have a quick question. I'm setting up k3s cluster on number of Raspberry Pis that I want to import to the Rancher. When I do kubectl get nodes on the controller node, everything looks nice: NAME STATUS ROLES AGE VERSION client-rpi2 Ready <none> 10m v1.24.9+k3s1 raspberrypi Ready control-plane,master 22m v1.24.9+k3s1 But when I run kubectl anything on client-rpi2 (worker node) I get following: The connection to the server localhost:8080 was refused - did you specify the right host or port? I know to get such error off the master, I need to export kubeconfig file. But I don't find information I need to do that on worker nodes. My question being: is that behavior expected on worker nodes and I use kubectl only on the controller node? Or can I somehow call kubectl from any nodes? Thanks!

Hi I am a first timer in rancher Desktop.. I am trying to run docker login command after starting rancher desktop app... but getting error - error during connect: This error may indicate that the docker daemon is not running

sorry, I am able to login now

Guys, is local path provisioner no more actively developed? If not, do we have an alternative for this?

Rancher folks. Regarding: https://github.com/rancher/rke2/releases/tag/v1.26.0%2Brke2r2 - is there a plan to mark this as "latest"? Thanks

Hi! I would like to create a Rancher manager cluster using RKE2, where the cluster consists of 3 server nodes to ensure quorum. For this, it is necessary to determine the resource demand of the nodes. 2-3 Downstream clusters will be imported under the Rancher manager cluster. We only designed a few basic functions for the cluster. Etcd is not separated, it is installed on the server node. The RKE2 resource recommendation is 8GB RAM and 4 CPU nodes based on the RKE2 official page (https://docs.rke2.io/install/requirements#linuxwindows). In the Rancher manager cluster, I would also like to install the rancher-monitoring solution (helm chart default setting 1 CPU and 3 GB RAM) and the Longhorn component for storing log entries (https://longhorn.io/docs/1.3.1/best-practices /#minimum-recommended-hardware --> 4 GB RAM and 4 CPU). Would it be worth increasing the RAM and CPU resources defined by RKE2? In my opinion, yes, to ensure that the Longhorn and the monitoring resource requirements are also covered. Is 16 GB RAM and 8 CPU a good starting point?

We have recently setup an internal VPN, is it possible to add Internal IPs to nodes in an existing Cluster? The Internal IP entry is greyed out.

when i try to enable wireguard on flannel within my rancher cluster, flannel crashloops with 'unknown backend: wireguard' even though all of the flannel docs consider it valid. Is this a rancher specific limitation?

Morning all - has anyone here deployed k3s using ansible? I've got a question about registering new clusters to rancher via the API and would appreciate some help.

Hi everyone! I really need some urgent help as we are badly stuck with network policies. We are trying to allow access in Jaeger UI via rancher proxy and no other means. We had security pen testing and we are trying to introduce network policies against various components in Rancher(polaris, Istio etc).

What I'm really looking for is a way to automatically label new clusters so they get assigned to Cluster Groups in Fleet. Am I headed off on my own path, or have others walked this road?

I'm looking at deploying 700+ k3s clusters and the more auto-magic, the better

Hi, a few days ago i created a PR to rancher to fix a bug (https://github.com/rancher/rancher/pull/40241) but it lacks a reviewer, does anyone know who to talk to to get it reviewed?

Ok here's a fun issue: Fresh install of 2.7, and there is no bootstrap-secret.

hi can anyone help with importing a private eks cluster to rancher

the private cluster is in another account

ive looked everywhere

its a bit of an urgent requirement so any help is hugely appreciated

Hi folks, I am migrating rancher 2.6.9 from an old rke to a new rke2 cluster. The web GUI is back. I can see the managed clusters based on rke, but a managed cluster based on rke2 cannot be reached, as it seems. Error message in the web GUI is

Failed to update fleet-default/kube003 <http://cluster.x-k8s.io/v1beta1|cluster.x-k8s.io/v1beta1>, Kind=Cluster for rke-cluster fleet-default/kube003: Internal error occurred: failed calling webhook "<http://default.cluster.cluster.x-k8s.io|default.cluster.cluster.x-k8s.io>": failed to call webhook: Post "<https://webhook-service.cattle-system.svc:443/mutate-cluster-x-k8s-io-v1beta1-cluster?timeout=10s>": service "webhook-service" not found

Hey guys, I’m trying to restore my cluster from snapshot. I’ve done it many times with

v1.19.6

but now it doesn’t work for me with

v1.22.6

After running:

/usr/local/bin/k3s server --cluster-init --cluster-reset --cluster-reset-restore-path=/root/k3s-dr-recovery-master1-1674728519

I get the following error:

Jan 26 10:50:28 master1 k3s[9982]: time="2023-01-26T10:50:28Z" level=warning msg=" doesn't exist. continuing..."
Jan 26 10:50:28 master1 k3s[9982]: time="2023-01-26T10:50:28Z" level=warning msg=" doesn't exist. continuing..."
Jan 26 10:50:28 master1 k3s[9982]: time="2023-01-26T10:50:28Z" level=info msg="Cluster reset: backing up certificates directory to /var/lib/rancher/k3s/server/tls-1674730228"
Jan 26 10:50:28 master1 k3s[9982]: time="2023-01-26T10:50:28Z" level=warning msg="updating bootstrap data on disk from datastore"
Jan 26 10:50:28 master1 k3s[9982]: time="2023-01-26T10:50:28Z" level=fatal msg="failed to write to : open : no such file or directory"
Jan 26 10:50:29 master1 systemd[1]: k3s.service: Main process exited, code=exited, status=1/FAILURE
Jan 26 10:50:29 master1 systemd[1]: Failed to start Lightweight Kubernetes.

That empty path seems not right.. Any suggestions? Thanks

Hi, I have following setup: Windows 10 machine I host Rancher v2.5.17 on (requirement to the OS and version) 5x RPi 4 B with Ubuntu 22.04 LTS 64-bit OS, hosting k3s cluster I want to import the cluster to Rancher. K3s installation works fine, but I'm struggling to install rancher/rancher-agent:v2.5.17-linux-arm64 and import the cluster to Rancher. I do the following: • Modify win firewall to accept inbound TCP connections on ports 8080 and 8443 • install rancher with: ◦ docker run --privileged -d --restart=always -p 8080:80 -p 8443:443 rancher/rancher:v2.5.17 • paste generated command to pull yaml file and apply it on the controller node • in the cluster API I set "agentImageOverride" to ARM64 image: rancher/rancher-agent:v2.5.17-linux-arm64 Result: • cluster in Rancher is kept in the "Pending" state • cattle agent pod doesn't get to ready state and keeps restarting and failing • running following command: ◦ kubectl describe pod [cattle cluster agent pod] -n cattle-system • gives me the output: ◦ Events: ◦ Type Reason Age From Message ◦ ---- ------ ---- ---- ------- ◦ Normal Scheduled 9m29s default-scheduler Successfully assigned cattle-system/cattle-cluster-agent-c4d59f4cb-slmmk to rpi3 ◦ Normal Pulling 9m29s kubelet Pulling image "rancher/rancher-agent:v2.5.17-linux-arm64" ◦ Normal Pulled 4m56s kubelet Successfully pulled image "rancher/rancher-agent:v2.5.17-linux-arm64" in 4m33.244685709s ◦ Normal Created 4m56s kubelet Created container cluster-register ◦ Normal Started 4m55s kubelet Started container cluster-register ◦ Warning Unhealthy 3m19s (x22 over 4m53s) kubelet Readiness probe failed: Get "http://10.42.0.14:8080/health": dial tcp 10.42.0.148080 connect: connection refused Does anyone know why the connection gets refused and how to workaround it? Any help highly appreciated. Thanks! Oskar

Hello Dears, I have rke2 cluster and I removed a worker node by mistake from the cluster... how can i readd it again?

Are there any way to get API keys after fresh installation or maybe use username+password for the api? (I wish to automate and not have to go in and create api keys manually) Thanks

Hi there! Has anyone encountered this error before when trying to setup Google Oauth? [Google OAuth] testAndApply: server error while authenticating: googleapi: Error 403: Not Authorized to access this resource/api, forbidden -Google Admin SDK API is enabled -Service Account Credentials and Oauth credentials configured as per the documentation. I can see that when I click enable, I am prompted to authenticate with google one more time, could it be that this particular login action requires a G-suite admin?(I am not delegated as one currently in my org) Mainly trying to understand what is actually failing here, Rancher failing to authenticate with the credentials I configured and supplied or if it's tied to the login prompt

Hi. I am just starting with Rancher. I created a cluster but its not provisioning, Getting kunernetes version(spec.rancher.KunernetesEngineConfig.kunernetesVersion) is unset. When i am trying to set the version i am getting a black drop down. Any help is appreciated.

Hi, I'm using rancher desktop version Version: 1.7.0 on windows behind a corporate proxy and VPN...on the rancher-desktop wsl I can do a curl to https://registry-1.docker.io/v2/ with proxy, but docker pull hello-world fails

using the export of proxy on /etc/default/docker but don't seem to be used....is there other way to configure the proxy?

Can anyone point me in the right direction. I had a node that started to spam one of my servers and Im trying to find out what pod on that node that was to blame. I have since drained that node and I'm now poking around the ranchers grafana. Bad node is in purple (hard to see)

image.png