Hey, I am facing errors while importing EKS cluster, rancher is deployed on another EKS cluster, anyone got any clue?

• Wait for Condition: InitialRolesPopulated

• Validation failed in API: cluster kubernetes version cannot be empty string

hello friends, I'm working with a really old cluster (k8s v1.18.0) today and I'm trying to figure out what's causing the cluster to apply Limits and Requests to all of my pods, I don't see any PodSecurityPolicies or similar that would be handling it, I've sorted through all the CRDs on the cluster as well but the issue we're seeing is just no matter if I set limits / requests on a pod, or not, the pod when it comes up has them applied. so I figure there's some policy in place that's causing it, any idea how I can dig further to research why this is happening?

Hello All, When I am importing EKS cluster it got stuck in Provisioning state(Waiting on eks crd to be initialized). Did anyone face the same issue?

I run a Rancher instance that was initially deployed at version 2.5.X and just noticed i have some 1300+

PipeLineSettings

resources which i think has been removed and replaced by Fleet https://ranchermanager.docs.rancher.com/v2.6/pages-for-subheaders/pipelines. Is it safe to just delete all of these unnecessary resources since Rancher hasn't cleaned them up?

Hello, I am facing errors on one of master node in Rancher.

Hello, I am facing errors on one of master node in Rancher. Does anyone know how to resolve this issue? Thanks

0607 14:02:05.757155      1 serving.go:348] Generated self-signed cert in-memory
 W0607 14:02:06.107438      1 requestheader_controller.go:193] Unable to get configmap/extension-apiserver-authentication in kube-system. Usually fixed by 'kubectl create rolebinding -n kube-system ROLEBINDING_NAME --role=extension-apiserver-authentication-reader --serviceaccount=YOUR_NS:YOUR_SA'
 unable to load configmap based request-header-client-ca-file: configmaps "extension-apiserver-authentication" is forbidden: User "system:kube-controller-manager" cannot get resource "configmaps" in API group "" in the namespace "kube-system"

Hello All, we're trying to upgrade Rancher 2.6.12 to 2.7.4 which happens to succeed, however when we try to destroy the cluster, (we create and destroy clusters quite often as part of our CI/CD), it fails with this error. We're running AWS EKS 1.24 I see few users complaining about the same error on RKE and GKE but haven't come across Known issues with EKS. Are there any pointers on what could be wrong here?

│ Error: uninstallation completed with 2 error(s): timed out waiting for the condition; uninstall: Failed to purge the release: Internal error occurred: failed calling webhook "rancher.cattle.io.secrets": failed to call webhook: Post "<https://rancher-webhook.cattle-system.svc:443/v1/webhook/mutation/secrets?timeout=15s>": context deadline exceeded
│ 

│ Error: uninstallation completed with 1 error(s): uninstall: Failed to purge the release: Internal error occurred: failed calling webhook "rancher.cattle.io.secrets": failed to call webhook: Post "<https://rancher-webhook.cattle-system.svc:443/v1/webhook/mutation/secrets?timeout=15s>": dial tcp 100.81.117.143:9443: i/o timeout

Would appreciate your help!

Just FYI for anyone using Jumpcloud with Rancher for auth - we successfully got a mix of ldap and saml working using the shibboleth connection yesterday and are working on documenting the setup. This gives you full user/group lookup with saml app "connectivity" - kind of the best of both worlds.. And you don't hit the issues of either system individually! Happy to answer questions if it's useful to anyone.

Currently I'm running Rancher 2.6.13 with rancher provisioned rke1/1.20 clusters. Does Rancher 2.7.x support these downstream clusters?

Importing a Kubernetes cluster into Rancher (2.7.1) displays this warning:

You should not import a cluster which has already been connected to another instance of Rancher as it will lead to data corruption.

Is there any way to make this a safe operation? I have a k8s cluster that was imported into a rancher installation that we're migrating away from, I want to import that same k8s cluster into our new rancher, but don't want to break anything.

Hi , I follow this page https://www.rancher.com/quick-start and create rke2 on existing node. The status is Reconciling and I could not find Provisioning Log. Could you help?

Hi Rancher community, I would like to reach out to you with a query regarding the support policy for Rancher. While exploring the main page, I have noticed the presence of three minor releases, specifically 2.7, 2.6, and 2.5, which have been highlighted. However, upon visiting the announcement page , I have come across the information that patches for version 2.4 and 2.3 are also being released recently. In order to gain a clear understanding, I need some assistance to clarify the support policy for Rancher. Specifically, I'm curious about the number of supported minor or patch versions of Rancher at any given time. Thanks.

Hello everyone, I'm seeking assistance in investigating the reason behind the failure of new nodes to register in our community. To address this issue, I created a fresh k3s cluster and proceeded to the Registration step. On a clean Ubuntu 22 virtual machine or container, I ran the following command: curl -fL XXXXX/system-agent-install.sh | sudo sh -s - --server xxxxx --label 'cattle.io/os=linux' --token AAAAA --ca-checksum BBBB --etcd --controlplane --worker ) the cluster is clean k3s cluster, the rancher running on clean ubunu22 vm i try to look errors on the logs but i cannot find any error or reason for the problem: Error applying plan -- check rancher-system-agent.service logs on node for more information Despite following these steps, the new nodes are not registering successfully. I have checked the logs but couldn't find any errors or hints about the root cause of this problem. The error message I encountered is as follows: "Error applying plan -- check rancher-system-agent.service logs on the node for more information." I would greatly appreciate any insights or guidance from the community to help me troubleshoot this issue effectively. Thank you in advance for your assistance.

👋 Hi everyone! Where I can find Rancher internal host name. for Docker its host.docker.internal. So what is the host name for Rancher?

Hi everyone, Does anyone have a crash-course on how to configure vsphere in order to automate cluster-creation/scaling? I am have difficulties understanding how the cloud-init configuration should work in vsphere

Hi everyone, I’m facing a strange error in my RKE1 k8s cluster. Running 1.24.13 on vsphere. kube-api-auth is constantly throwing these errors in the logs:

time="2023-06-08T09:21:09Z" level=info msg="Starting Rancher Kube-API-Auth service on 127.0.0.1:6440"
time="2023-06-08T09:21:09Z" level=info msg="Running in single server mode, will not peer connections"
time="2023-06-08T09:21:09Z" level=info msg="Starting workload controllers"
time="2023-06-08T09:21:09Z" level=info msg="Starting <http://cluster.cattle.io/v3|cluster.cattle.io/v3>, Kind=ClusterUserAttribute controller"
time="2023-06-08T09:21:09Z" level=info msg="Starting <http://catalog.cattle.io/v1|catalog.cattle.io/v1>, Kind=ClusterRepo controller"
time="2023-06-08T09:21:09Z" level=info msg="Starting <http://rbac.authorization.k8s.io/v1|rbac.authorization.k8s.io/v1>, Kind=Role controller"
time="2023-06-08T09:21:09Z" level=info msg="Starting /v1, Kind=Secret controller"
time="2023-06-08T09:21:09Z" level=info msg="Starting /v1, Kind=ConfigMap controller"
time="2023-06-08T09:21:09Z" level=info msg="Starting <http://rbac.authorization.k8s.io/v1|rbac.authorization.k8s.io/v1>, Kind=ClusterRoleBinding controller"
time="2023-06-08T09:21:09Z" level=info msg="Starting <http://rbac.authorization.k8s.io/v1|rbac.authorization.k8s.io/v1>, Kind=RoleBinding controller"
time="2023-06-08T09:21:09Z" level=info msg="Starting <http://rbac.authorization.k8s.io/v1|rbac.authorization.k8s.io/v1>, Kind=ClusterRole controller"
time="2023-06-08T09:21:09Z" level=info msg="Starting <http://cluster.cattle.io/v3|cluster.cattle.io/v3>, Kind=ClusterAuthToken controller"
time="2023-06-08T09:21:24Z" level=info msg="Processing v1Authenticate request..."
time="2023-06-08T09:21:24Z" level=error msg="found 1 parts of token"
time="2023-06-08T09:22:24Z" level=info msg="Processing v1Authenticate request..."
time="2023-06-08T09:22:24Z" level=error msg="found 1 parts of token"
time="2023-06-08T09:24:00Z" level=info msg="Processing v1Authenticate request..."
time="2023-06-08T09:24:00Z" level=error msg="found 1 parts of token"

Any help would be appreciated.

Hi. I'm trying to follow the directions for an air-gapped installation (https://ranchermanager.docs.rancher.com/pages-for-subheaders/air-gapped-helm-cli-install). I'm able to successfully install K3S and Rancher itself, but I'm noticing that when I connect to my nginx load balancer, the certificate being offered is the TRAEFIK_DEFAULT_CERTIFICATE as opposed to the one that I provided rancher on installation. Has anyone encountered this before, and did you have to update the traefik default cert to get this working?

I'm finding it difficult to deploy Rancher on RKE2 using Fleet, as it looks like the Fleet that Rancher itself installs for CD conflicts with the Fleet I installed onto the cluster to set up everything else. But I've been careful to match the versions.

Before I install Rancher v2.7.3 I have:

release=fleet ns=cattle-fleet-system chart=fleet-102.0.0+up0.6.0

release=fleet-agent-local ns=cattle-fleet-system chart=fleet-agent-local-v0.0.0+s-a308b0cf342cdf1dd6d8e7dde0226eba0bdb8c0cc97d0b2f4c36c86fd11e9

release=fleet-crd ns=cattle-fleet-system chart=fleet-crd-102.0.0+up0.6.0

And then after I install Rancher v2.7.3, this chart has been added by Rancher:

release=fleet-agent-local ns=cattle-fleet-local-system chart=fleet-agent-local-v0.0.0+s-4e4bca490df31d6a3cdca28ee3989d47b6c4ebfb4f9c97ad0b1299a2194e4

The bundles are showing errors like:

ErrApplied(1) [Cluster fleet-local/local: another operation (install/upgrade/rollback) is in progress]

Modified(1) [Cluster fleet-local/local]; priorityclass.scheduling.k8s.io cluster-low missing; priorityclass.scheduling.k8s.io cluster-medium missing; priorityclass.scheduling.k8s.io deployment-machinery missing; priorityclass.scheduling.k8s.io develop missing

It's as if the two agents are fighting over the bundles. The different hash code on the Rancher-supplied fleet-agent leads me to believe it is a different version perhaps.

Oh and its RKE2 v1.24.11.

This is all on the local cluster - nothing downstream.

We have configured our Rancher K8S cluster to use MetalLB as load balancer. When we deployed our database servers on the cluster. The load balancer is always pending. Attached the screenshot. Does anyone know how to resolve this issue or where to dig into further?

Could someone point me to the part of rancher code that manages the lifecycle of provisioning clusters? I was curious why this issue was occurring: https://github.com/rancher/rancher/issues/40552

In Rancher 2.6, I have a local helm repository that I've added to Rancher as a Repository. It contains custom helm charts built by my company. How can I trigger the deployment of a helm chart using the Rancher CLI? When I use rancher catalog ls, I do not see my helm repository. Is there an equivalent option to use for listing cluster repositories? In Rancher 2.5, I simply did a rancher app install helmchart -n namespace --version, but I can't seem to get the same functionality to work with Helm Repositories

•What are the CPU/Memory requirements from the platform to use RKE? Does rancher support single-node implementation?

k3s There is already a multi-cloud cluster solution, so is there a multi-cloud + edge cluster solution that is part of the expansion? Is there a solution for the situation where the edge cluster does not have a public ip and the cloud cluster has a public ip?

Hi Team,

Hello, I install Rancher server and its status is not ready. Below is the output from describe node. Does anyone know how to fix cni plugin not initialized.?

Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----             ------  -----------------                 ------------------                ------                       -------
  MemoryPressure   False   Thu, 08 Jun 2023 07:35:33 +0000   Thu, 08 Jun 2023 06:58:34 +0000   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure     False   Thu, 08 Jun 2023 07:35:33 +0000   Thu, 08 Jun 2023 06:58:34 +0000   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure      False   Thu, 08 Jun 2023 07:35:33 +0000   Thu, 08 Jun 2023 06:58:34 +0000   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready            False   Thu, 08 Jun 2023 07:35:33 +0000   Thu, 08 Jun 2023 06:58:34 +0000   KubeletNotReady              container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized

Hello, Does anybody knows, when vSphere 8 support is planned for downstream RKE1/2 clusters provisioned through Rancher? https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-7-4/ vSphere 7.0u3 is the most recent version supported for Rancher 2.7.4..

we have a problem that in the rancher ui, the local cluster is not visible anymore. we also upgraded rancher meanwhile to 2.7.3 but nothing changed. when i check the management.cattle.io/v3 resource for the local cluster, the k3s version is also not accurate anymore, shows as Kubernetes Version: v1.24.10+k3s1 but when i check the node it is: v1.25.9+k3s1. had anyone the same issue or know how to fix that?