Hello Everyone, I currently backup my rancher-server in a S3 bucket. I am trying to add the rancher backup to the RKE clusters that I created with the rancher server but apparently in the charts is not available. Is there any way to create backups of the clusters not just the rancher server?

Did anyone try using this helm chart for installing Rancher on EKS? It is giving 404 Not Found https://rancher.com/docs/rancher/v2.5/en/installation/install-rancher-on-k8s/#install-the-rancher-helm-chart

One of rancher-managed clusters is giving the error "Secrets "cattle-system/c-c-[clusterid]" not found". Never taken a note if such secret has existed before, but is there a way to recreate that? Curiously everything works and I can still manipulate the said cluster's resources, but I can't update cluster's settings in rancher.

Good morning folks, we are seeing an “interesting” error after upgrade one of our clusters from gke 1.21 to 1.22. The cattle-agent is reporting the following error:

W0704 12:09:14.026527      40 reflector.go:325] pkg/mod/github.com/rancher/client-go@v1.23.3-rancher2/tools/cache/reflector.go:168: failed to list *summary.SummarizedObject: Internal error occurred: error resolving resource

Which is more or less only a generic error from one of the go “helper” classes. My wild guess is, that the error comes from trying to watch a CRD that is not in place anymore. Did someone of you experienced that issue? https://github.com/rancher/rancher/issues/38184

Hello. I use for most of my setup a terraform provider that setup the clusters for me by using rancher2 api. Have a question about https://registry.terraform.io/providers/rancher/rancher2/latest/docs/resources/cluster#aks_config_v2 the

monitoring

argument in aks_config_v2 is about v2 or v1? Also the plan is to have one separate monitoring cluster that will collect mettrics from other existing clusters, is that doable by using monitoring v2 from rancher2?

Is Rancher 2.6.8 compatible with cert-manager 1.9.1 ?

Hi! I am trying to import an exist eks cluster to rancher version 2.6.8. The cattle agent on the dest eks cluster returns the following error. We are trying to access rancher (on another eks cluster) with internal network. Is there a way to skip the tls verification?

msg="Get \"<https://rancher.internal.me>\": x509: certificate is valid for <http://XXX.com|XXX.com>, *.<http://XXX.com|XXX.com>, not <http://rancher.internal.me|rancher.internal.me>"

Is it possible that join a k8s work node into a k3s cluster?

CrashLoopBackOff:

why and what is the reason behind it

Hi All, I'm looking to deploy Kubernetes cluster in on-prem(private infrastructure). Is there any installation guide or reference architecture available for deployment. As it should be production ready

Anyone observed a bunch of left over helm operations after upgrading rancher to 2.6.8? The main operation succeeded, the proxy container is left running.

Hello everyone I just have a quick question, I've tried to delete unused images via rancher desktop UI but after that, I noticed that I still haven't reclaimed disk space for it. But when I reset all my rancher configs, I get the free space back. Any thoughts?

I have installed rancheros on EC2. OS doesn't have command yum, apt or dpkg. How can I install any other tool to instance?

urgent help needed

Hi, i have cluster.yml file and rke backup of an old cluster created by rancher . How can i recreate it in a new rancher instance?

I guys, I just upgrade from 2.6.6 to 2.6.8, now in deployments where I have many containers, environment / command are not "separated" and if you change the config from the UI the config get totally messed up (example cmd of container 1 get used in container 2 etc). Is there a thing to adapt / do differently with 2.6.8 ?

Hi, I am running an 2.5.9 version of rancher hosted within a rancher cluster. This instance has been fine for about a year, however it has started throwing "Failed while: Wait for Condition: InitialRolesPopulated: True" when I attempt to create a new cluster.

was trying to add nodes to my worker pool on GKE to satisfy a condition for a temporary minio object storage requirement and ran into some google API issues last night regarding auto-scaling, etc. Looking at my options, another factor was available memory on my choice of VM's on GKE, so figured I'd do a rolling upgrade to satisfy more mem. Checking out https://rancher.com/docs/rancher/v2.6/en/cluster-admin/upgrading-kubernetes/ 1. for 2.6.6 and I see, "In the Upgrade Strategy tab, enter the Worker Concurrency as a fixed number or percentage. To get this number, you can take the number of nodes in your cluster and subtract the max unavailable nodes." Where is this tab? Is this in options when you click to "Next: Confgure Cluster"? Is there a better link that more accurately reflects 2.6.6?

or maybe I should be altering the cluster.yml directly?

also it seems that I am running RKE and not RKE2 based on the UI advanced options. I wonder if I should follow this before anything else. https://docs.rke2.io/upgrade/automated_upgrade/ thinking the same sort of plan approach could be used for altering my nodes (not at the same time!)

Hello Everyone, I currently backup my rancher-server in a S3 bucket. I am trying to add the rancher backup to the RKE clusters that I created with the rancher server but apparently in the charts is not available in the market. Is there any way to create backups of the clusters not just the rancher server? would it work with any cluster if I install it via helm? thanks in advance

sooooo... I was trying to model my gke cluster like I would model an on-prem cluster by tainting nodes as noexecute and dedicating them to longhorn but that seems to be causing more problems that what it's worth... as evidenced by my constraints for deploying minio and performing an RKE2 upgrade (the system upgrade plan kinda wants to execute on nodes... who would have thought! LOL). Ah... live and learn.

It sounds like the nodes may need to be cleaned up - see this comment https://forums.rancher.com/t/reinstall-after-cluster-teardown-not-working/19005/3?u=catherineluse

Hi All, looking for some help with an issue we are seeing; Rancher was reinstalled and the previously existing cluster re-imported. That cluster had istio installed through the UI, and after importing the rancher UI now reports istio as not being enabled. Can see this in the api, istioEnabled is definitely set to False. Is there a way we can get the UI/Rancher to recognise the existing istio installation?

Hi

I am trying to install rancher getting below error

any suggestions

WARN[0028] Can't pull Docker image [rancher/rke-tools:v0.1.87] on host [10.130.156.101]: Error response from daemon: Get "https://registry-1.docker.io/v2/": read tcp 10.130.156.10158820 >3.215.51.67443: read: connection reset by peer

docker is not able to pull the images ..?