Not sure this is the right forum but I’m having some issues upgrading rom 2.5.16 to 2.6.x (currently just trying 2.6.1, tried all the way to 2.6.6). My downstream clusters go unavailable with these messages, ideas on how I can further troubleshoot this?

error syncing 'c-57xzh': handler cluster-deploy: ClusterUnavailable 503: ClusterUnavailable 503: cluster not found, requeuing

Hey, fleet is giving me an error when we use

kustomize.dir

in our fleet.yaml and point to a directory with a

kustomization.yaml

file in it that references a github link like this

apiVersion: <http://kustomize.config.k8s.io/v1beta1|kustomize.config.k8s.io/v1beta1>
kind: Kustomization

resources:
- <http://github.com/hashicorp/consul-api-gateway/config/crd?ref=v0.3.0|github.com/hashicorp/consul-api-gateway/config/crd?ref=v0.3.0>

The error we are getting is

Error while running post render on files: accumulating resources: accumulation err='accumulating resources from '<http://github.com/hashicorp/consul-api-gateway/config/crd?ref=v0.3.0|github.com/hashicorp/consul-api-gateway/config/crd?ref=v0.3.0>': 'crds/github.com/hashicorp/consul-api-gateway/config/crd?ref=v0.3.0' doesn't exist': no 'git' program on path: exec: "git": executable file not found in $PATH

It would appear that whatever fleet container is doing this processing does not have access to a git executable. We are working on figuring out what container this is and trying to do a custom build of it that includes git. However, I think the public image for this should include the git executable or some alternative to get this functionality working.

Has anyone had luck getting metallb working a cluster built on openSuse physical boxes? From the k8s node itself, I can curl the service IP provided by metallb in layer2 mode and it works. But I can’t access it anywhere else outside a node.

Hey uh, recently it seems our

cattle-cluster-agent

has lost its mind in our sandbox cluster to the point where the cluster becomes unusuable. Whenever it's running, the CPU usage of all of the api-servers in the cluster are pegged at 100%. I'm not sure if this is requests coming in from Rancher or the agent. There don't seem to be any suspicious logs except for the persistent

error syncing 'system-library': handler system-image-upgrade-catalog-controller: upgrade cluster {cluster} system service alerting failing: template system-library-rancher-monitoring incompatible with rancher version or cluster's [{cluster}] kubernetes version, requeueing

. Oddly, we get this message for the cluster whether or not its agent is running. After a little bit, we start seeing errors that seem related to the API server just being too busy, things like: •

Unexpected error when reading response body: context canceled

•

"Reflector ListAndWatch" name:pkg/mod/github.com/rancher/client-go@v1.24.0-rancher1/tools/cache/reflector.go:168 (02-Nov-2022 00:36:47.268) (total time: 29608ms)...

And others. Is it possible to determine what the agent is doing that's causing this? I'm wondering if these nodes are a tad underprovisioned at 2 cores and 8GB of RAM? That seems weird though, they've been fine for a few years now. Also: Rancher v2.6.7 and Kubernetes v1.22.11.

(If any of the kubecon folks are here, this is the "broken cluster" we mentioned)

#general Having an issue with rancher2.6.8 and browsers crashing (firefiox) when multiple log windows are up at the same time

Hello I have a generic and basic question, I want to install rancher desktop on Linux (AWS). The documentation says it requires - x86_64 processor with either AMD-V or VT-X. Does it mean it will not work on normal ec2 instances (t2.large, m5.large etc..) and will work only on bare metal ec2 instances ?

Hello,everyone!I have a question. I want to know that how many nodes a k3s cluster can support? I can not find any similar pages to kubernetes.io

Hello, i ran following command on my localhost to try out the rancher quick start, but when i want to access the page https://localhost i just get http 403 in the browser

sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 --privileged rancher/rancher

Hi we started so quite a lot of these errors intermittently:

Error from server (InternalError): an error on the server ("unable to create impersonator account: error getting service account token: error getting secret: Get \"<https://10.43.0.1:443/api/v1/namespaces/cattle-impersonation-system/secrets/cattle-impersonation-u-7xsnq-token>\": net/http: TLS handshake timeout") has prevented the request from succeeding (get nodes)

Anyone know why ?

for enterprise rancher - can some please help me with yearly subscription pricing?

Hello guys. Im trying to use k3s 1.25 but im facing some issues: I have 3 masters and 3 workers, but sometimes i got this error viewing logs, on shell execution etc...

Error from server: error dialing backend: proxy error from 78.47.195.214:6443 while dialing 195.201.35.245:10250, code 503: 503 Service Unavailable

This just happen sometimes, other times it seems to work...

Anyone know why Rancher is uninstalling the rancher-operator and not reinstalling it on an upgrade from 2.5.16 to 2.6.1?

Help!!! I am running into an issue with Rancher Desktop it appears I keep running into an issue with with Kubernetes starting up. Not sure why it's having this problem. I am going to attempt to disconnect from the VPN that my company recently migrated too. Maybe it's conflicting somehow with the startup. This is the log output. I did try uninstall and re-installing the app and Also tried resetting the application.

}
2022-11-02T23:35:39.575Z: Waited more than 60 secs for nerdctl images to succeed. Giving up.
2022-11-02T23:35:39.575Z: Running: wsl.exe --distribution rancher-desktop --exec /sbin/rc-update --update
2022-11-02T23:35:39.769Z: Running: wsl.exe --distribution rancher-desktop --exec /usr/local/bin/wsl-service k3s start
2022-11-02T23:35:46.113Z: Capturing output: wsl.exe --distribution rancher-desktop --exec cat /proc/net/route
2022-11-02T23:35:46.329Z: Capturing output: wsl.exe --distribution rancher-desktop --exec cat /proc/net/fib_trie
2022-11-02T23:36:07.582Z: Capturing output: wsl.exe --distribution rancher-desktop --exec /bin/sh -c if test -r /etc/rancher/k3s/k3s.yaml; then echo yes; else echo no; fi
2022-11-02T23:36:07.784Z: Capturing output: wsl.exe --distribution rancher-desktop --exec wslpath -a -u C:\Users\marzamor\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\wsl-helper
2022-11-02T23:36:07.995Z: Capturing output: wsl.exe --distribution rancher-desktop --exec /mnt/c/Users/marzamor/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/wsl-helper k3s kubeconfig

If i want to do a chart install like the mirrored chart rke2-cilium or rke2-metrics from a internal repo and during cluster install, what is the best way to do that? Add it to the local cluster, as a global catalogue? Then point it out as a additional chart?

I know cattle is end of life, but hopefully someone here still support the old rancher. Do you know if https://hub.docker.com/r/rancher/lb-service-haproxy has any pensing SSL security issue? it looks like it uses ssl 1.1 so shouldnt be affected by ssl3 recent security issues?

👋 Hi everyone!

Hi guys, We are facing couple of serious issues in rancher. 1.Issue with prometheus • A month back we had 50x more load than usual. Since then we are having issue with prometheus. • We couldn't see the metrics and some of the prometheus pods are crashing and there are going to crash loop backoff state. • We tried a few solutions like increasing the resources, deleting the

/wal

folder but with no success • This is causing some issue in autoscaling i.e horizontal pod auto scaler 2. New users cannot login to rancher • We are not able to add new users using their github account or even manually to rancher • We see this issue - https://forums.rancher.com/t/x509-certificate-has-expired-or-is-not-yet-valid/20518 • We already tried the solution from this post and it did not work We are new to rancher. The guy who has setup the entire thing is not in the team no more. So we are trying trial and error with zero knowledge. It would be helpful if you guys help us resolving this. Thanks..

We have deployed Rancher as a docker container in single-server mode. Can we launch existing docker images that use existing docker volumes ? Looks like the only types of volumes are of type Kubernetes. Currently, we are running images directly on the commandline (

docker run ... -v ...

). How can that be done in a K8S deployment ?

Is there a channel for discussing the MonitoringV2 solution in Rancher? I’ve tried every which way to get Alertmanager to fire alerts for a Project workload without success and was hoping there were some community resources that might be able to tell me what I am doing wrong

I can see my alerts in the Project-scoped Alertmanager, but the alertmanager config doesn’t include any of the routes/receivers that I’ve put into the alertmanager secret in the Project

Hi, who know how to use vSphere CSI for new RKE clusters deployed by Rancher? to know, I created RKE cluster using Rancher and when I wanted to created RKE cluster, I choose vSphere provider among other providers (AWS, Azure, Custom and others), then I filled out few paramters including cluster name, node template, network and cloud provider!! in this part I am not sure what item should be selected (None, in-tree, external ) ??

after creation of RKE cluster, what should I do to use vSphere CSI ??? Do I need to go RKE cluster\App, and choose CSI helm chart and install it ??

I’m trying to track progress of a rancher-backup based on the Backup k8s resource. Anyone know a kubectl command I can use to track the status? I would reference the rancher-backup pod but it’s always running and logs backups in addition to the restores. I just want to see when the restore has “completed”

Hi - my logs/shell tab seems to be stuck at the bottom - how can I expand it ? Very frustrating, seems to be an UI bug? Thanks.