Hi, am deploying Rancher with

ingress.tls.source=secret

and this Secret am creating with openssl pub/pvt keys. Now I want to deploy same from Terraform and planning to either populate pre-created keys in Secret Manager or ACM, which will be fetched during terraform deploy. Any terraform tips pls

Is there any any known way to migrate a downstream cluster from Current Rancher deployment to a new rancher Deployment? I currently have two AWS accounts and have a separate rancher in each one. I would like to create a new rancher in a “central” account, setup VPC peering and have One Rancher to Rule all my clusters.

Hello. What are the IAM permissions that rancher needs in order to import EKS cluster. I am asking only about import. No plans currently to use for creating clusters. So this https://ranchermanager.docs.rancher.com/reference-guides/amazon-eks-permissions/minimum-eks-permissions documentation is about both, but is there such for importing only ?

Hi there! I have an EKS cluster in Rancher that shows 1.22 as the latest available k8s version. What could be the reason I cannot upgrade it to a newer k8s version?

👋 Hello, team!

At my company we are considering using Rancher to deploy our clusters in EKS

I am struggling with one last requirement, upgrade nodegroups one at the time. Is this possible with Rancher?

To add on that I am using Terraform provider, not the UI

Hello, We had an issue today after replacing a managed node group, rancher decided to delete the new node group, and a few more we added manually. Looking at the permissions we've given rancher now I see a lot of uneccesary things, like in our case "eks:DeleteNodegroup" We're not using rancher to provision the clusters, they're created elsewhere and then imported. Do we really need all the permissions listed here? https://ranchermanager.docs.rancher.com/v2.5/reference-guides/amazon-eks-permissions/minimum-eks-permissions

Hello, if i'm right, it is currently impossible to upgrade an EKS cluster from kube 1.22 to kube 1.23: https://github.com/rancher/rancher/issues/40323

I have rancher running in EKS. Rancher 2.6.9, EKS 1.23. I have two downstream clusters both also EKS 1.23. Yesterday one of my downstream clusters became unreachable. Trying to click on it just times out. I have workloads deployed and they are running just fine. The last thing I remember doing was scaling down a nodegroup. Where do I begin to troubleshoot this? @fast-piano-59234 You have given me valuable advice in the past. Perhaps you can assist?

Is there a way to get rancher to provision a kubernetes 1.2.4 cluster on eks?

Hi. Please I need some help on this. Would anyone be kind enough to point me in the right direction. https://rancher-users.slack.com/archives/C3ASABBD1/p1676636834886089

@chilly-toddler-80124 has left the channel

Does anyone have a opinion if you manage an AWS EKS cluster via terraform why you would would pick Generic vs EKS to import the cluster into Rancher? We are building up new EKS clusters via our own terraform and found out that in order to import them via the EKS method into Rancher requires them to have at least one managed node group. We are exploring that if we import via the Generic method might be a better way to go for us, because it allows us to runs our EKS clusters with only self managed node groups. And since we aren't using Rancher to manage our EKS cluster, we don't need that functionality.

What are the supported configurations for the Cluster Autoscaler with Rancher provisioned EKS clusters? If I already have a Rancher provisioned EKS cluster (provisioned with Terraform), and am following the docs here , am I good to go? The Rancher docs only discuss setting up the cluster autoscaler using a Custom RKE cluster: https://ranchermanager.docs.rancher.com/v2.5/pages-for-subheaders/install-cluster-autoscaler

Hello, we are getting error on the GUI when trying to take snapshots. Tried checking if it was space issue but everything seems to be fine. The snapshots are save at /opt/rke/etcd-snapshots/. Could some one point me in the right direction please ?

Hello, we're having trouble importing an eks cluster. Rancher v2.6.9, eks v1.23. Security credentials/permissions are good since we've already imported other clusters from the same account, using the same user. That user is added to aws-auth configmap as system:masters. status is forever pending. complete status from the yaml below. any ideas on what might be wrong?

@here: is anyone faced/facing the below issue when spinning up kubernetes cluster using rancher 2.7.

level=info msg="[Applyinator] No image provided, creating empty working directory /var/lib/rancher/agent/work/

Hello! I'm trying to learn the ropes of Rancher and its capabilities and am curious about its relationship with Amazon EKS, specifically EKS distro/EKS anywhere. Is it possible to set up a cluster using rancher which is running on an on-prem EKS Anywhere/a using EKS distro as the Kubernetes distribution? From the research I've done so far it seems like it is possible but would be an unintended use of Rancher, is this true? Has anyone done this before? Thanks for any advice/clarification!

Hi there, I am working on on proof of concept and trying to deploy Rancher on top of AWS EKS following this documentation: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rancher-on-amazon-eks. At step 6, I don't get an external-IP for the load balancer (it stays in <pending> ). Is there a step missing to integrate Rancher with AWS Load balancer ?

Is anyone aware of success, challenges, documentation around connecting to AWS hosted Prometheus/Grafana services natively today with Rancher?

Has anyone seen this error? I am using the Rancher MCM v2.7.2 to create an EKS cluster to another AWS account. "error retrieving resource lock kube-system/cloud-controller-manager: leases.coordination.k8s.io "cloud-controller-manager" is forbidden: User "eks:cloud-controller-manager" cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "kube-system""

I'm using Rancher to manager a non-EKS EC2 cluster and things are mostly working, but load balancer target groups have no targets in them. I have no idea what is going wrong, how do I troubleshoot this?

@careful-appointment-9763: do you have deployed an ingress-nginx like stated in the documentation?

I'm using the AWS Load Balancer Controller and it is creating the AWS load balancer and target groups, but the target groups remain empty. I'm using Instance target type and have check the labels on the pods, nodes, and service annotations. I'm still not sure what I've missed

Hi guys, we are running Rancher

2.7.3

and would like to update our EKS Cluster to Kubernetes

1.25

. Actually when we go on Cluster Config to update Kubernetes, we can’t see

1.25

version on UI. Does anyone know why

1.25

is not appearing? Thanks in advance for your help!

Hi folks, the Rancher 2.7.3 support Matrix goes through EKS 1.24. Supporting up to 1.24 (N-2), when EKS is on 1.26 presents an interesting customer experience if we want folks managing EKS clusters with Rancher. Their default deployment version is 1.25 and will very shortly be 1.26. Our Marketplace offering deploys onto 1.23. I'm hoping the new MP offering will at least leverage 1.25 but should target 1.26 or we'll be outdated very quickly. Can I ask what the plans are for this offering? Posted in #rancher-setup

@acoustic-motherboard-98931 has left the channel

What happened in this dashboard before upgrading to 2.7.3? It is showing up pods information here, btw I'm using EKS 1.25