I tried running: • /usr/local/bin/rke2-uninstall.sh • /usr/local/bin/rancher-system-agent-uninstall.sh But I can still see remaining data

and rancher still shows the node in the cluster machines list

@big-jordan-45387 Did you stop the service?

no

I am now

Hi! I added a private GKE (worker nodes without external IP, control plane with external IP, but authorized networks enabled) which I added to Rancher. However, I can't deploy any apps from within Rancher - the appstore is empty. When I add a public GKE to Rancher, I see the complete app store. So I suppose, I have to change particular rights / RBACs somewhere. Any idea which one?

I encounter the below error while using the install script. The default script uses https to get repomd.xml. If I manually use http, it works. Any workarounds ? Rgds.

01:12:01 root@T7910-k3sm1 ~ → curl -sfL <http://get.k3s.io> | INSTALL_K3S_VERSION=v1.24.10+k3s1 sh -
[INFO]  Using v1.24.10+k3s1 as release
[INFO]  Downloading hash <https://github.com/k3s-io/k3s/releases/download/v1.24.10+k3s1/sha256sum-amd64.txt>
[INFO]  Skipping binary downloaded, installed k3s matches hash
Rancher K3s Common (stable)                                                                               0.0  B/s |   0  B     00:00
Errors during downloading metadata for repository 'rancher-k3s-common-stable':
  - Curl error (35): SSL connect error for <https://rpm.rancher.io/k3s/stable/common/centos/8/noarch/repodata/repomd.xml> [OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to <http://rpm.rancher.io:443|rpm.rancher.io:443> ]
Error: Failed to download metadata for repo 'rancher-k3s-common-stable': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

hi everyone, my first day join this channel start with a quick question: i have rke2 installed and next step is to deploy rancher server. as i found the images list in github releases page is long, is that a minimum pre-req images list if i only want to deploy server itself without any addons?

Hi there 👋 I was able to join an AWS node with a GCP node using K3s and Kilo and this made my day. Honestly. I never before worked so deep down the network layer (configuring WireGuard to establish a VPN) and I’m pretty proud of myself 😁 The current state is committed to the repository. Only the Azure node is making trouble. I read that

--node-external-ip

must be provided as argument to the primary K3s node, which I did (steps are documented here). Still the setup of K3s fails with this error:

[root@az-japaneast-node azureuser]$ curl -sfL <https://get.k3s.io> | K3S_URL=<https://10.0.0.1:6443> K3S_TOKEN=$K3S_TOKEN sh -
[INFO]  Finding release for channel stable
[INFO]  Using v1.25.6+k3s1 as release
[INFO]  Downloading hash <https://github.com/k3s-io/k3s/releases/download/v1.25.6+k3s1/sha256sum-amd64.txt>
[INFO]  Downloading binary <https://github.com/k3s-io/k3s/releases/download/v1.25.6+k3s1/k3s>
[INFO]  Verifying binary download
[INFO]  Installing k3s to /usr/local/bin/k3s
[INFO]  Skipping installation of SELinux RPM
[INFO]  Creating /usr/local/bin/kubectl symlink to k3s
[INFO]  Creating /usr/local/bin/crictl symlink to k3s
[INFO]  Creating /usr/local/bin/ctr symlink to k3s
[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[INFO]  Creating uninstall script /usr/local/bin/k3s-agent-uninstall.sh
[INFO]  env: Creating environment file /etc/systemd/system/k3s-agent.service.env
[INFO]  systemd: Creating service file /etc/systemd/system/k3s-agent.service
[INFO]  systemd: Enabling k3s-agent unit
Created symlink /etc/systemd/system/multi-user.target.wants/k3s-agent.service → /etc/systemd/system/k3s-agent.service.
[INFO]  systemd: Starting k3s-agent
Job for k3s-agent.service failed because the control process exited with error code.
See "systemctl status k3s-agent.service" and "journalctl -xe" for details.

The systemd status is as follows:

[root@az-japaneast-node azureuser]$ systemctl status k3s-agent.service
● k3s-agent.service - Lightweight Kubernetes
     Loaded: loaded (/etc/systemd/system/k3s-agent.service; enabled; vendor preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Fri 2023-02-03 19:08:40 UTC; 845ms ago
       Docs: <https://k3s.io>
    Process: 21049 ExecStartPre=/bin/sh -xc ! /usr/bin/systemctl is-enabled --quiet nm-cloud-setup.service (code=exited, status=0/SUCCESS)
    Process: 21051 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
    Process: 21052 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
    Process: 21053 ExecStart=/usr/local/bin/k3s agent (code=exited, status=1/FAILURE)
   Main PID: 21053 (code=exited, status=1/FAILURE)
        CPU: 101ms

Feb 03 19:08:40 az-japaneast-node systemd[1]: k3s-agent.service: Main process exited, code=exited, status=1/FAILURE
Feb 03 19:08:40 az-japaneast-node systemd[1]: k3s-agent.service: Failed with result 'exit-code'.
Feb 03 19:08:40 az-japaneast-node systemd[1]: Failed to start Lightweight Kubernetes.

Does anyone maybe have an idea how to resolve that?

Hi Techies, I am struggling with getting

helm plugin

installed in my cluster managed via rancher, to be precise I would like to install helm spray plugin: https://github.com/ThalesGroup/helm-spray and use it like helm spray to deploy umbrella chart .. So far, I didn't find any clue on how we can install helm plugins within a rancher cluster keeping GitOps CD pipeline intact so I can deploy via gitlab

Out of curiosity, anyone out there crazy enough to still be running rancher server 1.6 in production? We’ve still got an old rancher 1 setup running alongside our rancher2 just waiting for it to die and move everything over but it still hasnt given up the ghost and does everything we need it to do. Its kinda wild how after 8 + years of running it, despite being completely unsupported, it still gives our engineers less trouble and loss of sleep compared to our “modern” Rancher2 rke production environment 😆. It got me wondering if there are any community forks of 1.6 floating around or some sort of community around it?🤔

Hi, I want to fork the Rancher origin repo & push the helm chart to my private registry. The problems is

rancher/chart/Chart.yaml

contain some dummy text need to replace with the right version (Ex:

appVersion: %APP_VERSION%

). My question is: 1. How can i replace that value? I find the file

scripts/chart/build

but don't see any document explain what parameter need passing to it. Thank for you support.

How can I extend the scheduler and add the plugin for GPU sharing to RKE Kubernetes like v1.20.15-rancher1-4 ?

Hi, anybody can please support me in regards to my query here

Hello everyone ! I am trying to install Loki Grafana in my cluster ! I am finding some issue with new version of grafana image v9.y.z The logs am getting with my instance :

level=error msg="Failed to look up user based on cookie" error="user token not found"

Hitting my dashboard got this : Notice: However downgrading to v7.y.z resolve the problem Could this be related to my problem https://grafana.com/tutorials/run-grafana-behind-a-proxy/

Hi all i'm totally new with kubernetes and reancherm i have some issue for install rancher on a kubernete cluster, can i ask here for an help? Or there is another more indicate channel?

I think problem is more related to traefik but my "noobines" is big 😄 Long story short, kubernetes cluster with 7 nodes (2 master) , think i have deployed rancher succesfuly

kube-master-01:~/rancher$ kubectl -n cattle-system get pods
NAME                       READY   STATUS    RESTARTS      AGE
rancher-658645db48-2ljtg   1/1     Running   0             36m
rancher-658645db48-7bmql   1/1     Running   0             36m
rancher-658645db48-xmmxm   1/1     Running   1 (36m ago)   36m

I saw anyway some errors

Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Pulled     37m (x2 over 37m)  kubelet            Container image "rancher/rancher:v2.7.1" already present on machine
  Normal   Created    37m (x2 over 37m)  kubelet            Created container rancher
  Normal   Started    37m (x2 over 37m)  kubelet            Started container rancher
  Normal   Scheduled  37m                default-scheduler  Successfully assigned cattle-system/rancher-658645db48-xmmxm to kube-worker-01
  Warning  Unhealthy  36m (x2 over 37m)  kubelet            Readiness probe failed: Get "<http://192.168.188.132:80/healthz>": dial tcp 192.168.188.132:80: connect: connection refused

And on my traefik i see the entrypoint and services

kube-master-01:~/rancher$ kubectl get services -n cattle-system
NAME      TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)          AGE
rancher   ClusterIP   10.99.96.200   <none>        80/TCP,443/TCP   40m

Hi everyone, We are on 2.7.1 version and the UI is extremely slow, we have imported eks cluster using generic import, the cluster runs 459 nodes. Can you suggest some tuning, we can do to improve UI performance?

Hi Team - New to this channel and great to be here. I am getting issues installing racher-desktop. It fails non stop - Tried everything (restarts, uninstallations of rancher, etc). Can you help me? Rancher Desktop 1.7.0 - win32 (x64) Error Starting Kubernetes

Error: connect ECONNREFUSED 172.27.100.13:6443

2023-02-06T095525.224Z: Registered distributions: Ubuntu,rancher-desktop,rancher-desktop-data 2023-02-06T095531.416Z: Registered distributions: Ubuntu,rancher-desktop,rancher-desktop-data 2023-02-06T095538.026Z: Registered distributions: Ubuntu,rancher-desktop,rancher-desktop-data 2023-02-06T095543.904Z: Registered distributions: Ubuntu,rancher-desktop,rancher-desktop-data 2023-02-06T095543.904Z: data distro already registered 2023-02-06T095637.958Z: Did not find a valid mount, mounting /mnt/wsl/rancher-desktop/run/data 2023-02-06T095722.403Z: Installing C:\Users\stefan.depagter\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\internal\trivy as /mnt/c/Users/stefan.depagter/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/internal/trivy into /usr/local/bin/trivy ... 2023-02-06T100008.191Z: Installing C:\Users\stefan.depagter\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\internal\rancher-desktop-guestagent as /mnt/c/Users/stefan.depagter/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/internal/rancher-desktop-guestagent into /usr/local/bin//rancher-desktop-guestagent ...

Hello Rancher team! I use 1.25.6 kubernetes version, and when I run 'docker login some.url' I get this message - request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) If I try to use 1.26.1 version I get this error Can someone help me with it? 😟

Hello all, I accidently ran a terrifying command on my Rancher cluster, this is it:

k scale deploy rancher -n cattle-system --replicas=0

Now the Rancher itself is unreachable neither from the web UI nor from the kubectl, how do I fix the problem, can anyone help?

Defining Ingress for k3s traefik I am running k3s version 1.25.5 and I would like to define traefik as an ingress for one of the services defined through an external helm chart. I am struggling to find the right ingress definition. I tried with the below yaml file but that gives an error stating

error: resource mapping not found for name: "c8-ingress" namespace: "" from "zeebe-traefik.yaml": no matches for kind "Ingress" in version "extensions/v1beta1"
ensure CRDs are installed first

This seems to be because of the an old

apiVersion

used in the yaml file. How to do it the right way? Thanks.

hi guys, could someone help with rancher cluster? i am facing issues after updating certs to the custom one

Get "<https://10.43.116.54/k8s/clusters/c-m-gz28sbhl/version?timeout=15s>": net/http: request canceled (Client.Timeout exceeded while awaiting headers)

force update is not working and cluster agents are full with these logs

time="2023-02-06T14:52:08Z" level=error msg="Failed to connect to proxy. Response status: 400 - 400 Bad Request. Response body: cluster not found" error="websocket: bad handshake"
time="2023-02-06T14:52:08Z" level=error msg="Remotedialer proxy error" error="websocket: bad handshake"

In an autoscaling cluster, sometimes nodes time out during registration. This results in it being stuck in it being there forever, even if the instance is removed by the ASG in AWS. Is there any way for rancher to be able to set some check to clean this up after a certain time. I've seen up to hundreds of nodes at times that never go away and have no instances backing them. Since they don't register, they aren't listed in kubectl, so it has to be done internally in rancher somehow.

Hi y'all I am having a very hard time debugging an issue with rke-cli. I am trying to add more nodes, I am following the exact same steps as I did the first time I added them, and many times after. Except something is wrong now cuz when I run the command: rke up --update-only it does not add the new nodes it actually complains that "Node not found" on the new nodes i have attempted to add There are no other error logs The cluster is functioning okay, afaik since everything else is running ( this is also in production ) I have managed to see the node for like 1-2 seconds on the node list and then it went away. The new node's kubelet complains that the node is not found as well when attempting to run kubelet the k8s version is 1.24.4

Hi everyone, is there anyway to deploy rancher with public ip address as the hostname, not with FQDN

because, with FQDN, the agent not able to resolve to an IP using /etc/host (Custom DNS) configuration

so anyone can suggest how to use ip address instead of dns name

?