Is there a recommended way of keeping downstream cluster roles like

project-owner

in updated when adding new api resources to the cluster? Is manually updating them a potential issue later on?

I have similar requirement.. I would want to set istio injection at Rancher project so that all namespaces can inherit it..but currently that is not propagating. any thoughts?

And when I am trying to run kubectl locally, it gives me below error-

kubectl
I0928 16:56:20.464234   16761 versioner.go:58] Get "<https://127.0.0.1:6443/version?timeout=5s>": dial tcp 127.0.0.1:6443: connect: connection refused
kubectl controls the Kubernetes cluster manager.

hi all, am running terraform with rancher2 provider 1.24.1 trying to get the cluster id through a rancher_cluster resource however I am having 422 error code with the details of fieldname=Cluster name, code=notUnique

is this question appropriated for this channel?

Hi , I have a issue which is I make deployment to rancher, code base is laravel. my application run for 6 hrs or 5 hrs and its stop working on rancher. when i redeploy application its start working again what should be the error. i have one pod running against application. Please help Thanks

We are currently experiencing an issue where we are using a large (360) node cluster using the AWS CNI driver. We have noticed that this puts excessive strain on the Clusters CP/ETCD nodes due to network overload. Also, the rancher local server just randomly times out accepting responses, which ends in "error in remotedialer server 400 / websocket close 1006" errors, and those rancher pods on the local cluster stop accepting any new node registrations (for any cluster). Can't really figure out how to prevent this

Hi all do we have less visibility over the downstream clusters using AKS ? (Nodes Provisioned by Hosted Kubernetes Providers) than with RKE downstream clusters (Nodes Hosted by an Infrastructure Provider) ? Though the Rancher UI can we see same amount of info for both clusters ?

Is there a way to have Rancher delete the load balancer created by the user-addon ? When using terraform to create/destroy, the load balancer (which is created from the user-addon) is not destroyed together with the rke cluster and breaks the terraform destroy because it uses the cluster vnet.

Try posting in #rancher-desktop

Has anyone attempted to deploy an OKE cluster via Rancher? I'm setting one up, and it is going into a creation loop, where it creates a cluster with no nodepools, and then declares the cluster failed to create and tries again.

- I'm running Rancher on version 2.6.8. - I want to create a downstream cluster with RKE2. - I ran the registration command (with all roles) on the newly installed ubuntu 20.04 machine and this error occurred.

[INFO]  Label: <http://cattle.io/os=linux|cattle.io/os=linux>

[INFO]  Role requested: etcd

[INFO]  Role requested: controlplane

[INFO]  Role requested: worker

[INFO]  Using default agent configuration directory /etc/rancher/agent

[INFO]  Using default agent var directory /var/lib/rancher/agent

[INFO]  Successfully tested Rancher connection

[INFO]  Downloading rancher-system-agent binary from <https://rancher.quving.com/assets/rancher-system-agent-amd64>

[INFO]  Successfully downloaded the rancher-system-agent binary.

[INFO]  Downloading rancher-system-agent-uninstall.sh script from <https://rancher.quving.com/assets/system-agent-uninstall.sh>

[INFO]  Successfully downloaded the rancher-system-agent-uninstall.sh script.

[INFO]  Generating Cattle ID

curl: (28) Operation timed out after 60000 milliseconds with 0 bytes received

[ERROR]  000 received while downloading Rancher connection information. Sleeping for 5 seconds and trying again

[INFO]  Successfully downloaded Rancher connection information

[INFO]  systemd: Creating service file

[INFO]  Creating environment file /etc/systemd/system/rancher-system-agent.env

[INFO]  Enabling rancher-system-agent.service

Created symlink /etc/systemd/system/multi-user.target.wants/rancher-system-agent.service → /etc/systemd/system/rancher-system-agent.service.

[INFO]  Starting/restarting rancher-system-agent.service

In rancher the following error is described at the associated cluster.

Configuring bootstrap node(s) custom-0eb66db1c875: waiting for probes: calico, etcd, kube-apiserver, kube-controller-manager, kube-scheduler

- The cluster is labelled with "Updating" but waiting does not solve this issue. In the meantime I resetted the server completely a few times without any success. Anybody else?

Hi David. Those are helm charts. So you should create your app, containerise it, and then create a helm chart to deploy it. Once you have the chart, you need to create a Rancher custom catalog/app so you can publish your app. https://docs.ranchermanager.rancher.io/v2.0-v2.4/how-to-guides/new-user-guides/helm-charts-in-rancher/adding-catalogs

Hello All , I am using rancher with RKE2 installed with single container node and i need any way to disable the redirect option for Rancher UI from http to https , i have publish external URL for rancher UI using the wildcard certificate with nginx+ and need to reverse the traffic without https ? i can't find any way to disable this redirect option , please any one can help ?

👋 Hi everyone! I'm using rancher for quite awhile now... and having trouble regarding permission management

Hi All 👋 - Is this the spot for Harvester related questions?

Hi, I'm asking again, I'm trying to upgrade a docker rancher install from 2.6.6 to 2.6.8 (or 2.6.7) but I end up with an

ClusterUnavailable 503

error shortly after starting the 2.6.8 container, going back to 2.6.6 fixes this and it works as usual Our downstream cluster is running with RKE1, Kubernetes 1.23.10 and Ubuntu 20.04 Any ideas?

Hi, i am trying to get a rancher 2.6.8 installation active in production because of the EOL of 2.5.. Is there any other working UI available than the "new" UI that we could use? Somehow i feel that the current UI should never touch production, since the last days i lost every trust in the UI. The Problems start from every node in a pool gets deleted on a downgrade to the UI is not reflecting Yaml values from deployments. I wonder how others can use rancher 2.6.x or is rancher not in use anymore?

Question born out of general ignorance: is it feasible to run several rancher instances in the same k3s cluster? I’d like to reuse the same physical infrastructure, but I need more instances due to wildly conflicting end user needs

How to set pod level proxy details in rancher environment. We have already tried throough env variable but still no luck . Please let me know is there any other way to add proxy details.

Hi, How can I set a config for log rotation of Docker engine? I know that we can set it manually and restart docker daemon, but I think its not a good solution, because after adding every node we should set the config manually (and restart docker daemon) Size of log file of my RKE container is about 4GB!!

k3s weekly report! https://github.com/k3s-io/k3s/discussions/6202

Hi, is it possible to regenerate a lost Ranger kubeonfig?

Hi I deleted deployment by mistake from cluster manager instead of deleting the pods which will eventually get restarted. How to get the deployments now , is there any way ?

Hi everyone. I've used rancher a few years ago successfully for a small cluster. I'd like to use it again now for an existing on-prem cluster running on microk8s. There is existing workload on it. Is there a special way to register/import this cluster into rancher? 2 other questions: I'd like to deploy rancher itself in HA on that same cluster. It's still feasible? and I'll use Google SSO for the users. Will it mess up any existing Service Account/Role Binding in the cluster?

Hi... I upgraded rancher from one of the versions upper than 2.6.2 to 2.6.8, sometime after the upgrade the system stopped to work, after i am doing login it stuck with loading, looks like something related to the socket. any idea how to solve the problem?

from the console (including XHR requests) Find All: [management] management.cattle.io.setting console.js:26:30 Some cookies are misusing the recommended “SameSite“ attribute 3 Find All: [rancher] user console.js:26:30 Find All: [rancher] principal console.js:26:30 Reset store: management console.js:26:30 Reset store: cluster console.js:26:30 Reset store: rancher console.js:26:30 Find All: [rancher] authprovider console.js:26:30 Find All: [management] management.cattle.io.setting 2 console.js:26:30 Find: [management] management.cattle.io.setting ui-banners console.js:26:30 XHRPOSThttps://rancher-address.local/v3-public/localProviders/local?action=login [HTTP/1.1 200 OK 248ms] Find All: [rancher] user console.js:26:30 XHRGET https://rancher-address.local/v3/users?me=true [HTTP/1.1 200 OK 63ms] Find All: [management] management.cattle.io.setting console.js:26:30 XHRGET https://rancher-address.local/v1/management.cattle.io.setting [HTTP/1.1 200 OK 165ms] Find All: [rancher] principal console.js:26:30 XHRGET https://rancher-address.local/v3/principals [HTTP/1.1 200 OK 47ms] All of schema is not loaded yet 3 console.js:26:30 All of namespace is not loaded yet console.js:26:30 Loading management... console.js:26:30 All of management.cattle.io.cluster is not loaded yet console.js:26:30 Socket connecting (id=1, url=wss://rancher-address.local/v1/subscribe...) console.js:26:30 Find All: [management] schema console.js:26:30 Find All: [rancher] schema console.js:26:30 XHRGET https://rancher-address.local/v1/schemas [HTTP/1.1 200 OK 424ms] XHRGET https://rancher-address.local/v3/schemas [HTTP/1.1 200 OK 241ms] Socket opened (state=connecting, id=1) console.js:26:30 Find All: [management] management.cattle.io.cluster console.js:26:30 Find All: [management] management.cattle.io.feature console.js:26:30 Find All: [management] userpreference console.js:26:30 Socket connecting (id=2, url=wss://rancher-address.local/v3/subscribe...) console.js:26:30 Find All: [management] count console.js:26:30 Find All: [management] management.cattle.io.setting console.js:26:30 Find All: [management] namespace console.js:26:30 Find All: [management] management.cattle.io.fleetworkspace console.js:26:30 XHRGET https://rancher-address.local/v1/management.cattle.io.cluster [HTTP/1.1 200 OK 236ms] XHRGET https://rancher-address.local/v1/management.cattle.io.features [HTTP/1.1 200 OK 48ms] XHRGET https://rancher-address.local/v1/userpreferences [HTTP/1.1 200 OK 230ms] XHRGET https://rancher-address.local/v1/counts [HTTP/1.1 200 OK 247ms] XHRGET https://rancher-address.local/v1/management.cattle.io.settings [HTTP/1.1 200 OK 386ms] XHRGET https://rancher-address.local/v1/namespaces [HTTP/1.1 200 OK 374ms] XHRGET https://rancher-address.local/v1/management.cattle.io.fleetworkspaces [HTTP/1.1 200 OK 216ms] Socket opened (state=connecting, id=2) console.js:26:30 Done loading management; isRancher=true; isMultiCluster=true

it is like that something like a week, tried to restart the rollout and nothing solve the problem.

any clue?