Screenshot 2023-05-03 at 8.01.17 PM.png

Hi All, I want to upgrade my rancher from 2.6.7 to latest version 2.7.3 as we are facing an issue with the aks cluster imported as aks is of version 1.25.6. Is AKS 1.25.6 compatible with rancher 2.7.3 as I couldn't see it in compatibility matrix? https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-7-3/

hello, please have a look here, kubelet is down in 2/3 masters and do not know how to trace this https://rancher-users.slack.com/archives/C3ASABBD1/p1682493079592159

Hello everyone, Hi have a issue with prometheus, the init container doesn’t start and i get this error while my node has only 11% used:

add config file /etc/prometheus/config/prometheus.yaml.gz to watcher: no space left on device

Hello! I am attempting to replace docker desktop with Rancher at the moment but I'm having an issue launching containers:

error: exec: "docker-compose": executable file not found in $PATH

I'm sure this is a simple fix but if someone could point me the right direction that would be great. I'm on an intel mac and launching containers via tilt.

Nevermind, my brain finally started working this morning and I realized docker-compose wasn't installed. Now i'm getting this

error getting credentials - err: docker-credential-osxkeychain resolves to executable in current directory (./docker-credential-osxkeychain)

which is a bit more cryptic.

Is there a way to SSH into the nodes from Rancher dashboard?

I have to install the Citrix Zen server dashboard does it mean the k8s cluster is running in a Citrix Zen server environment on top of bare metal on prem hardware?

Screenshot 2023-05-04 at 9.32.50 AM.png

Hi. Apologies firstly as I can't post logs etc. from my actual servers, and can't replicate the issue I'm experiencing in my lab, but any pointers would be appreciated. I'm running rancher 2.6.5 on a management cluster all on Rocky 8. I am having issues suddenly registering new nodes to an existing downstream cluster. There are already 7 identical nodes in the downstream cluster and I'm stumped as to why I can't register this new node. When I drop in the registration command, the script pulls fine from the management cluster, validates certs etc., downloads the rancher-system-agent binary and generates and ID for the new node, which pops up in the UI. But then the scripts stalls and keeps retrying with "[ERROR] 000 received while downloading Rancher connection information. Sleeping for 5 seconds and trying again curl: (28) Operation timed out after 60000 milliseconds with 0 bytes received". This I believe is trying to get the json for the rancher2_connection_info.json file from the /v3/connect/agent endpoint. But I can't find any way to see that endpoint, and if I manually construct a curl string for that endpoint I get a 301 permanently moved redirect. I've tried checking my certs, redeploying rancher and the cluster agent etc. But I'm stumped as to where this endpoint is, or why this is failing. Any hints or tips for where to take my troubleshooting next woul be appreciated.

Hi, I am getting error " tls: private key does not match public key" Create the certificate secret object, from here: https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/resources/update-rancher-certificate#4-reconfigure[…]the-private-ca

What is the best practice for exposing a range of ports? I'd like to containerize a VoIP application and am running into a lot of networking challenges, e.g. SIP behind NAT and the RTP port range.

Is there a reason I get these errors from what seems the ETCD server? I cannot find anything on Google or Github about them. I am using the Docker Single node installation

These logs are from the Rancher Instance

Hi, I'm using rancher with an RKE1 cluster which I've been using for many months. I recently upgraded the cluster to k8s 1.24.13 and started getting the following error when deploying using

kubectl apply -k ...

(using kustomize to deploy several manifests):

error: error validating "kustomization/juicy-staging": error validating data: the server has asked for the client to provide credentials; if you choose to ignore these errors, turn validation off with --validate=false

This seems to be a simple authentication issue, but I can execute any other kubectl command I can think of without issue, and the kustomize deployment even works if I add

--validate=false

. I'll add some more detail in a thread.

after running command, getting error below, does anybody had that issue before? Rnahcer 2.7.0 Single docker Install helm get values rancher -n cattle-system -o yaml > values.yaml Error: release: not found

Activating Rancher with an external identity provider such as Azure AD through the UI is working without issues. However, when attempting to activate through the Rancher API, the identity provider is successfully enabled, but the user groups are not being pulled into Rancher. I am making the API calls using the following endpoint

RANCHER_URL/v3/azureADConfigs/azuread

, and the HTTPS request body is identical to the one sent during activation through the UI.

Guys, if I've created a cluster using Rancher provider in Terraform and I have a question: Can I delete the cluster in Rancher UI without delete cluster in cloud??

Hello everyone 👋🏻 Does anyone know if there is a way to install rke2 and rancher without an internet connection? And if there is, could you please share the documentation/steps with me? Thanks a lot!!!

hi team , I installed latest Rancher without any issue while I run cmd docker images and got error

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

so how to fix this issue?

Hell anyone can help me with this bug ? https://github.com/rancher/rancher/issues/41425

Hi all, I created a Rancher cluster with 3 control planes using RKE. When I run "kubectl cluster-info", I get the following result:

kubectl cluster-info
Kubernetes control plane is running at <https://10.155.10.115:6443>
CoreDNS is running at <https://10.155.10.115:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy>

It seems that my installation is not in HA (high availability). In fact, if I turn off the node 10.155.10.115 and run "kubectl" with a profile that points to the Rancher server, I am unable to query the cluster. I would like to modify this installation by defining a load-balanced hostname instead of an IP address. How can I do this? I imagine there is a parameter to define in the RKE configuration file. If so, which one?

Guys, I came across the setting up the test env document in developer wiki, it seems out of date, can anyone provide a new document?

Activating Rancher with an external identity provider such as Azure AD through the API, it's possible ?

Hi, It is possible to set PV as local when provisioning PVC dynamically via Rancher Local Path ?

Hi, Auto assigned PV hostpath have less IOPS and manually created one have higher IOPS why ?

Hi, where I can find ingress.tls.source=rancher parameter in Rancher? As per guide it should be here "helm get values rancher -n cattle-system" but no rancher pod/deployment in that namespace. Rancher 2.7.0 single node install with docker.

I am posting here in general to get some inputs on how some of you guys deal with this issue... How can we possibly prevent users from accidentally deploying something in

kube-system

or

cattle-system

namespace? Yes by training is one, but accidents can happen. There is a way deploying to default namespace is disallowed; is there similar method for kube-system and cattle-system?

Do not use Admin logins, you can restrict the Users via Roles this is how we do it in Production.

if you’re using Rancher, don’t give your users access to the projects associated with those namespaces?