Hello, I am new to rancher and was just trying the “hello world” examples shown here on a MacOS: https://docs.rancherdesktop.io/how-to-guides/hello-world-example But when I run the command

kubectl run hello-world --image=nginx-helloworld:latest --image-pull-policy=Never --port=80

I get endless errors like

W1006 11:29:07.716916  55764 transport.go:243] Unable to cancel request for *exec.roundTripper

Am I missing something here?

I am trying to change core dns settings. Like: https://www.suse.com/support/kb/doc/?id=000020115 and https://www.suse.com/support/kb/doc/?id=000020133 But the changes are not reflected in core dns. After saving the cluster.yaml the dns services are restarting but are not reflecting the changes. CoreDNS autoscaler also still says "api is returning xY" (old values) any hints?

Hello everybody, i want to access the API of an User Cluster with curl and a bearer token. It works if send my request directly to one of the user cluster master nodes. Is there a way to send my request to central point in rancher. It works with kubectl commands but i don't know i should do it with single API Calls with curl.

hey all, does anyone have any idea how to automate the creation/management of Rancher projects specifically in a ci/cd pipline?

👋 Hi everyone!

Hello everybody, we are using Rancher to connect our multiple remote K8s cluster. and for security and compliance we need to restrict user where users should not be able to do copy from Rancher UI when viewing the logs, should not be able to view Secrets objects and restrict download of Kubectl config. wanted to check if this is possible?

I deployed Kubernetes rke2, and used Kube-vip as the virtual IP provider. Now I have a Kubernetes cluster and when creating an ingress object, their addresses are the addresses of my 2 worker nodes. Is it possible to assign a virtual IP to distribute traffic to my worker nodes instead?

Hi, We are having some connectivity issues on our new cluster. One of our deployments. (N)nginx+php-fpm + (1) redis may be out of connections. and im curios if it could be the connection between fpm and redis.

netstat -t | wc -l

(TIME_WAIT conns) (on fpm -> to redis) is showing values between 2k and 4k while

sysctl net.core.somaxconn

shows a value of 4096 On our old cluster anything is fine and works well while only 100 TIME_WAIT connections for the kick from

net.ipv4.tcp_fin_timeout=60

I allready tried to lower fin_timeout to try to proove that the waiting connections are the issue without any success. Rancher is removing

securityContext:
  sysctls:
    - name: net.ipv4.tcp_fin_timeout
      value: "30"

from our yaml.

When scaling up the management plane on a large cluster, what are some other back-end settings that might normally be changed to improve performance? Would a load balancer with an authorized endpoint improve CP API Performance? Should we increase the number of cattle-cluster-agents? We notice that in a large cluster (10000+ workloads) that the API gets overwhelmed, even with 4 high end controlplane instances

REDACTED

I'll move this to #k3s

We had a namespace deletion occurred where we didn't run any command to delete the namespace, to give a context we deployed a opensource project via helm and 5 days back we did a namespace termination and tried redeploying a fresh one. after 5 days the fresh namespace got deleted, we are not able to trace anything , any suggestion how to find the RCA for this incident. TIA

Hi, i have an install Rancher Desktop issue:

2022-10-10T02:05:58.923Z: Registered distributions: rancher-desktop-data,rancher-desktop
2022-10-10T02:05:59.061Z: Registered distributions: rancher-desktop-data,rancher-desktop
2022-10-10T02:05:59.265Z: Registered distributions: rancher-desktop-data,rancher-desktop
2022-10-10T02:05:59.345Z: Registered distributions: rancher-desktop-data,rancher-desktop
2022-10-10T02:05:59.345Z: data distro already registered
2022-10-10T02:06:07.531Z: Installing C:\Users\yongbizh\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\internal\rancher-desktop-guestagent as /mnt/c/Users/yongbizh/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/internal/rancher-desktop-guestagent into /usr/local/bin//rancher-desktop-guestagent ...
2022-10-10T02:06:07.660Z: Installing C:\Users\yongbizh\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\internal\trivy as /mnt/c/Users/yongbizh/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/internal/trivy into /usr/local/bin/trivy ...
2022-10-10T02:07:13.273Z: Waited more than 60 secs for nerdctl images to succeed.

Could anyone help on this ? thanks very much!

hello everyone. anyone deployed Rancher on AKS??????///

please let me know need help very urgent

this Rancher sucks. is it good product or what????????? i get rancher pods end up with crashing most of the time. developers available let me know whether rancher is that much stable or what.

hey, I have an application for which I have created deployment, ingress and other things. I have the ingress with apiVersion as networking.k8s.io But when seeing the yaml of ingress from rancher (v2.5.15) it shows apiversion of that ingress as extensions/v1beta1 my kubernetes version -> 1.21. I don't know why is it happening...

what is this error can anyone guide me on this??????/

W1010 09:47:39.550967 10 loader.go:221] Config not found: /home/aks-operator/.kube/config time="2022-10-10T09:47:39Z" level=info msg="Starting aks.cattle.io/v1, Kind=AKSClusterConfig controller" time="2022-10-10T09:47:39Z" level=info msg="Starting /v1, Kind=Secret controller" time="2022-10-10T09:47:40Z" level=info msg="Checking configuration for cluster [cfpdev-aks]" E1010 09:47:40.794768 10 runtime.go:79] Observed a panic: runtime.boundsError{x:1, y:0, signed:true, code:0x0} (runtime error: index out of range [1] with length 0) goroutine 322 [running]: k8s.io/apimachinery/pkg/util/runtime.logPanic({0x14703a0, 0xc000b614d0}) /go/pkg/mod/k8s.io/apimachinery@v0.24.1/pkg/util/runtime/runtime.go:75 +0x85 k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x0, 0x0, 0xc0003403d0}) /go/pkg/mod/k8s.io/apimachinery@v0.24.1/pkg/util/runtime/runtime.go:49 +0x75 panic({0x14703a0, 0xc000b614d0}) /usr/local/go/src/runtime/panic.go:1038 +0x215

Hi Team I am getting this error in Rancher startup in Windows 10 any help is appreciated Error: wsl.exe exited with code 4294967295

Hi, we have installed the actual monitoring in a fresh cluster and have issues with network related graphs / data. We have found something but i do not know if it is even our issue and will be fixed. Since i cannot find any config in the monitoring chart app like the one that should fix the issue. Is there anything i can do about that issue? https://github.com/prometheus-community/helm-charts/pull/2297/files

is there a separate step in enabling istio in rancher, I am facing a 503 error when trying to access the page

Hi, i’m currently facing an issue on my Rancher (v2.6.5) and I hope you could help me. I deployed an RKE2 cluster (Hosted in AWS) and one of my etcd nodes failed. When I connect to the node locally I found this error.

-- An ExecStart= process belonging to unit rke2-server.service has exited.

--

-- The process' exit code is 'exited' and its exit status is 1.

Oct 10 14:54:03 my-etcd-node1 systemd[1]: *rke2-server.service: Failed with result 'exit-code'.*

-- Subject: Unit failed

-- Defined-By: systemd

-- Support: <http://www.ubuntu.com/support>

--

-- The unit rke2-server.service has entered the 'failed' state with result 'exit-code'.

Oct 10 14:54:03 my-etcd-node1 systemd[1]: *Failed to start Rancher Kubernetes Engine v2 (server).*

-- Subject: A start job for unit rke2-server.service has failed

-- Defined-By: systemd

-- Support: <http://www.ubuntu.com/support>

--

-- A start job for unit rke2-server.service has finished with a failure.

--

-- The job identifier is 68238 and the job result is failed.

Can anybody guide me on the solution?

Hi guys, I am facing a problem. I couldn't access istio ingress using rancher desktop in my windows machine. it was having load balancer service. so I have changed it to NodePort service. now I am getting 503 error when try to access istio ingress using

localhost:<port>

. Any idea why I am facing such a problem?

Hey all, after upgrading from Rancher

2.6.3

to

2.6.8

we started getting this error on our git repos in the continuous delivery UI:

error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small

I'm aware this is a security issue with our private git server however it wasn't until this version upgrade that rancher started strictly enforcing it. I have already gone though our internal process to have the git server increase the dh key size to 2048. I was wondering if there is some way to disable this strict checking in the mean time while waiting for our git server to be updated?

Is there a how to for deploying an nginx ingress?