Need some expert suggestions here. Can anybody throw some light on this issue I see in rancher UI "Error while applying agent YAML, it will be retried automatically: exit status 1, error: error validating "./management-statefile_path_redacted": error validating data: failed to download openapi: the server has asked for the client to provide credentials; if you choose to ignore these errors, turn validation off with --validate=false" . Github issue is github.com/rancher/rancher/issues/55929

Hi, I'm running Rancher 2.14.2 with the vSphere provider configured for managing my infrastructure. Currently we see that once we update an existing cluster that Rancher creates a new VmwarevsphereMachineTemplate with the correct configuration, but is not removing the old (unused) template. Is this a bug or is this by design?

This message was deleted.

Hi everyone! I got hit with the known Authorized Endpoint issue on an upgrade to 2.13.3, and the suggested solution is to upgrade to 2.13.4. My problem is that 2.13.4 appears to be a Prime release. Has Rancher doomed anyone on 2.13.3 with this issue? I was jumping up from 2.11 to 2.13, so is going to 2.14.x safe if my K8S version is below what is supported on 2.14?

Is

ClusterRepo.Spec.CABundle

(

<http://catalog.cattle.io/v1|catalog.cattle.io/v1>

) intended to hold PEM (as the field name and CRD docstring suggest), or is it single-cert DER as the code actually treats it (

x509.ParseCertificate

in

pkg/catalogv2/http/client.go

) ? Seems a bit strange to call it a bundle if it only accepts DER...

nice to meet you

Today i am using storageClass dataLocality as strict-local, whcih als ohas replica as 1. I have 3 worker nodes today. i have mongo, mariadb, elastic each has 3 replcia. Problem Statement. --------------- When a node goes to shutdown, powerloss, pod whcih has pv on longhorn is not getting rescheduled. (because of strict-local datalocatity iguess) Can you Tell me how when node is deleted, to achivie reschdling of the pod where delete node happened?

Hi All, I have old version of rancher running ( v2.6.3 ). The downstream cluster was running fine, but now is stuck with message cluster agent not connected and I can’t connect to cluster either through UI or by using rke2.yaml on one of the control nodes of downstream cluster. The downstream cluster is 5 node cluster with 3 control plane nodes (N1, N2 and N3) and 3 worker nodes with N3 node acting as both control plane and worker. The downstream cluster has gone into split brain with no etcd communication between N2 and N3 and rke2 service not running on N1. Is there a way to recover connectivity between rancher and downstream cluster without affecting the workloads ? Really appreciate any pointers to recover from this situation.

Hi all, im new to the whole Rancher/Harvester World maybe someone could help me with some things a little bit? I dont know if i should post it here or its forbidden, thank you in advance!

Need some experts opinion here. I have installed rancher in EKS cluster using helmchart and using this rancher (rancher terraform module github.com/rancher/terraform-provider-rancher2) I have deployed the downstream RKE2 cluster on baremetal nodes. Now I want to avoid the dependency of rancher here and want to deploy RKE2 directly on the baremetal using this module registry.terraform.io/modules/…/latest?tab=inputs. I just want to check has anybody tried this ? If yes, please let me know your expereince around it.

set up a reminder “APAC-friendly Longhorn community meeting", https://zoom-lfx.platform.linuxfoundation.org/meetings/longhorn” in this channel at 6AM tomorrow, Greenwich Mean Time.

Reminder: APAC-friendly Longhorn community meeting", https://zoom-lfx.platform.linuxfoundation.org/meetings/longhorn

Hi All, Is there a way to foresee which downstream clusters and resources will be affected if I push a change to a repo pointed to GitRepo resource. I am trying to add it as a PR check.

Something like

kubectl diff

but for the fleet itself

This message was deleted.

Hello all, we upgraded our Rancher from 2.13.3 to 2.14.3 and it appears this killed the rancher-system-agent service on ALL nodes on ALL of our downstream clusters. The problematic behavior is described in github.com/rancher/rancher/issues/56013 , since /v3/connect/agent is not responding, the rancher2_connection_info.json got replaced with an empty file on all downstream cluster nodes.

Is there anything I can do to further debug this issue?

Hi, How do i install the Rancher Desktop Privileged Service? I installed the Rancher Desktop but i'm not seeing the service

We have usecase saying that a single node rke2 control plane node on physical server and want to autoscale the worker node joining my rke2 cluster as we see pending pods. I saw on internet and got around to using Metal3 but still i have some questions and need help. How shall i boot and join and remove the nodes from cluster. Where i have to define userdata and ip credentials.

When I execute this command to an rke2-based cluster running rancher, it consistently takes 60s to get a response...what's the best way to debug the issue?

kubectl get --raw \
  '/apis/ext.cattle.io/v1/tokens?allowWatchBookmarks=true&resourceVersion=2903900033&watch=true' -v10

Rancher image origin files and source files, is anybody using them these days? Eg. github.com/rancher/rancher/releases#…

rancher-images-origins.txt

and

rancher-images-sources.txt

Hello everyone, looking for a review on this PR when anyone has a moment in rancher support-bundle-kit repo: github.com/rancher/support-bundle-kit/pull/185 It’s been sitting for a bit and I’d like your comments and reviews regarding the fix. Thank you

Hello everyone, I am facing an issue with Rancher Desktop. When I click on the application icon, it fails to start and gives me the following error:

When I search with helm and look at the index file it doesn't have all the stable versions in it. Shouldn't this have them there? releases.rancher.com/server-charts/stable/index.yaml

Hello, I want to ask about Rancher Web UI. I notice in docs there is integration for VM using harvester. Does Harvester is mandatory or plain kubevirt also supported?

Hi everyone! 👋 I'm Adriel from Pampanga, Philippines. I'm a Senior Software Engineer with 7+ years of experience building scalable systems and AI-powered solutions. I love working with LLMs, RAG, and backend tech—always excited to learn new things and share what I know. I'm here to connect, collaborate, and help onboard new people into the team. If you're new or just want to chat about tech, feel free to reach out—I'd love to get to know you! 😊

set up a reminder on “Join us for a Rancher Live episode to learn how WSO2 are building atop Rancher & Harvester with the Open Cloud Datacenter project” in this channel at 2PM today, Greenwich Mean Time.

Hi all 👋 I put up a PR a little while ago that adds optional time-based log collection to

rancher/support-bundle-kit

. It is super handy for RCA when incidents happen (no more digging through thousands of logs!). It's opt-in via an env var, otherwise behaves the same as before. Would love your 👀 and thoughts when you get a chance! PR link: github.com/rancher/support-bundle-kit/pull/189 Thank you

Reminder: Join us for a Rancher Live episode to learn how WSO2 are building atop Rancher & Harvester with the Open Cloud Datacenter project.

Hello folks, our streaming provider malfunctioned at the last moment & we were only able to stream on LinkedIn. Please join us here -> linkedin.com/events/7488131659796742145?viewAsMember=true