In the "Apps & Marketplace" the chart versions can get very old. e.g. for my Rancher v2.5.7 deployment I see this: Is there a way to get newer charts. Seem that it's pulling from git branch

release-v2.5

and that these charts are not getting updated?

Hi, any clue how to enable boot_diagnostics settings for AKS cluster from rancher2 perspective?

I was able to get rancher deployed in HA using; helm install rancher rancher-stable/rancher --namespace cattle-system --set-hostname=rancher.cluster.local --set-replicas=3 but I am unable to access rancher.cluster.local. rancher.cluster.local is a DNS with IP{ assigned by my metallb local balancer. After I deployed rancher, I only see cluster IP for services and no loadblanacer

ok not sure I am. doing this right but I was able to edit my rancher svc from clusterIP to LoadBalancer and I am able to access rancher url now

I'm running kuberentes 1.20.15-rancher2-1. Can I use firewalld or should I install iptables?

Anyone running k8s 1.20.15 or greater with firewalld? The rancher docs state to use iptables, which is a huge hassel that I want to avoid if possible.

Hi. Rancher Desktop Version 1.4.1 Getting error running kubectl config view command. Looks like Rancher is trying to download an older version of kubectl? Any suggestions?

Hi everybody. I want to create a project with the v3 api of Rancher. Does anybody know how to do this? I can't find any documentation about the api spec.

👋 Hi everyone!

hi. I just successfully created my first kubernetes cluster using rancher and the vsphere driver. provided were several options to boot up a VM. I picked boot2docker, which was marked as legacy. I notice that the "legacy" is very accurate. The OS seems to be quite old and has trouble connecting to letsencrypt-certified HTTPS endpoints. So I'm wondering what the standard way of creating a kubernetes node is for the vsphere driver. all the other options require templates, existing VMs or something else. boot2docker seems to me to be the only option where rancher generates the whole cluster on its own

Hello, I’m pretty sure I have a DNS issue in my Single Node Docker/Rancher 2.x setup - in troubleshooting I keep seeing this:

kubectl exec -i -t dnsutils -- nslookup kubernetes.default
;; reply from unexpected source: 10.42.0.6#53, expected 10.43.0.10#53

I can’t really find a clear path forward, would anyone have any insight as to what I might need to do to resolve this issue?

The installation script for Fleet is failing. https://fleet.rancher.io/quickstart Did anyone experience this?

Hi everyone.. I’ve got a question about rancher on mac. I just installed it as a replacement for the docker engine on my mac and I’m having issues with it not finding local folders for

bind

mounts

Hi Everyone, how safe is to change via the rancher GUI the

server-url

? we are not using lets-encrypt and we create our own certificates and ingress (we use istio). We do not have any upstream clusters yet, and noticed the server-url is incorrect, so does not make sense to keep it incorrect.

👋 Hi everyone!

hi #general team, was wondering can we do this aws-cloud-credentials via an AWS IAM role when i have RKE running on AWS EC2?

Hey everyone, is it possible to create and manage Google Oauth user with Terraform for Rancher2? I can't find an info about Oauth on Rancher's terraform provider

Hi guys, i’m using Rancher v2.6.5 and I want to create a Global Role with permissions to access only in 1 namespace. How can I do that? Any help please? Thanks

On microk8s 1.23, I disabled the registry addon and the message recommends to do the following microk8s disable storage:destroy-storage But I feel like it would disable the default storage addon for eveything. Is that right? And I shouldn't do that if other pods rely on it now.

Good morning. I'm having trouble figuring out how to add users to projects with the rancher cli. I'm going to have to do a query by name which you can do from the API, but I don't see how to do it from the CLI. I was going to use the python rancher client, but it says it's deprecated in favor of the CLI. How do I do this?

Hi! Can I add CSI plugin (vmware storage) to my currently running rke2 cluster? Or it's possible only on creating new vsphere cluster?

Hi, I am creating new RKE cluster using Rancher UI with the help of VMware vSphere provider. After creating RKE cluster, it created new VMs on vSphere and then connect it and ... Finally, the cluster status in Rancher is shown "Waiting for API to be available" and the cluster is not usable. When I check the cluster condition, it is shown like this. can you share your opinion to fix this issue?

hello guys, i'm using Rancher 2.5 and all of a sudden it stopped creating projects. Does anyone know why?

Hi. I have cluster running with cloud-provider=rke2. Can I add vmware CSI to it to add persistent volumes?

Hi, I have a RKE2 Cluster with Istio as ingress, but when I setup

Rancher

with Letsencrypt Certificate. I Cannot anymore

port-forward

and

exec

$ k exec -it rancher-58f6c44c59-zg2ft -- bash
Error from server:

$ k port-forward svc/rancher 8080:80
error: error upgrading connection:

Has anyone an Idea why is that?

👋 Hi everyone!

the kubectl shell in the rancher web interface is outdated:

Client Version: <http://version.Info|version.Info>{Major:"1", Minor:"21", GitVersion:"v1.21.8", GitCommit:"4a3b558c52eb6995b3c5c1db5e54111bd0645a64", GitTreeState:"clean", BuildDate:"2021-12-15T14:52:11Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: <http://version.Info|version.Info>{Major:"1", Minor:"24", GitVersion:"v1.24.4", GitCommit:"95ee5ab382d64cfe6c28967f36b53970b8374491", GitTreeState:"clean", BuildDate:"2022-08-17T18:47:37Z", GoVersion:"go1.18.5", Compiler:"gc", Platform:"linux/amd64"}

For example, I can't run "kubectl create token" from the kubernetes-dashboard docs: https://github.com/kubernetes/dashboard/blob/master/docs/user/access-control/creating-sample-user.md 1.24 doesn't automatically create a token anymore either Is there a way to update that kubectl shell?

Is there any way to automatically clean-up or remove nodes stuck in a registering state in the Rancher U/I after a certain timeout period? I notice with auto-scaling that sometimes a node doesn't join, and gets cleaned up by the ASG/Cluster Autoscaler but is always still in the rancher U/I and has to be manually removed.