morning all. Feeling lazy as the coffee isn't percolating yet in my brain for me to use my google-fu. Is there an easy way to extract everything as yaml from a Rancher server? I know there is the indiviual 'download as yaml' from the UI. Just wondering how it is stored. All in it's etcd or is there a local repo or is there a function to perform this?

s/indiviual/individual (as in targeted for each type of resource)

Use case: I'd like to be able to pull out my configurations so someone could recreate what I have done over time without being 'locked in' to using Rancher server to do the same thing on their own k8s distro, particular environment, etc.

Hey, anyone know of a good way to delete rancher v1 apps without deleting the workloads? Looking to move them over to a gitops solution without causing disruption

do i need additional configuratiton on my gke ingress nginx? I got rancher HA deployment deploYed on 3 pods but I cant access it via the ingress loadbalncing ip/url

Why doesn't rancher / rancher agents update the ip address in rancher management console if its changed? ( dhcp )

reading the the doc and it says I need to do TLS termination on the ingress-nginx load balancing IP when deploying rancher withh helm. does anyone have more info on how?

After joining an agent node, I can see it from the server, but I cannot see the server from the agent:

# kubectl get nodes
The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?

Do I need to specify the server node address somehow?

I tried to deploy with : helm install rancher rancher-stable/rancher \ --namespace=cattle-system \ --set-hostname=x.x.x.x.sslip.io \ --set-replicas=3 \ --set tls=external and still dont work

x.x.x.x.sslip.io is the public ip to myu nginx load balancer

ubectl get service ingress-nginx-controller --namespace=ingress-nginx NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE ingress-nginx-controller LoadBalancer 10.36.6.88 x.x.x.x 8032731/TCP,44332638/TCP 27h

My apologies to the Rancher team members on here. I am obviously peeved about the server-url/cert change issue after installation and still think you need to provide better guidance or strict warnings but

I'm over that and just wanted to say I think you guys are on to something and really appreciate the effort you have put into not only Rancher but the whole SUSE ecosystem.

I’m trying to install Rancher on a single server just to make running some dev ops on a single box easier. I’ve followed the instructions here: https://rancher.com/docs/rancher/v2.5/en/installation/other-installation-methods/single-node-docker/ but it doesn’t seem to work. It looks like core-dns won’t deploy and I can’t seem to create any other deployments either… they all just sit in “pending”…. not sure where to begin troubleshoot to resolve this issue!

Hi! We have some automation to install the latest release of Rancher CLI. Last night our pipeline broke after the 2.6.7 release of Rancher CLI, and the issue is that it seems like the tar.gz's are not available as release assets, ref. https://github.com/rancher/cli/releases. Are someone looking into fixing this, or do we have to rewrite our pipelines?

Hi is there a guide as to how to enable external access to the components of the rancher monitoring stack?

Hello everyone, I have an RKE cluster with k8s 1.21.13 and I want to upgrade it to 1.22. I have Rancher 2.6.6 running on this RKE cluster. I checked the 2.6.6 compatibility matrix and it says that only 1.22.9 is supported for RKE clusters. The issue is that when I run "rke config --list-version --all", only v1.22.10-rancher1-1 is listed and not 1.22.9. Will the 1.22.10 version work too? Or can I somehow install the 1.22.9 version using the RKE binary?

I'm running Rancher 2.5.12 - I was just removing couple of nodes from one of my clusters, and they were removed from the Kubernetes cluster it self, however they seem to be stuck in the Cluster Manager (don't show up in Cluster Explorer or kubectl nodes) with the message "Waiting on user-node-remove" - Anyone knows of a trick to get them removed from the interface?

When I have encountered this error I found that refreshing the web page worked. The error seems to occur (for me anyway) when a background task completes while I am making changes. This changes the underlying YAML (generates a new version) causing my attempted changes to be applied to an older version. Refreshing the page and attempting the changes again applies the changes to the latest YAML definition. But that is my experience. Your mileage (kilometerage?) may vary.

Hi, Does anybody know how i can update Rancher tls ca, example https://myrancher.com/v3/settings/cacerts?

How can i see more logging of the errors I got when I try to deploy a application via continuous delivery. It stays at "waiting applied" forever

How do set up a default page vs the

Default backend 404

message? I have several hostnames that resolve various subdomains but want to handle the case where a user enters the wrong domain.

Hey guys, question about Worker Node Auto Scaling - For EKS Clusters managed via Rancher 2.6, which Cluster Auto Scaler do we need to use, is the one from Rancher or the one for AWS EKS? Rancher Cluster Autoscaler: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/rancher/README.md AWS Cluster Autoscaler: https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/aws/README.md

Hello 👋 Situation: Rancher does currently not support OCI Registry for Helmcharts. And has currently no plans to do so (as confirmed by Rancher/SUSE). We have a Harbor registry set up and we have an issue there. Feedback from Harbor is, we should switch to OCI registry instead using the "old" chartrepo standard. They also told us that they will sooner or later switch to OCI only and deprecate chartrepo. Question: What can we do now? We have a workaround in place for the Harbor issue, but that can't be there forever. I'd like to avoid switching from Rancher, but I'm starting to get into trouble explaining that now. Especially since OCI Registry is a standard and sooner or later (rather sooner) all others will switch to it. Any ideas?

Hi all, can anyone confirm whether RKE1 has a future or not? Will it be deprecated? Thanks

silly question everyone. Where in the 2.6.6 UI would I edit an auto scaling node group with taint and toleration info?

cluster management/cluster explorer... I have been able to create node pools via cluster reconfiguration but can't seem how to just see where I can edit/via yaml on the pool itself. In cluster management I can see my nodes and via that they talk about machine pools, of which none of mine are in a pool.

this is very cluster provider (ClusterAPI) specific and just not sure where in the UI it is providing us with where we can add those taints and tolerations so when it provisions a new node those labels will be applied automatically.

cluster management and then config of cluster show me where I can adjust properties of the node details and group details but the node details for taints and labels are not editable and there is nothing for the group in that respect. I have an autoscaling group for worker nodes and I have just created a node group that can handle the longhorn CSI which I want to dedicate for just longhorn but within the same cluster.

Is it possible to run Rancher 2.6.6 in Docker 20.10.17 on Ubuntu 22.04 without making a cgroup2 mod as follows:

GRUB_CMDLINE_LINUX="cgroup_memory=1 cgroup_enable=memory swapaccount=1 systemd.unified_cgroup_hierarchy=0"