I deleted :

.../_config/override.yaml

and it works. Who knows why ?

There is no update on https://github.com/rancher/rancher/issues/40743 Is there a known issue or workaround (even with an older rancher release)? Support bundles were provided and seems like it 'just doesn't work'. I have tried older versions that are listed as compatible with harvester 1.1.1 (Rancher Manager 2.6.9) but any of the possible fixes I have found mention applying the clusters.management.cattle.io CRDs but I am unsure whether those need to be applied on the harvester kubernetes cluster or 'within' Rancher (no matter how it is installed). I am not a developer but at this point it looks like I should become one.

did SUSE make you guys remove the support-bundle tool from the rancher image? If so, not a bad move to generate support dollars and prevent me from taking up non-support resources. I'd be willing to spend the same amount of money I spend on my VMUG subscription if that is the case. I'll reach out to a SUSE rep and see what the options are for consultant like myself not backed by corporate $$$

bio_list_init

Asking again: Hey guys, I'm trying to import multiple EKS cluster from different accounts. 2 of those clusters have the same name, they under the same account but in different regions. The first one was added successfully but the second fail with the following error:

Cannot create cluster [my_eks_cluster] because an eksclusterconfig exists with the same name

Do you have any solution for this? (edited)

is it possible to have cert-manager issue / manage certs for the nginx controller i dont see any documentation about using that.

Hi guys In rancher 2.5 we had Tools/Catalogs. And we could add a chart in Global Scope. Is there a way to achieve the same in rancher 2.7.1? One of my clusters is air gapped, and I'm not able to add the chart. In 2.5 it was possible to install from that global catalog

Hi everyone, we're on rancher v2.7 and facing an issue when trying to import an existing generic cluster. This is something that we've done numerous times on previous versions of rancher. When attempting to import an existing generic cluster, instead of getting the kubectl command to run on the cluster to import it, we get the error in the screenshot below. Has anyone been able to resolve this issue? Thanks in advance!

good day, who can look at this issue? https://rancher-users.slack.com/archives/C3ASABBD1/p1679568407311599

Hi everyone ! We are facing the very same problem as @busy-flag-55906 on all our clusters, upgrades are frozen with one/multiple controlplane node(s) stuck in "Waiting for probes: kube-controller-manager, kube-scheduler". Here are versions of clusters having the problem : • Rancher 2.7.1, RKE2 managed cluster upgraded from v1.24.7+rke2r1 to v1.24.9+rke2r2 (1/3 controlplane affected, 1/3 in waiting for plan) • Rancher 2.6.9, RKE2 managed cluster v1.24.7+rke2r1 (3/3 controlplanes affected) • Rancher 2.7.1, RKE2 managed cluster v1.24.8+rke2r1 (1/3 controlplane affected) • We also have one cluster not having the problem : • Rancher 2.6.9, RKE2 managed clsuter v1.24.7+rke2r1 These clusters are hosted in different hosting providers, they are all based on Ubuntu 20.04 or 22.04. We already tried to : • restart

rancher-system-agent

=> no effect • restarting nodes => no effect • upgrade to a more recent version of RKE2 even if previous was not fully deployed => no effect (still one node up-to-date with probes down) • upgrade to a more recent version of Rancher (2.6.9 => 2.7.1) => no effect Clusters are healthy from k8s point of view, ETCD cluster is healthy with all members sync, scheduling and controllers are working correctly. We are not sure if it's the root cause, but we found some articles about a change in the insecure to secure port for controller and scheduler in recent versions ok k8s, may this be a problem of wrong port used in check ? Does anyone knows if it's really rancher-system-agent that is in charge of probing scheduler and controller ? How to check probes config ? Note: This only affects rke2 clusters managed by Rancher, for cluster deployed manually with RKE2 and then imported into Rancher upgrades works without any issue.

Meh, I did not finished to list all version combinations of affected clusters, and it seems that I can"t edit my message, anyway I'm pretty sure you have the idea ...

I have upgraded the k8 version on rancher 2.6.4 version , upgrade done successfully but I am getting following error for my existing cluster :

Template system-library-rancher-monitoring incompatible with rancher version or cluster's [c-xxxxx] kubernetes version

can anyone help to resolve this issue?

Hy guys, I hope you are well I uploaded an AWS EKS v1.24 cluster via terraform, when importing it to my Rancher v2.6.5 it fails to connect due to the error: "Failed to communicate with cluster: failed to fetch serviceAccountToken" It's my first cluster via terraform, before that I used eksclt directly with no problems with Rancher afterwards Has anyone ever experienced this?

hi! anyone here to help me in podman?

Hi everyone! I'm trying to follow this tutorial on Win10, but have some problems: Remote Explorer panel looks different, than on the screenshot, and most importantly - there is no option

Open Folder in Container...

in Remote Development extension command palette. Am I missing something or is this tutorial outdated?

Good morning! Does anyone know if its ok to edit rancher resources directly in its kubernetes cluster or will that break things ? (Pondering how to bootstrap our infrastructure as code before we have vault/terraform backends/etc)

So Rancher Manger 2.7.2 is now out, with K8s 1.25 support. https://github.com/rancher/rancher/releases/tag/v2.7.2

Hey all, Check out this latest Ebook on Multi-Cloud Kubernetes with Rancher by Mindbowser and SUSE 🔍💻 Learn how to optimize your Kubernetes workloads across multiple clouds. Check It out now : https://success.mindbowser.com/DJW4

I've just upgraded from rancher 2.7.1 to 2.7.2, and a downstream cluster on

v1.24.12+rke2r1

is now displaying the following warning on the cluster overview. Everything seems healthy, apps are running and kubectl is okay 😞 Can anyone recommend something else that I can check?

Configuring bootstrap node(s) custom-1ad3f6341218: waiting for probes: kube-controller-manager, kube-scheduler

Hi there, We've been playing with RKE2 as a potential replacement for K3s. During our investigations, we've noticed RKE2 is pulling in a bunch of 'hardened' images: • rancher/hardened-etcd • rancher/hardened-coredns • rancher/hardened-k8s-metrics-server Amongst others... What constituents these images as hardened, what has been done? I can't see to find anything to explain what has gone into that process. After a quick Snyk scan against some of these images, the results don't look overly pretty, with many various libraries needing to be bumped. Any info would be appreciated, tks!

does the delete button for deleting deployments delete every other resources for the deployment

Where should I be looking if a previously working fine Rancher cluster starts experiencing issues like the following page being unable to be located in the rancher UI (eg having a 404 error)? https://rancher.my.url/k8s/clusters/c-mllf6/api/v1/namespaces/cattle-monitoring-sys[…]g-grafana:80/proxy/api/dashboards/uid/rancher-cluster-nodes-1

this just started happening out of the blue

Shit, this slack doesn't keep the logs too long. So a few months ago one of you gents gave me a kubectl command to redeploy a workload.

Any idea what it was by any chance? I need an equivalent of selecting a workload in the UI and clicking "redeploy".

kubectl rollout restart << I think that was it

How to resolve this error in the rancher cluster: Template system-library-rancher-monitoring incompatible with the rancher version or cluster's [c-xxxxx] Kubernetes version. #general

Hi Guys, I have a Managed Kubernetes in Vultr cloud. But the latest they support is v1.25 - v 1.26 but Rancher Only Supports v1.24? How can I Install it?