Hi, We're running an RKE1 cluster in Rancher 2.6.5 in an air-gapped environment. I need to configure aws as the cloud provider but it turns out we don't have our CA in the kubelet, kube-controller-manager, etc... pods. The CA bundle is on the node itself in /etc/ssl/certs. How do I configure rancher to mount that directory into all of the pods? I found this but I don't think it's quite applicable to our setup

I have installed Rancher 2.6.8 on k8s with the helm chart value useBundledSystemChart=true. I have noticed at startup the rancher leader pod is replacing the bundled charts. For example, execing into the pod I see /var/lib/rancher-data/local-catalogs/v2/rancher-charts/4b40cac650031b74776e87c1a726b0484d0877c3ec137da0872547ff9b73a721/assets/rancher-webhook being updated. Why is this happening if we set useBundledSystemChart=true.

Hi guys! How long RKE1 will be maintained? Does it make sense to start new cluster using RKE1 instead of RKE2? If i remember correctly RKE1 use docker and there was a problem with dockershim. Is there any upgrade scenario for downstream cluster using RKE1 to RKE2?

Hello! Was anyone able to get the VSphere Cloud Driver to successfully work in a vSphere 8 environment? I’m running into some odd issues and noticed that the support matrix only seems to support vSphere 7(https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-7-0/).

Hey all, Don't know if you already go through this, but I'm facing a issue with rke. Basically, I was trying to add a node on a cluster but it seems everything is stuck. Right now, rke is showing that the cluster is upgrading ( which is not ) and doesn't allowed me to add/remove nodes. Do you guys have any idea what could be ? TIA

Hey all, i am trying to install an RKE2 custom cluster. When i am executing the given command by rancher on the nodes, they show these errors in there logs:

Hi! I'd like to deploy RKE1 Kubernetes Clusters on VMware and I'm looking for a way to implement proxy settings - but I couldn't find the regarding options. Do I have to implement them via cloud-config.yaml by "cmd"?

Is there a way to exclude only certain privileges in Rancher as part of RBAC rather than adding all the resources and selecting the privileges for each resource, I want to exclude only the cluster, nodepools and nodes deletion access, but should have all other access specifically to all custom resources within the cluster.

I enabled the aws cloud provider in my rke1 cluster, but it doesn't appear to be happy with my host names. Our host names follow the format of ip-xxx-xxx-xxx-xxx, apparently the k8s cloud-provider is looking for the format ip-xxx-xxx-xxx-xxx.region.compute.internal. This left the cluster in a weird state with new control plane and etcd nodes in rancher that don't resolve. Has anyone run into this before?

hello, i have a problem with rancher desktop. when i download the file: https://github.com/rancher-sandbox/rancher-desktop/releases/download/v1.7.0/Rancher.Desktop-1.7.0.aarch64.dmg and look at the info from the app, I am told this is an Intel version. where can i get an apple silicon version?

I’ve been fighting Rancher for weeks trying to get the legacy components removed, however in the Rancher server container logs (rancher is in docker), I keep seeing the following for all the clusters. I don’t have cluster or project monitoring or logging enabled, all the alerts and notifers, etc have all been removed. I can’t find anything left over. What in the heck can I do?

2023/01/19 16:17:49 [ERROR] error syncing 'system-library': handler system-image-upgrade-catalog-controller: upgrade cluster local system service alerting failed: template system-library-rancher-monitoring incompatible with rancher version or cluster's [local] kubernetes version, handler system-image-upgrade-catalog-controller: upgrade cluster c-m-5hcbznvh system service alerting failed: template system-library-rancher-monitoring incompatible with rancher version or cluster's [c-m-5hcbznvh] kubernetes version, handler system-image-upgrade-catalog-controller: upgrade cluster c-qjpsc system service alerting failed: template system-library-rancher-monitoring incompatible with rancher version or cluster's [c-qjpsc] kubernetes version, handler system-image-upgrade-catalog-controller: upgrade cluster c-tgk45 system service alerting failed: template system-library-rancher-monitoring incompatible with rancher version or cluster's [c-tgk45] kubernetes version, handler system-image-upgrade-catalog-controller: upgrade cluster c-jpmb8 system service alerting failed: template system-library-rancher-monitoring incompatible with rancher version or cluster's [c-jpmb8] kubernetes version, handler system-image-upgrade-catalog-controller: upgrade cluster c-hpvn8 system service alerting failed: template system-library-rancher-monitoring incompatible with rancher version or cluster's [c-hpvn8] kubernetes version, requeuing

2023/01/19 161759 [ERROR] error syncing ‘c-tgk45/cl-zf689’: handler cluster-logging-deployer: timeout checking app status, app deployed namespace: cattle-logging, labels: map[app:fluentd], handler cluster-logging-configsyncer: get secret cattle-logging:rancher-logging-fluentd-ssl failed: secrets “rancher-logging-fluentd-ssl” not found, requeuing 2023/01/19 161829 [ERROR] error syncing ‘c-tgk45/cl-zf689’: handler cluster-logging-deployer: timeout checking app status, app deployed namespace: cattle-logging, labels: map[app:log-aggregator], handler cluster-logging-configsyncer: get secret cattle-logging:rancher-logging-fluentd-ssl failed: secrets “rancher-logging-fluentd-ssl” not found, requeuing

Hello, Does anyone know if SUSE cert retake policy is paid or free ? Retake Policy: If you do not pass the exam, you must wait 72 hours before you can schedule and take the exam again

Hi all, I'm wondering what the "best practice" minimum hardware requirements for a Rancher set-up are in production? I know Kubernetes best practice would be around 6 machines/nodes: 3 for HA control plane and 3 worker nodes for HA. What about Rancher? Someone mentioned best practice is 2 complete K8 cluster, i.e., 12 machines/nodes. Is that correct?

Hi everyone, I'm a little confused about the out-of-tree vsphere configuration. The chart for vSphere CSI in the Apps tab appears to be missing but the CPI app is present. Am I missing something or is there a resource that anyone has that can point me in the right direction?

Hi guys, I need some advice, I just removed some nodes from my pool but it seems they are stuck. They have been in this state for hours. What can I do in order to definitely remove them and be able to use my cluster normally? I would appreciate your help Thanks

Hi Team, How do we adjust the virtual memory in rancher desktop ?

[1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

Not getting this error on Docker Desktop though. Anyone can point me to right direction it will be a great help. Thanks,

Hello, after I installed rancher-desktop, and open the dashboard, there is no 'App' tab, how to install helm like rancher dashboard?

Can I expose 443 port in appimage rancher-desktop?

Hi everyone. We're running a lot of RKE1 clusters (v1.23) on Ubuntu/CentOS and would like to migrate from docker to containerd. Is there an official way to do this? There are two KB from Suse but none is mentioning the migration-path. • https://www.suse.com/support/kb/doc/?id=000020536 • https://www.suse.com/support/kb/doc/?id=000020538 How did you migrate your nodes from docker => containerd? Thanks!

I’m trying to understand how the helm charts that are managed by Rancher, for ex

rancher-monitoring

are tracking versions, and which version of the “rancher chart” corresponds to the actual chart/application that will be deployed. If i look at the rancher docs https://ranchermanager.docs.rancher.com/v2.6/pages-for-subheaders/helm-charts-in-rancher i intepret the following that it will deploy version

16.0.0

of the

kube-prometheus-stack

As an example, 100.x.x+up16.6.0 for Monitoring tracks upstream kube-prometheus-stack 16.6.0 with some Rancher patches added to it.

However the latest version is 0.11.0 https://github.com/prometheus-operator/kube-prometheus ?

Hi all, Anybody who might be able to point me in the right direction? I have a single-instance docker install (for a lab) that has been unstable at best (every ~30 minutes it decides to restart the Docker pod), but now it won’t run at all. The pod stays alive but I can’t actually connect to it in any manner:

2023/01/17 20:50:35 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: error creating dynamic rest mapper for remote cluster "fleet-default/islab-rke2-1": Get "<https://10.43.118.172/k8s/clusters/c-m-66t8w548/api?timeout=10s>": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
2023/01/17 20:50:45 [ERROR] [CAPI] error watching nodes on target cluster: error creating client and cache for remote cluster: error creating dynamic rest mapper for remote cluster "fleet-default/islab-rke2-1": Get "<https://10.43.118.172/k8s/clusters/c-m-66t8w548/api?timeout=10s>": context deadline exceeded
2023/01/17 20:50:45 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: error creating dynamic rest mapper for remote cluster "fleet-default/islab-rke2-1": Get "<https://10.43.118.172/k8s/clusters/c-m-66t8w548/api?timeout=10s>": context deadline exceeded

Hi, I am trying to disable Rancher's embedded cluster API feature at compile time (I want to use community CAPI), but Rancher doesn't seem to fully start if this feature is disabled. E.g., fleet doesn't come up. This is what I changed in features.go to try and disable the embedded cluster api. It wasn't present as a feature CRD, so I wasn't sure how else to disable it

EmbeddedClusterAPI = newFeature(
		"embedded-cluster-api",
		"Enable an embedded instance of cluster-api core controller",
		false,
		false,
		false)

Is it possible to disable this? Any pointers are appreciated. Thank you!

Hi. When setting up a Rancher Backup, what is actually being backed up? Is it what is under the "resources"? Or is everything being backed up, so the whole cluster can be restored again?

Hi all, couldn't find anything on this in the official documentation: is there a recommended way/best practice to rotate the default admin account's key (i.e. the account that is used in /etc/rancher/rke2/rke2.yaml) in #rke2?

anyone know if there is a workaround for getting visual studio container tools working with rancher desktop instead of docker desktop?

Hello everyone, I'm new to Rancher and I forgot to set the HTTP proxy when installing version 2.7 :( how can I do this afterwards? Best regards

Hi everyone

can any one help me how to increases the existing rke cluster pod limit Actually i tried edit the cluster.yaml and update the cluster like rke up --update-only but it is not working

please help me on this issue

Hello everyone, I am bringing up RKE2 by adding the cluster-cidr and service-cidr value updated in the /etc/rancher/rke2/config.yaml. Where are these values stored in and can I fetch the values that are used at the time of installation for my analysis. Please help me on finding this.