Hi All We are facing sudden issue with our Rancher with AWS which was working fine earlier Its quite some time we were finding it stable until we received the below error while scaling up worker/etd/control plane nodes Error creating machine: Error in driver during machine creation: network.InterfacesClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code=“SubnetWithNatGatewayAndBasicSkuResourceNotAllowed” Message=“NAT Gateway /subscriptions/1797627d-40da-4b11-ad4b-e6015a9692a4/resourceGroups/k8suae/providers/Microsoft.Network/natGateways/bwm-ae-prod cannot be deployed on subnet containing Basic SKU Public IP addresses or Basic SKU Load Balancer. NIC /subscriptions/1797627d-40da-4b11-ad4b-e6015a9692a4/resourceGroups/k8suae/providers/Microsoft.Network/networkInterfaces/prod-4-nic/ipConfigurations/ip in subnet /subscriptions/1797627d-40da-4b11-ad4b-e6015a9692a4/resourceGroups/k8suae/providers/Microsoft.Network/virtualNetworks/rancher_prod/subnets/default has reference to Basic SKU Public IP address or Load Balancer /subscriptions/1797627d-40da-4b11-ad4b-e6015a9692a4/resourceGroups/k8suae/providers/Microsoft.Network/publicIPAddresses/prod-4-ip.” Details=[]; Timeout waiting for ssh key; waiting on node-controller Can someone let me know where could have been the problem occurred as this system was working fine before?

Did anyone decrypt secrets from an ETCD backup using the key from the rkestate?

any insight on when RHEL 9 might be officially supported? https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-7-3/

I just noticed

/var/lib/rancher/logging/rke

is taking up a lot of space. 53gb and only 10gb left on the machine. If I don't care about the logs, is there a recommended way to handle clearing it?

ended up doing

echo

and it seemed to work. thanks anyway

why application is not open justk8s.k8s/kitchen or justk8s.k8s/gym using ingress?

Hi All, I have Rancher_V2.6.11 Deployed in AWS EKS_1.24 With managed nodes (EC2 Instances). Rancher Backups are working (to S3 Bucket with IAM Role) with EC2 Metadata IMDSv1. But when i enable EC2 Metadata IMDSv2 , rancher backup is failing with error (ERRO[2023/05/18 061036] error syncing 's3-recurring-backup': handler backups: failed to check if s3 bucket [svmx-rancher-backups] exists, error: 401 Unauthorized, requeuing). Rancher document says EC2 Metadata IMDSv2 works with rancher. Can you please help here to see if i miss anything?

Warning Unhealthy 77s (x3 over 78s) kubelet Readiness probe failed: calico/node is not ready: BIRD is not ready: Error querying BIRD: unable to connect to BIRDv4 socket: dial unix /var/run/bird/bird.ctl: connect: no such file or directory Warning Unhealthy 69s kubelet Readiness probe failed: 2023-05-18 070310.798 [INFO][233] confd/health.go 180: Number of node(s) with BGP peering established = 1 any one facing this issue K8s: 1.25 HYP: KVM

Team, I am new to rancher, I have installed Rancher with its version 1.6, I can't see the option of tools.

@stocky-account-63046 @brainy-printer-12087

I want to understand the definition of

local cluster

. Does it refer to the Rancher installation? In my case we have on-prem bare metal cluster with Rancher + app workloads sharing the same cluster. I cannot connect to the Rancher cluster. I have the kubeconfig YAML downloaded but not sure on where i am connecting - is it Rancher API Server or k8s API server endpoint and also what is the user?

For some reason i had to add

insecure-skip-tls-verify: true

even though kubeconfig file has the token to connect to the API server

Hello, i'm new using Harvester. I created a storage class called ''test'' with 2 disk tags inside (every disk from separated servers), but when I try to create a volume with the storage class ''test'', it says that the replica scheduling failed Image of error and Storage Class config:

Hey, I been struggling for 2 months to make Rancher webserver work, but I'm stuck with CORS setting... I start to think it may be a bug with Rancher or there is something wrong with my ingress controller. To be more specific, I can access the UI homepage just fine, but I get the following error when I try to authenticate. Anyone has any lead to work on ? I tried many nginx config playing with the CORS setting but no effect. For some Context, I am using nginx-ingress as a nodeport that binds a port xxxx59 to rancher-service 443 port, with some annotations to fix this error .-.

This appers on longhorn... why it appears as unschedulable? maybe that's the problem?

Okay so both nodes are now schedulable but it still says ''replica scheduling failed''

Hi, I have a very general question of weird behavior of my new RKE2 cluster, after my RKE1 cluster decided to commit suicide, we ended up deploying a new RKE2 cluster using the terraform providers from Rancher (I can share the code if needed), it runs in a Debian 10 in a Docker Single Container deployment Rancher Version : 2.7.3 Kubernetes Version : v1.25.9+rke2r1 Node OS : Ubuntu 20.04.2 LTS, latest AMI ami-024e6efaf93d85776 After I saw that our Okta group assigment in the cluster did not work from Terraform, I ended up adding a few Okta groups as Cluster Members with the WebUI, and after taking easily 30 seconds to end the "Saving" step after editing a cluster, I saw that all of the nodes are getting recreated, and my question is, is that needed for a simple cluster member assigment? sounds very overkill to recreate all the nodes for that reason

Hi, we’re running Rancher 2.7.3, RKE with the Amazon EC2 provider - but we’re not seeing the m6 AWS instance types in our node template options - can anyone point me to docs or explanation as to why and/or how to fix?

Hello I'm running Rancher on windows 11, and having memory leak problems when building apps on docker compose, and also some bugs when stopping containers or restarting all on docker-cli On nerdctl it doesnt read docker compose 😞

Hi all

Any idea why the repos are shoing in progress. The rancher version is the stable version and EKS version in 1.26

while I connect to Rancher "kubectl shell" it disconnects me after few seconds of inactivity. Anyone overhere faced the same issue?

Hello

I’m very new in Rancher and Kubernetes

I want to deploy a cluster with vmware with a custom image. The vm is automatically deployed to vmware but waiting for connection infinitely

I also attatch a network in order to give an static ip address to the vm but rancher assigns an ip from a different range…

is there any 101 rancher with vmware that I can follow?

thanks!

Hello! I am currently evaluating Rancher products for a greenfield project. The team is already experienced with k8s, and is looking into products that could accelerate our platform setup. I have a few questions regarding rancher manager and rke2 in particular: RKE2: