it says “Extension support is not enabled ”

Hi, is there anyone who managed to get a cluster up and running i just get "Rancher 2.7 Cluster agent is not connected" and i'm not the only one having this issue. Seems like every new user is having same issue and stops using rancher. Would appreciate it someone could help out https://forums.rancher.com/t/rancher-2-7-cluster-agent-is-not-connected/39766/1

I'm having a really difficult time upgrading from rancher 2.5.17 to 2.6. My downstream clusters are on v1.20.15-rancher2-1 which is supported by 2.5.17, but I cannot find a 2.6.x release that also supports v1.20.15-rancher2-1 (only rancher 2-2). The only version I do see in rancher 2.6.7-rc9 which I can't find a helm chart for. I believe this is causing my downstream clusters to not sync

Is there a version of Rancher 2.6.x that supports v1.20.15-rancher2-1 or a version of Rancher 2.5.x that supports v1.20.15-rancher2-2?

How do I set the AWS Placement Group when creating nodes?

Hey folks! what does this error means

mustkim@MustkimsPC:~/Desktop/kuma_/kuma$ sudo make -j k3d/restart
make k3d/stop
make[1]: Entering directory '/home/mustkim/Desktop/kuma_/kuma'
/bin/sh: 1: /root/.kuma-dev/kuma-release-none./bin/k3d: not found
make[1]: *** [mk/k3d.mk:106: k3d/stop] Error 127
make[1]: Leaving directory '/home/mustkim/Desktop/kuma_/kuma'
make: *** [mk/k3d.mk:155: k3d/restart] Error 2

meanwhile the install location is

mustkim@MustkimsPC:~/Desktop/kuma_/kuma$ which k3d
/usr/local/bin/k3d

I would appreciate any helps!

Hi Team I am testing the RKE2 deployment with dual stack by passing the ipv4 and v6 address for cluster and service CIDR. But facing an error message of "cluster-cidr: [10.42.0.0/16 2c0625f1cd1110::/80] and node-ip: [172.21.50.20], must share the same IP version (IPv4, IPv6 or dual-stack)”. I have not passed any value for the node ip in the config.yaml, it is automatically determined. Need a help in understanding why is it designed this way to specify for node ip as well.

As a side project I've been working on a Prometheus exporter specifically for Rancher. Note this is a community project and not official. If anyone wants to give it a go and has any feedback (including anything to add) please raise a GH issue. Thanks 🙂 https://github.com/David-VTUK/prometheus-rancher-exporter

good day, please have a look at this https://rancher-users.slack.com/archives/C3ASABBD1/p1682493079592159

Hi all can someone help solve this error ? INFO ] [dialer] Setup tunnel for host [192.168.65.4]84714 am[ERROR] Failed to set up SSH tunneling for host [192.168.65.4]: Can't retrieve Docker Info: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?84714 am[ERROR] Removing host [192.168.65.4] from node lists

Does anyone have experience in Rancher + RKE2 + Calico and using eBPF dataplane? Rancher/RKE2 websites don’t describe that, but Calico website says that it can be done, but not during installation rather only as post-install configuration https://docs.tigera.io/calico/latest/operations/ebpf/enabling-ebpf

~Hello, anyone experienced with custom cluster plus autoscaling feature? I'm not able to find docs to support /clarify my query I'm using custom clusters (deploying from scratch) and later installing autoscaler (as per instructions in rancher page docs) Scaling out (up), works smoothly nothing to add here Scaling in (down), the cloud provider will remove node as expected but within rancher manager (cluster management, cluster itself page) the node entry still there any way of having it removed, from rancher manager (cluster management UI), in the scaling in process?~

Hi everyone. I have k3s installed on a lab system. i recently did some experimenting and i might have used a wrong port as since this hapened i receive the following error on using kubectl:

kubectl get pods
Unable to connect to the server: x509: cannot validate certificate for 127.0.0.1 because it doesn't contain any IP SANs

As this is a lab system. we have not configured backup. Is there a way to recover from this issue without having to reinstall the entire cluster?

Hi folks, Getting this error on running

kubectl

W0503 17:00:45.972009   48730 transport.go:243] Unable to cancel request for *exec.roundTripper

Rancher-Desktop Version: 1.8.1 Mem: 6GB, Cores: 2 Container engine: dockerd (moby) I’ve disabled K8s in RD but the problem persists. Seems RD modified some kubectl config.

Hello, We're currently running rancher-backup operator version 2.1.5 and we notice there is a major version out v3.1.0. What would be the recommended approach to upgrade from v2.1.5 to v3.1.0? is it possible to directly upgrade or is there an alternate strategy we can follow?

++ We're running Rancher v2.6.9 here https://rancher-users.slack.com/archives/C3ASABBD1/p1683115416852219

I have create my management cluster, and when I try to create my first downstream, I get this weird error:

Failed to create fleet-default/psi-rancher-infra <http://cluster.x-k8s.io/v1beta1|cluster.x-k8s.io/v1beta1>, Kind=Cluster for rke-cluster fleet-default/psi-rancher-infra: Internal error occurred: failed calling webhook "<http://default.cluster.cluster.x-k8s.io|default.cluster.cluster.x-k8s.io>": failed to call webhook: Post <https://webhook-service.cattle-system.svc:443/mutate-cluster-x-k8s-io-v1beta1-cluster?timeout=10s>: proxy error from 127.0.0.1:9345 while dialing 10.42.5.129:8777, code 503: 503 Service Unavailable, failed to create fleet-default/psi-rancher-infra-pool1 <http://cluster.x-k8s.io/v1beta1|cluster.x-k8s.io/v1beta1>, Kind=MachineDeployment for rke-cluster fleet-default/psi-rancher-infra: Internal error occurred: failed calling webhook "<http://default.machinedeployment.cluster.x-k8s.io|default.machinedeployment.cluster.x-k8s.io>": failed to call webhook: Post <https://webhook-service.cattle-system.svc:443/mutate-cluster-x-k8s-io-v1beta1-machinedeployment?timeout=10s>: proxy error from 127.0.0.1:9345 while dialing 10.42.5.129:8777, code 503: 503 Service Unavailable

I've used nicolaka/netshoot do verify that I can resolve webhook-service.cattle-system.svc from within the cattle-system namespace, I have also not found any logs from any fleet pods indicating any errors or issues. I tried the suggestion in this SuSE kb article recreating the webhook helm deployment, but no success. This is v2.7.2 off rancher. Any suggestions?

Hello, i'm new using any type of docker, i've tried to build an ubuntu docker but when i do "docker build -t ubuntu:latest ." it says this " ERROR: failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to read dockerfile: open /var/lib/docker/tmp/buildkit-mount872211/Dockerfile: no such file or directory "the only thing i've done is add the image in the rancher but i don't know if it needs anything more

Hey everyone, I've been on the hunt for a Terraform module that edits the aws-auth configmap (from EKS) when creating a cluster. I came across a few solutions, some workarounds, and others that made the whole cluster with the changed configmap. But, what I needed was a separate module to run after the main EKS creation resource. It might be handy for your projects (automating roles is always a good idea): • Repository link: https://github.com/cayohollanda/terraform-aws-eks-auth • Terraform registry link: https://registry.terraform.io/modules/cayohollanda/eks-auth/aws/latest?tab=inputs If it helps you out, please give it a star. If you have any questions, just drop me a message on Slack and I'll get back to you as soon as I can.

maybe this soluction can help anyone here

Sorry newbie question i am trying to create a NFS type PV and i see this screen. What does server field refer to , is it the NFS server? Also at present we use longhorn storage and would like to replace it with NFS server. One of the REDIS components needs this NFS and it seems like REDIS is deployed as an installed App from Rancher dashboard from helm charts and i don’t see any reference to the Storage in these charts. How do i update the storage class to change from longhorn to use my new NFS server?

Screenshot 2023-05-03 at 11.07.00 AM.png

Hello everyone any one as an idea why rancher agent is looping

time="2023-05-03T17:24:55Z" level=info msg="Plan monitor checking 120 seconds"
time="2023-05-03T17:26:55Z" level=info msg="Requesting kubelet certificate regeneration"
time="2023-05-03T17:26:55Z" level=info msg="Plan monitor checking 120 seconds"
time="2023-05-03T17:28:55Z" level=info msg="Requesting kubelet certificate regeneration"
time="2023-05-03T17:28:55Z" level=info msg="Plan monitor checking 120 seconds"

I checked rancher github but i don’t find nothing.

how do I enable a feature gate through the Rancher gui? I want to enable

--feature-gates=MixedProtocolLBService=true

Trying to resolve error "Error syncing load balancer: failed to ensure load balancer: mixed protocol is not supported for LoadBalancer". We need Port 5060 UDP and TCP on the same load balancer IP

Does anyone know or can help me on how to solve this problem?

What does installed apps in Rancher GUI refer to - essentially a microservice deployed via a helm chart? And how does it differ from the deployments and statefulsets under workloads are they same?