Good morning everyone, I got question. I installed rancher onprem Vsphere network. When I create new cluster it gets stuck with waiting for etcd to register. Ultimately i figure out there are two things needs to make it work, add /etc/hosts entries " IP_OF_RANCHER_HOST hostdomain" this registers the cluster to rancher. So my question is why DNS is not resolving with new cluster. ? Do I need any additional automation step to make dns resolve here?

Hi also i have to patch this

kubectl -n cattle-system patch  deployments cattle-cluster-agent --patch '{
    "spec": {
        "template": {
            "spec": {
                "hostAliases": [
                    {
                      "hostnames":
                      [
                        "<http://stage-k8senv1.xxx.se|stage-k8senv1.xxx.se>"
                      ],
                      "ip": "172.20.10.100"
                    },
                    {
                      "hostnames":
                      [
                        "<http://stage-k8senv1.xxx.se|stage-k8senv1.xxx.se>"
                      ],
                      "ip": "172.20.10.101"
                    }

                ]
            }
        }
    }
}'

Which allows cluster agent to connect. Any permanent solution? when we create downstreame cluster in rancher it should work out of the box?

Hi guys, I bought new certificate from godaddy for my rancher domain. Current self sign certificate says "Not Secure" Always, Now When I update tl-ingress by editing secrete it updates again to default. Do you know how to use Cert Manager or option to import new Godaddy SSL in Rancher UI ? IS this area i need to explore? Thank you.

Earlier I try to edit private key and ceritficate here and i notice it automatically becomes default.

I also find this area where secrete name under certificates, should i create new secrete with new pem and cert and then apply here ?

Create a new certificate secret, then edit the rancher ingress to use that new secret, be sure the secret is in the same namespace as the original

I did updated with new secrete, ingress but seems like its still shows insecure and old cert in browser do we need to redeploy ?

Hi Folks!! I get the following error upon doing a

docker-compose up

. Does anyone have any clue about what am i missing? This works fine on another machine with docker desktop

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/etc/localtime" to rootfs at "/etc/localtime": mount /etc/localtime:/etc/localtime (via /proc/self/fd/6), flags: 0x5001: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

Any one use cifs mounting in there kubernetes cluster ?

Warning  FailedMount  7s (x7 over 41s)  kubelet            MountVolume.SetUp failed for volume "config" : mount command failed, status: Failure, reason: cifs mount: failed to mount the network path: mount error(79): Can not access a needed shared library

Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) root@devops-development-f1fc2e79-jsng7:~# Warning FailedMount 7s (x7 over 41s) kubelet MountVolume.SetUp failed for volume "config" : mount command failed, status: Failure, reason: cifs mount: failed to mount the network path: mount error(79): Can not access a needed shared library -bash: syntax error near unexpected token `('

👋 Hi everyone!

hello

I have deployment kind in my rancher, when i sh to the ubuntu pod, and try to run apt update it doesnt resolve internet. my yaml i am missing anything? https://codeshare.io/OdqmA0

do we need to add any sidecar container to manage internet?

I have installed k3s in a bare metal server without Traefik and installed Nginx ingress from: (sudo kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.4.0/deploy/static/provider/cloud/deploy.yaml) If I try one simple ingress configuration in my laptop with Docker desktop I have connectivity. However, the same deployment is not working in k3s. Could somebody give me a hand? I have posted the full case here: https://stackoverflow.com/questions/74411249/k3s-lan-test-with-nginx-ingress

Hi, when i create deployment/pod /etc/resolv.conf has wrong nameserver, i want core-dns cluster ip as nameserver but it has something else 172.x.x.x , how do i make default as core-dns ip. ?

the file doesnt exists here in rancher downstream k8s cluster "/var/lib/kubelet/config.yaml" file?, i am trying to set nameserver there.

hello all, While initialing the Rancher desktop I unable to start the k3s Image Attached does anyone know how to resolve it.

2022-11-13T15:55:26.215Z: Registered distributions: rancher-desktop,rancher-desktop-data
2022-11-13T15:55:26.216Z: data distro already registered
2022-11-13T15:55:45.778Z: Installing C:\Users\INPRASHANDHI\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\internal\trivy as /mnt/c/Users/INPRASHANDHI/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/internal/trivy into /usr/local/bin/trivy ...
2022-11-13T15:56:00.214Z: Installing C:\Users\INPRASHANDHI\AppData\Local\Programs\Rancher Desktop\resources\resources\linux\internal\rancher-desktop-guestagent as /mnt/c/Users/INPRASHANDHI/AppData/Local/Programs/Rancher Desktop/resources/resources/linux/internal/rancher-desktop-guestagent into /usr/local/bin//rancher-desktop-guestagent ...
2022-11-13T15:57:14.221Z: Waited more than 60 secs for nerdctl images to succeed. Giving up.
2022-11-13T15:57:14.960Z: WSL: executing: /usr/local/bin/wsl-service k3s start: Error: wsl.exe exited with code 1
2022-11-13T15:55:32.804Z: /sbin/init exited with status 1 signal null
2022-11-13T15:55:33.557Z: Registered distributions: 
2022-11-13T15:55:34.264Z: Registered distributions: rancher-desktop

Hi All, So issue i am having here if someone encountered or know whats wrong. So basically I setup rancher on vspehere cluster, now when i create downstream cluster. I am trying to install jenkins using helm chart. I notice I can add helm from terminal level but inside rancher UI it fails. Closely i notice that inside rancher ui, it is requesting using upstreame kube-dns ip, I also see core-dns running on downstream cluster. there is way to update routing for helm chart to go core-dns in same cluster so it get can make requests? Also when you setup downstreame cluster , Its required to define cluster cidr and service cidr in downstreame ? when we setup downstreame why that cluster has default /etc/resolve to uptreame kube-dns. instead of its own dns (core-dns?

I am getting a 'waiting for API to be available' while importing eks cluster into rancher running in my local kind cluster. These are the rancher logs

2022/11/14 06:21:02 [INFO] Stopping cluster agent for c-fdzz5
2022/11/14 06:21:02 [ERROR] failed to start cluster controllers c-fdzz5: context canceled

Any idea why this is happening ?

Hey team, I installed rancher desktop But i am facing the issue in running the kubectl commands, I am getting this error:

2580 versioner.go:56] Remote kubernetes server unreachable
Unable to connect to the server: dial tcp 147.154.135.50:6443: i/o timeout

as i have put the following command in my .zshrc file to run docker without which docker commands were also not getting recognised:

export PATH="$HOME/.rd/bin:$PATH"

Hi, I am trying out local-path storage and while it works, I wonder if there is a way to define multiple mappable paths per PersistentVolumeClaim instead of having to define one PersistentVolumeClaim for each mappable path.

Rancher 2.6.9 is installing Docker 20.10.17 from 2022-06-06. The current version is 20.10.21 from 2022-10-25, so there's almost 5 months worth of bugfixes and security updates missing, including fixes for 3 CVEs with a score of 7.5 (High) in 20.10.19. Rancher 2.6.9 is from 2022-10-18 and at least Docker 20.10.18 had been out for more than a month back then. So I figured this must be something independent of the specific Rancher version. I found out Rancher retrieves a file from an URL under releases.rancher.com and that version 20.10.17 is hardcoded in there:

$ curl -s <https://releases.rancher.com/install-docker/20.10.sh> | grep ^VERSION
VERSION="20.10.17"

Should this be updated?

Hello, how to check rancher dashboard acme certificate status and logs?

Hi. I've posted before about some auditing items with Rancher, but this question is a little different (more generic kubernetes related). I'm having a hard time figuring out what user creates a deployment. I have auditing configured correctly on my RKE2 instance, it logs to the file specified, so this is good to go. I'm using the attached 'generic' audit-policy.yaml file (the one described on the main kubernetes site). I'm using kubectl to connect to the cluster, and ran: kubectl create deployment blarg777 --image=rancher/hello-world I searched the auditlog for the blarg777 entries, and see the container pulling/starting and all that, but I'm not seeing anything where I can identify WHO did that. Is that something I have misconfigured in the audit policy, or does kubernetes not know how to show that info in a useable way? Thanks for the help, and sorry for the long post.

Hi, any advice on managing rancher projects? Anybody using an operator to create and manage projects?

We use Terraform