Hello! How difficult would it be change the pods' and services' subnets on RKE2 rancher?

Is there an appropriate channel to suggest improvements? I have just had to work through issues not directly related rancher but I feel the status messaging could have been less terrifying, if developers are open to hearing my story

Hi guys, I installed some HelmChart resources using the k3s manifest. Now, I want to use helm to take ownership of those deployed workloads. But if I delete the

HelmChart

resource, the workloads will be deleted as well. Is there a way to stop this? Thanks

ICYMI - https://rancher-users.slack.com/archives/C01GKHKAG0K/p1790086559442939

Hi @limited-pizza-33551, I’m currently working on the GPU View stack for Portainer. The goal is to consume DCGM Exporter metrics and surface the relevant GPU information and utilization metrics directly in the Portainer dashboard. Does Rancher have anything similar in terms of GPU monitoring/visibility that I could use as a reference for the dashboard design and the metrics they expose? I’ve already built a script that collects and reports the GPU stack details across the Kubernetes cluster. You can take a look here: github.com/ShubhamTatvamasi/gpu-operator/blob/…/gpu-cluster-report.sh Any references or examples from Rancher would be really helpful as I shape the GPU view. Thanks

Hi everyone! I recently tried using Rancher (manager) to manage an AKS cluster and ran into a few problems, including the fact that Rancher doesnt support Cilium as a Network Policy. I realized that the Azure community seems almost non-existent (#C010UHEMYDT has 🦗 sounds 🎵 ). Anyone have insight as to why it seems Azure is marginally used with rancher employee ?

We upgraded to Rancher v1.36.4 and running into an issue where some CRDs were upgraded. I traced the issue down to the `system-upgrade-controller`Helm chart failing. How can I troubleshoot this issue? I'm failing to see an actual error. Also, the `system-upgrade-controller`seems to hang indefinetely.

Good morning. I apologize for being the bearer of bad news, but the website get.rke2.io is no longer available. I don't know if this is a geo-fencing issue for EU, but it doesn't work for Germany or Romania.

Hello, I am using Rancher v1.24.0 with kubernetes v1.36.4. I am seeing a frequent error message "Error response from daemon: failed to connect to the backend: timed out dialing Hyper-V socket". I am seeing this both on the Containers tab and when I try to run any Docker command using PowerShell. Can anybody help me figure this out?

Hey Rancher Community! Looking to get more out of your Kubernetes deployments, streamline your VM migrations, or harden your container security? Join us for our upcoming free, interactive workshops and live demos designed to help you scale seamlessly: • SUSE Rancher Rodeo - October 8th : Deep-dive into enterprise Kubernetes management at scale. • SUSE Virtualization Rodeo - October 22nd: Modernize and migrate your legacy VM workloads using cloud-native stack technology. • Kubernetes & Container Security Made Easy - October 13thth: Learn how to easily secure containerized workloads with enterprise-grade protection. Get hands-on guidance, ask questions live, and see what’s possible when upgrading your stack. View our upcoming Virtual Events Here!

Hey Rancher Community! Looking to get more out of your Kubernetes deployments, streamline your VM migrations, or harden your container security? Join us for our upcoming free, interactive workshops and live demos designed to help you scale seamlessly: • SUSE Rancher Rodeo - October 8th : Deep-dive into enterprise Kubernetes management at scale. • SUSE Virtualization Rodeo - October 22nd: Modernize and migrate your legacy VM workloads using cloud-native stack technology. • Kubernetes & Container Security Made Easy - October 13th: Learn how to easily secure containerized workloads with enterprise-grade protection. Get hands-on guidance, ask questions live, and see what’s possible when upgrading your stack. View our upcoming Virtual Events Here!

I was trying to understand how kubelet on the worker nodes works relative to the controlplane nodes. And I see that every worker node kubelet configuration connects to 127.0.0.1:6443. Does that mean that basically you don't need to add a load balancer, because the workers will be able to round-robin (or whatever algorithm they use) between control plane nodes and the cluster will continue working even after the first control plane node fails?

Rancher 2.14.4 It seems users with Project Owner roles cannot create namespaces in that project? If I remember this used to work?

Hi team 👋 I'm Akarsh, I have a few open PRs in

rancher/rancher

that are currently blocked waiting for a maintainer to approve the CI workflows. Could someone please take a quick look to review the code and click 'Approve and run' when you have a moment? - github.com/rancher/rancher/pull/56963 - github.com/rancher/rancher/pull/57226 - github.com/rancher/rancher/pull/57467 - github.com/rancher/rancher/pull/57468 Thank you

Is the RKE2 supervisor API that runs on port 9345 dependent on the Rancher manager node in any way? Or does it work independently within a Rancher cluster?

ok…i usually configure Traefik under “Additional Manifests” in the Rancher GUI. However, that seems to be fighting the configuration of somewhere else…where is the proper way to configure Traefik through Rancher now?

hello, do you consider to enroll rancher to the anthropic oss scanner? github.com/anthropics/oss-scanner

This message was deleted.

Hey there, I have a small pr which we would need to be able to keep using STACKIT in the future. Is this something someone can have a look at? github.com/rancher/rancher/pull/57806

This message was deleted.

Hi all, I'm Tokyo-based and use k3s. Nice to be here.

This message was deleted.

Hello there! For unknown reasons:

registry.opensuse.org served the GitHub runner an expired certificate (valid until 2026-05-17)

Seems to be flaky - 2 out of 3 runs showed that issue.

hello, is rancher-monitoring removed from available charts in rancher intentionally? it can be upgraded if already installed, but not newly installed.

Hey everyone, is something going on with the Rancher team or SUSE? it's been over a month without any release candidate or alphas or anything. I've never seen this before. Thanks!

Hosting your own distributed storage is not only a fun learning experience, it’s also a critical foundation for a sovereign Kubernetes Cluster. Join us in >5 mins with @astonishing-electrician-70936 for the Longhorn global online meetup and find out what’s new in Longhorn and in the world of Kubernetes Storage. We're going live on LinkedIn and !

Helm v3 end of security fixes is February 10th, 2027 (extended from November 2026): helm.sh/blog/helm-v3-end-of-life The Helm version requirements for installing Rancher is Helm v3: ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/resources/helm-version-requirements Is Helm v4 support for installing Rancher coming soon?

How are we feeling? Is 2027 going to be the year

rancher-cli

gets a browser-based auth flow? Because that would be table stakes circa 2024 sweeeet.

Hi. Anyone successfully managed to add Project Resource Quotas for DRA resources? I’m just getting errors when trying to add some.

🚀 We’re announcing rancher-cli, a new experimental AI-native command-line tool for Rancher Manager, for you and your coding agent. The repository is now public and v0.1.0-beta.1 is out. It’s under heavy development, and we’d like your feedback. Install Linux and macOS:

curl --proto '=https' --tlsv1.2 -fsSL <https://raw.githubusercontent.com/rancher/rancher-cli/main/install.sh> | sh

Windows (PowerShell 7 or Windows PowerShell 5.1):

irm <https://raw.githubusercontent.com/rancher/rancher-cli/main/install.ps1> | iex

Neither installer needs root or admin rights. Dry run first, no prompts Commands like

create

,

patch

, and

delete

need

--dry-run

to preview or

--apply

to make the change. A delete also needs

--yes

. The Rancher server runs the preview with the same permission checks and validation as the real change. If the change would fail, the preview fails too. There’s no “are you sure?” prompt: a prompt can’t be scripted, retried, or audited, and a coding agent either gets stuck on it or pipes in a “yes”. It also comes with • Readable output by default, and versioned JSON or YAML for scripts from nearly every command with

-o json

or

-o yaml

. • Errors with a code and an exit status a script can act on. When there’s a clear next step, the error tells you the exact command to run. •

rancher schema

, a built-in schema an agent uses to learn the CLI: a short overview first, then the full details of only the commands it needs. • A skill that shows your coding agent how to use rancher-cli.

rancher skill install

sets it up for each agent it finds: Claude Code, Codex, GitHub Copilot CLI, and the shared

.agents

directory that Gemini CLI and other agents read. For Gemini CLI alone, add

--agent agents

. • Tab completion for your shell, plus opt-in live completion of cluster, project, and other resource names. • Credentials kept in your OS keychain, or in other stores like HashiCorp Vault through a credential helper. It works with Rancher 2.14 and later, on Linux, macOS, and Windows. Commands and output can change between releases. 📖 Quickstart: https://github.com/rancher/rancher-cli#quickstart 📝 Release notes: https://github.com/rancher/rancher-cli/releases/tag/v0.1.0-beta.1 💬 Bugs and feature requests: https://github.com/rancher/rancher-cli/issues/new/choose