How to add proxy in case of installing Rancher UI using helm

Hello experts, we are running Bamboo Application in Rancher Kubernetes cluster. The ingress servers are behind the F5 LB. We are using F5 LB to offload SSL. The communication between F5 and Ingress is on port 80. curl -vvv https://app.bamboo.mycomp.com/rest/remote-event-consumer/1/capabilities The above url is responding with the body referring the other url with "http://app.bamboo.mycomp.com/remote-event-consumer/latest/events/stash-pullrequest-rescoped-remote-event" - means with http There is a parameter in Bamboo to configure base url, we configured that as well as https://app.bamboo.mycomp.com We tried these settings as well.

<http://nginx.org/redirect-to-https|nginx.org/redirect-to-https>: "true"
<http://nginx.ingress.kubernetes.io/ssl-redirect|nginx.ingress.kubernetes.io/ssl-redirect>: "true"

Still not working. Ingress controller details: image: private.artifactory.mycomp.com/rancher/nginx-ingress-controller:nginx-0.49.3-rancher1 imagePullPolicy: IfNotPresent image: private.artifactory.mycomp.com/rancher/nginx-ingress-controller:nginx-0.49.3-rancher1 imageID: docker-pullable://private.artifactory.mycomp.com/rancher/nginx-ingress-controller@sha256:1617a3df09627d8b3b9b9d54c4791637dbbc6c75ec213f9d2ec886d82b03b48c (edited) Is there any setting we need to do in the ingress to update all the content in the body reffering http://app.bamboo.mycomp.com to https://app.bamboo.mycomp.com (edited)

Hi Guys, I am provisioning new AKS cluster from rancher with existing vnet and subnet. Rancher is trying to create a new VNET even though I have mentioned

virtual_network, virtual_network_resource_group, subnet

in

aks_config_v2

. Did anyone be able to create aks cluster with existing vnet and subnet using

kubenet

as network plugin

FYI: After upgrading to Rancher 1.5 on an M1, none of my previous containers seemed to work anymore and also seemed to have been maybe detecting the wrong architecture and was spewing hard to diagnose errors when starting containers w/freshly pulled images. After various debugging attempts, reverting back to 1.4 seems to work fine. Sorry, moving to #rancher-desktop

Hey folks -- we're looking to get some feedback from the community on whether folks would like us to re-add the

--docker

flag to k3s 1.24+, you can read our reasoning here: https://github.com/k3s-io/k3s/pull/5916/files#diff-39ad330180a5add99095027b6f60c62d12f0ffa6e7b569959c3a29f0dc68ede0

Hello guys, I have a problem in Banzai logging operator. When I deploy that in my environment, an error occurs in container log like this >> ""rancher-logging-root-fluentd.cattle-logging-system.svc.cluster.local', err=4): Domain name not found"" The problem is that my domain name is different than "cluster.local" and I have to change that during installation in helm chart like other deployments. I red documents but didn't find and labels or options to set it during chart installation. my rancher is 2.6.3 and the kubernetes engine is RKE. I would be greatful if someone help me fix this problem. because I do really need this logging operator. thanks alot.

I cannot get get Rancher 2.6.6 to install on GKE

Hey ya’ll! I’m having trouble setting up an HA RKE Kubernetes cluster in Digital Ocean using rke version v1.3.12.

Experts, I seem to be hitting a bug. An alert is firing from time to time

etcdHighNumberOfFailedGRPCRequests

etcd cluster kube-etcd: 100% of requests for Watch failed on etcd instance <instance>

A quick search shows this issue, https://github.com/rancher/rancher/issues/29939 , which is a bit old (from 2020). Might have been fixed since, but I'm still having it

And I'm using the latest 100.1.2+up19.0.3 rancher-monitoring chart

Hello, quick question regarding Rancher-Desktop on Ubuntu, how is it possible to access the services without port-forward. In WSL2, it is straight forward, but for some reason same concept doesn't work here.

Hi Lads, I’ve got a problem with Rancher v2.6.5. I’m trying to create a cluster using RKE2 on vSphere. For example I’m creating 3 etcd nodes, 2 control planes and 4 workers. The cluster is prepared, etcd and a control planes are up but non of the workers are joining the cluster. It doesn’t matter a number of the nodes always workers stay out.

HI! The documentation suggests that all nodes should have static IPs assigned https://rancher.com/docs/rancher/v2.5/en/best-practices/rancher-server/rancher-in-vsphere/ But how do you accomplish that with rancher launched vsphere cluster ?

Thanks Andreas for your reply, my rancher is up and running, I would like to use that Rancher to spin up downstream clusters for testing purposes

Hi guys, I have a very dumb question, I have a Rancher installed on an Amazon EKS cluster, that is installed in the default VPC, then if I want to install a RKE cluster (managed by Rancher) in a different VPC than Rancher, should be made a VPC peering between VPC default and VPC of RKE?

On Rancher 2.6.6, I can't view logs 😞

Is this a known issue?

Hello

Hi, I hope this is the right place to ask for help. One of my rancher clusters lost access to the rancher management console, and kubectl can't connect. I think it is the cattle-node-agent or cattle-cluster-agent that is down . I cant conect to my k8s cluster .

Another Friday, another k3s weekly report! https://github.com/k3s-io/k3s/discussions/5964

Hello how to install rancher on kubernetes ? Cos, when i tried to install i only got 502 and 503 errors.

why am I using rancher server again? [rhetorical frustrated question] chicken and egg problems. By the time I figure out how to properly change the server-url and ensure cert-manager is the correct version to allow letsencrypt instead of a self signed certificate I might as well using the Lens IDE, which I'm using to 'fix' rancher, so I can deploy clusters.

s/using/use

Hello everyone. I'm facing an issue with Rancher where both the eks-operator and Rancher pods are crashing due to a boundsError related to the buildUpstreamClusterState function. I assume this is related to one of the EKS clusters we have added. I'd like to remove those clusters from Rancher, however since many of those clusters were provisioned using Rancher, when I delete them it also deletes the whole cluster from AWS. Is there any way to prevent this on version 2.5.15? I was able to prevent this on another Rancher instance running 2.6 by editing the clusters.management.cattle.io, clusters.provisioning.cattle.io and EKSClusterConfig resources and removing the finalizers, but clusters.provisioning.cattle.io and EKSClusterConfig do not seem to be available on 2.5.15. Any help would be greatly appreciated.

I have a demo next week and on my environment (2 Ubuntu VMs, 1 rund Rancher the other a single node cluster) I see that when the VM with the single node cluster reboots it fails to restart the K8s cluster. I see some of the containers come up in docker ps for a few seconds but then they die right away. Anyone got a pointer how to troubleshoot this?

I have four Ubuntu 22.04 VMs running. One of them is my RKE workstation that has SSH tunneling established to the other three VMs, which serve as my nodes. I’m trying to create an HA RKE Kubernetes cluster so I can install Rancher. I run the

cluster.yml

using rke up. I get the following error.

4 years later? Really guys? Still no supported guidance? https://github.com/rancher/rancher/issues/14731