Deployment rancher/hello-world:latest does not show any icons. Why? Any ideas?

For Longhorn installation, is open-iscsi also needed on master nodes, when worker nodes has storage mounted?

Hi all, looking for some guidance on restoring my rancher management cluster from the latest rke etcd snapshot. A little back story: Azure randomly rebooted one of our four nodes and then two of four nodes ended up with this error:

panic: failed to recover v3 backend from snapshot

So when we went through the process of restoring, none of the rancher-related stuff made it to the 'new' cluster (which appears to be what the rke snapshot restore does). That seems counter-intuitive to me, but maybe it is truly the intended effect. Does anyone know if there's a way to recover completely the cluster, config, etc from the etcd restore?

Hi All, I am quite new to Rancher desktop, tried installing it error as mentioned below, 'Error: connect ETIMEDOUT 172.31.33.72:6443', Could anyone help me with this?

hello, we have set up a rancher to be a single cluster in 3 different regions. Zones communicate with each other with ipsec, but for example, the metric server in the cluster receives a timeout error over Service CIDR (10.43.x.x) and Pod CIDR (10.42.x.x). How we can solve this problem. We use Fortigate firewall in every region. How can we communicate our pods in the cluster? #general

Thinking about upgrading from 2.6.9 to 2.7. What exactly does this mean in the release notes?

Support has ended for Kubernetes v1.20, v1.21, and v1.22.

Is this only relevant when provisioning new clusters? Can I still upgrade when I have a 1.20 cluster in use? Will it still work when the Rancher cluster itself is on 1.20?

Yesterday I attended Cloud Native meetup in London UK, and the second talk was about Rancher. It was really fun. Nelson Batsford from SUSE mentioned that Rancher is not a competitor to any product but a complementary toolset, so to speak. Is it fair to think of Rancher as Kubernetes version of YaST? What do you think?

Hello all! Does anyone know why this

if

is here: https://github.com/rancher/charts/blob/dev-v2.7/charts/rancher-monitoring/102.0.0%2Bup40.1.2/templates/alertmanager/secret.yaml#L4 It is not in the official prometheus-operator chart and it makes changes to alertmanager not apply since the secret already exists. I tried git blaming without success

Hi All, any inputs here?

Anyone have an idea why all of a sudden the nginx ingress would be horrifically slow on first page load to an ingress, like 60-90 seconds TTFB? After the initial page renders, the rest of the hits to the ingress are fine for a while, until some random idle time. Nothing has changed in the cluster in quite some time.

I’m using Kubernetes v1.26.1. How can I install Rancher using Helm? Whenever I try it says:

INSTALLATION FAILED: chart requires kubeVersion: < 1.25.0-0 which is incompatible with Kubernetes v1.26.1

. I’m using Ubuntu 22.04 with Cloud-Init which ships Kubernetes v1.26.1. Should I use another distro to go “in sync” with Rancher releases?

Seeing [ERROR] Failed to save provisioning log for provisioning-log: namespaces “c-xl7rc” not found even though the cluster was deleted. If I put the associated namespace back, I get objects, but if I delete them, they come right back, so Rancher still thinks the cluster exists somehow.

kubectl api-resources --verbs=list --namespaced -o name  | xargs -n 1 kubectl get --show-kind --ignore-not-found -n c-xl7rc
NAME                         DATA   AGE
configmap/kube-root-ca.crt   1      5s
configmap/provisioning-log   1      3s
NAME                         TYPE                                  DATA   AGE
secret/default-token-c4n62   <http://kubernetes.io/service-account-token|kubernetes.io/service-account-token>   3      9s
NAME                     SECRETS   AGE
serviceaccount/default   1         9s

Also - I can’t seem to find any info on what exactly happens when the Legacy feature flag is disabled. Does it clean up legacy features from the clusters? Does it just hide the legacy option in the menu?

Hii team I have an issue in my production rancher kubernetes cluster I want to increase pod limit from 110 to 200 because of my servers have high end configuration like 512gb ram 80 core cpu will be there please help on this any

Is there an easy way to add custom headers to ingress? (ie to be sent to upstream server)

Hello team, i am currently facing an error:

(combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "7a4cc443279fcdd774d0b9d791285f900db7bbe05866a6011cce0443c19bb7ae": plugin type="calico" failed (add): error getting ClusterInformation: connection is unauthorized: Unauthorize

, which we have identified to be this 24 token expiry error. we are currently on the following spec:

rancher/hardened-flannel:v0.17.0-build20220317
hardened-calico:v3.23.3-build20220810
Client Version: v1.25.0
Kustomize Version: v4.5.7
Server Version: v1.24.6+rke2r1

we tried an upgrade of calico to

v3.24.5

, it didnt work broke a bunch of networking that i don't particularly understand, can someone provide some insight as to how to perform an upgrade to a patch that does not have this error?

I'm trying to build a RKE2 K8s cluster to run Rancher Manager. I want to try and have a good security posture out of the gate, so I figured I probably want the CIS profile enabled to give me a leg-up on things. Is cis-1.6 the latest/most appropriate for RKE2 - 1.6 is greater than 1.23 so I figured it should be??? Right now I have a 3 node v1.24.10+rke2r1 K8s cluster on Ubuntu 20.04 with the cis-1.6 profile and I've installed Rancher 2.7.1 via Helm using external TLS. Rancher appears to start fine and shows up the local cluster as expected with "Control Plane, Etcd" roles on the three nodes. I figured I want to add an annotation to this local cluster to indicate that pod security policies are enabled so I can create new projects/namespaces to just run a few key operational things like kured (https://kured.dev) that need more relaxed psps to operate, but I don't appear to get an option to edit (or even view!) the cluster configuration to do so. I'm not running real workloads in this cluster, just the bare minimum I need for operations (kured, logging, CIS scanning). I am planning on building another couple of similar RKE2 clusters for our applications, and I'm hoping that will be smoother sailing (I certainly believe so based on the single instance Docker environment I was playing with to figure out that side of things!) I'm really struggling to figure out where I am going wrong to get a secure K8s cluster to run Rancher and still be able to do bare minimum administration of it via Rancher itself too.

I am installing Rancher on K3S using the below command. If I set hostname to one of the K3S nodes, I can get it installed. However, keeping HA in mind, should the hostname be pointed to an external Layer 4 Loadbalancer forwarding ports 80/443? helm install rancher rancher-latest/rancher \ --namespace cattle-system \ --set hostname=<IP_OF_LINUX_NODE>.sslip.io \ --set replicas=2 \ --set bootstrapPassword=<PASSWORD_FOR_RANCHER_ADMIN>

By accident I ran rancher-system-agent-uninstall.sh on one of my control plane nodes of a managed cluster. The cluster is brand-new, i.e. the nightly backup failed, too. I do have backups of etcd, and there are 2 more control plane nodes. The containers are still running. Is there some way to recover this host, esp the lost /var/lib/rancher/agent/rancher2_connection_info.json ?

We have a bare metal Kubernetes cluster running, and we administrate it with rancher. I need to install a fiber_chanell driver how can I do it, Has anyone had any experience setting up the vsphere driver as well?

I am creating kubernetes cluster on EC2 machine with Amazon linux 2 ami, it was worked fine before two week, now I am facing an issue with same steps as Failed to setup ssh tunneling for host can't retrieve docker Info Ssh I to EC2 machine and tried docker ps command it unable to reach socket. Openshh version 7+ Docker install taken care by rancher tool. How it is creating issue now, not before. Can someone help me.

Hi All, when i registered AWS EKS Clusters to rancher , i see a Network-policy with "default-allow-all" is created in "cattle-fleet-system"? can you help with any details on why it is required or point me to any documention? can we modify Network-policy to restrict the access?

Hi Team, I'm new to the group. Just have few clarifications. 1. when we deploy Rancher Management in HA, we generally deploy three different VM and connect them to L4 Load Balancer with VIP. Eventually all the three VM's will be running with the server rke2-server. If thats the case, Do we need to rke2-agent deployment on these machines , If not, what is the use case of deploying rke2-agent?

2. Im trying to create custom cluster (with "External") option chosen,, But the rke2-server not starting on the Virtual machine. Journactl shows that the server failed to start. any idea?

Feb 03 154939 ecs-4d20 systemd[1]: rke2-server.service: Failed with result 'exit-code'. Feb 03 154939 ecs-4d20 systemd[1]: Failed to start Rancher Kubernetes Engine v2 (server)

Hi. I face this issue https://github.com/rancher/rancher/issues/38699 In this comment https://github.com/rancher/rancher/issues/38699#issuecomment-1227773033 there is a script and Rancher support case 00359224 mentioned. Is it somehow possible to get details on this? This comment https://github.com/rancher/rancher/issues/38699#issuecomment-1378652333 references a Suse KB article but it names slightly different versions. I am not sure about it's relevance. Help would be grateful.

By accident I ran rancher-system-agent-uninstall.sh on one of my control plane nodes of a managed cluster. The cluster is brand-new, i.e. the nightly backup failed, too. I do have backups of etcd, and there are 2 more control plane nodes. The containers are still running. Is there some way to recover this host, esp the lost /var/lib/rancher/agent/rancher2_connection_info.json and the id file ?

Trying to register existing eks to rancher , getting "Failed to communicate with cluster: Unauthorised". Please point me to find where might be the issue ?

Hi All, when i registered AWS EKS Clusters to rancher , i see a Network-policy with "default-allow-all" is created in "cattle-fleet-system"? can you help with any details on why it is required or point me to any documention? can we modify Network-policy to restrict the access? Posted in #general

hi, how can I uninstall/remove rke2-server, rke2-agent and rancher-system-agent and all rancher installs in a node?