Even if you’re not using Rancher, the answer is RBAC. Use it.

That is a good point; we do use Rancher. Let me experiment with giving just project level access. Will that also work with Fleet targets?

Hi all. we are doing an upgrade of our kubernetes clusters from 1.24.10 to 1.24.13 We are running rancher 2.6.11 And we are hitting the following error:

[ERROR] Failed to set up SSH tunneling for host [10.0.10.108]: Can't retrieve Docker Info: error during connect: Get "<http://%2Fvar%2Frun%2Fdocker.sock/v1.24/info>": can not build dialer to [c-9wsdt:m-40e5929765ec]
[ERROR] Removing host [10.0.10.108] from node lists

It's not very clear why this is happening. It's also causing all existing pods to go down which is something we didn't expect. Anything to look at?

Hi there, I have issues to run the monitoring of rancher on Flatcar Linux nodes. Here is told: "_When installing monitoring on an RKE cluster using RancherOS or Flatcar Linux nodes, change the etcd node certificate directory to

/opt/rke/etc/kubernetes/ssl_"

Do you know where this certificate directory settings can be checked and changed?

im getting failed to apply the service account: tls handshake timeout, can anyone help

while provisioning the rancher

Hi - I have a k3s master node - that was a single node cluster on a 2.5.9 Rancher server - the cluster is now unavailable - and I’m not sure how to get the node reconnected

We were doing OS upgrades from Ubuntu 18 to 20 - and I believe the node-agent/cluster-agent pods were deleted

The CACERT string changed - and I was able to update it on the other clusters - to get all the system pods running - but with the cluster in this state - I’m not sure how to update that string

chatai gave me some clues - but they still lead to the API server

I can probably delete and recreate a new cluster - but would still lose all the user/storage configs - not the data - just the settings - which I think I can recreate fairly easily

I don’t think deleting the cluster actually deletes the data that the persistent storage objects point to - those are all sitting on an NFS server

I did fix the issue Marcus mentioned with the Cluster Explorer - which was also affecting the Kubectl console in the Rancher GUI - so that was good

essentially the same issue with the secret

Uninstalling K3s deletes the local cluster data, configuration, and all of the scripts and CLI tools. It does not remove any data from external datastores, or created by pods using external Kubernetes storage volumes.

so - I’m guessing deleting the cluster is fairly safe - I’d just have to recreate the users and storage stuff

Greeting everone, can anyone help me? I have a problem with deploy rancher on aws eks. Please help me why I can't deploy rancher

Follow helm install cert-manager 
# refer <https://ranchermanager.docs.rancher.com/getting-started/quick-start-guides/deploy-rancher-manager/helm-cli>
helm repo add rancher-latest <https://releases.rancher.com/server-charts/latest>
kubectl create namespace cattle-system
kubectl apply -f <https://github.com/cert-manager/cert-manager/releases/download/v1.11.0/cert-manager.crds.yaml>
helm repo add jetstack <https://charts.jetstack.io>
helm repo update
helm install cert-manager jetstack/cert-manager \
  --namespace cert-manager \
  --create-namespace \
  --version v1.11.0

deploy rancher
helm install rancher rancher-stable/rancher \
  --namespace cattle-system \
  --set hostname=<http://dograbbit.org|dograbbit.org> \
  --set bootstrapPassword=admin \
  --set ingress.tls.source=letsEncrypt \
  --set letsEncrypt.email=me@example.org \
  --set letsEncrypt.ingress.class=nginx --set global.cattle.psp.enabled=false

k get pod -n cattle-system
NAME                              READY   STATUS      RESTARTS   AGE
helm-operation-bkt8t              0/2     Completed   0          12m
helm-operation-vjk7p              0/2     Completed   0          12m
rancher-7c655cfbf7-7pcg5          1/1     Running     0          14m
rancher-7c655cfbf7-g4fcx          1/1     Running     0          14m
rancher-7c655cfbf7-tb9r7          1/1     Running     0          14m
rancher-webhook-656cd8b9f-5prv8   1/1     Running     0          12m

 k get ing -n cattle-system
NAME      CLASS    HOSTS           ADDRESS   PORTS     AGE
rancher   <none>   <http://dograbbit.org|dograbbit.org>             80, 443   13m
I confuse about . How can I access my <http://dograbbit.org|dograbbit.org> in chrome? It's seem ing doesn't have CLASS.

I want to access the dog <http://rabbit.org|rabbit.org>. Please help me

Hi Team, I have deployed a Rancher server by following this doc -> https://ranchermanager.docs.rancher.com/getting-started/quick-start-guides/deploy-rancher-manager/aws. Now I am trying to create a new RKE cluster in my cloud but I am not able to do it. I getting an error when as shown below. I am giving the right details but still I am getting 403 issue. Can anyone help?

Screenshot 2023-05-08 at 9.45.15 AM.png

Hi all, So I have this single node k3s cluster. k3s uses local-path (https://github.com/rancher/local-path-provisioner) as default SC that allows one to create dynamic volumes using nodes local storage. So we have this statefulset for which the volume part (volumeMounts, volumes and pvc) looks like below.

apiVersion: apps/v1
kind: StatefulSet
metadata:
  labels:
    app: sceptre-themes-manager
  name: sceptre-themes-manager
  namespace: enterprise
spec:
  replicas: 1
  serviceName: "sceptre-themes-manager"
  selector:
    matchLabels:
      app: sceptre-themes-manager
  template:
    spec:
      containers:
        .
        .
        .
        volumeMounts:
        - mountPath: /storage
          name: sceptre-repo-storage
      volumes:
      - name: sceptre-repo-storage
        #persistentVolumeClaim:
          #claimName: data
      imagePullSecrets:
      - name: xxxxxx
  volumeClaimTemplates:
  - apiVersion: v1
    kind: PersistentVolumeClaim
    metadata:
      name: data
    spec:
      accessModes:
      - ReadWriteOnce
      resources:
        requests:
          storage: 20Gi
      volumeMode: Filesystem

Once I create a statefulset, I could see pvc and pv being created and are in bound state

kubectl get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                                      STORAGECLASS   REASON   AGE
pvc-aa65bc02-d0bf-432d-a943-dc1223e03687   20Gi       RWO            Delete           Bound    enterprise/data-sceptre-themes-manager-0   local-path              2d8h
kubectl get pvc -n enterprise
NAME                            STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
data-sceptre-themes-manager-0   Bound    pvc-aa65bc02-d0bf-432d-a943-dc1223e03687   20Gi       RWO            local-path     2d8h

I ssh into the statefulset container and I could see the /storage is mounted.

root@sceptre-themes-manager-0:/usr/src/app# df -h
Filesystem      Size  Used Avail Use% Mounted on
overlay         547G   69G  450G  14% /
tmpfs            64M     0   64M   0% /dev
tmpfs            32G     0   32G   0% /sys/fs/cgroup
/dev/sda4       547G   69G  450G  14% /storage
shm              64M     0   64M   0% /dev/shm
tmpfs            63G   12K   63G   1% /run/secrets/kubernetes.io/serviceaccount
tmpfs            32G     0   32G   0% /proc/acpi

I go to /storage dir and touch a file called test. Then I delete the stateful, I could see the pvc and pv remains intact in bound state. I recreated SFS and ssh into new container and this test file is gone. I could see a proper 777 permission directory is getting created inside /var/lib/rancher/k3s/storage/ for this volume.

root@ent-edge-chennai-metal:/var/lib/rancher/k3s/storage# ls -lat
drwxrwxrwx 2 root root 4096 May  8 04:32 pvc-11089e28-a17b-4aee-8d6e-7429a0b1f752_enterprise_data-sceptre-themes-manager-0

Any idea what might be wrong. Is there something here I am missing?

Hi Team, I provisioned RKE cluster via remote machine using rancher command line. Looking to check the cluster provision log using Rest API or command line. Can you guidance please?

Hi! I am trying to add a Windows worker node to a newly setup RKE2 cluster. I used the "windowsNodeCommand" which downloads and runs the ./install.ps1 script. I have enabled containers and installed containerd in the host, windows server 2022 ltsc. The node is not registering and my current last error log for rancher-wins looks like this:

1690 maj 08 09:38  Error       rancher-wins                    1 error syncing 'fleet-default/custom-59de284649bf-machine-plan': handler secret-watch: secret received was too old, requeuing
    1689 maj 08 09:38  Error       rancher-wins                    1 [K8s] received secret to process that was older than the last secret operated on. (454544841 vs 454545100)
    1649 maj 08 09:37  Information rancher-wins                    1 [Applyinator] Command powershell.exe [-File run.ps1] finished with err: <nil> and exit code: 0
    1647 maj 08 09:37  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stdout]: INFO: Succesfully started rke2
    1643 maj 08 09:37  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stdout]: INFO: Attempting to start rke2
    1642 maj 08 09:37  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stderr]: time="2023-05-08T09:37:44+02:00" level=fatal msg="The specifi...
    1641 maj 08 09:37  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stdout]: INFO: RKE2 agent service not found, enabling agent service       
    1640 maj 08 09:37  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stdout]: [INFO] install complete; you may want to run:  $env:PATH+=";c...
    1639 maj 08 09:37  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stdout]: [INFO] unpacking tarball file to c:/usr/local
    1638 maj 08 09:37  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stdout]: [INFO] verifying tarball
    1637 maj 08 09:37  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stdout]: [INFO] staging local binary tarball from C:\var\lib\rancher\a...
    1636 maj 08 09:37  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stdout]: Using stable channel of rke2 for installation
    1635 maj 08 09:37  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stdout]: [INFO] Windows feature: 'Containers' is installed. Installati...
    1631 maj 08 09:37  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stdout]: WARNING: Waiting for service 'rke2 (rke2)' to stop...
    1630 maj 08 09:37  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stdout]: WARNING: Waiting for service 'rke2 (rke2)' to stop...
    1629 maj 08 09:37  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stdout]: WARNING: Waiting for service 'rke2 (rke2)' to stop...
    1628 maj 08 09:37  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stdout]: WARNING: Waiting for service 'rke2 (rke2)' to stop...
    1623 maj 08 09:36  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stdout]: INFO: RKE2 agent service found, stopping now
    1621 maj 08 09:36  Information rancher-wins                    1 [38073db02ce4b06ae83a2f4510f5dfac2e35984539e2dbc642d2b99db5ec1883_0:stdout]: INFO: Checking if RKE2 agent service exists
    1614 maj 08 09:36  Information rancher-wins                    1 [Applyinator] Running command: powershell.exe [-File run.ps1]

am I missing some major step here? How can I debug this further and can I do some more actions than the inital setup command "windowsNodeCommand"? Great Thanks! for any help on this

Hi Team, I need help with deploying the RKE cluster. I tried to follow this doc https://ranchermanager.docs.rancher.com/getting-started/quick-start-guides/deploy-rancher-manager/aws this helps is deploying the RKE2 is there any similar way to deploy RKE as well? OR is it possible to use the same terraform scripts and deploy RKE with it? If yes please let me know how.

Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.4+k3s1", GitCommit:"8d0255af07e95b841952563253d27b0d10bd72f0", GitTreeState:"clean", BuildDate:"2023-04-20T003318Z", GoVersion:"go1.19.8", Compiler:"gc", Platform:"linux/amd64"} Kustomize Version: v4.5.7 Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.4+k3s1", GitCommit:"8d0255af07e95b841952563253d27b0d10bd72f0", GitTreeState:"clean", BuildDate:"2023-04-20T003318Z", GoVersion:"go1.19.8", Compiler:"gc", Platform:"linux/amd64"} master@master01:~$ ^C master@master01:~$ helm install rancher rancher-stable/rancher --namespace cattle-system --set hostname=172.16.26.7.sslip.io WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/master/.kube/config WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/master/.kube/config Error: INSTALLATION FAILED: chart requires kubeVersion: < 1.26.0-0 which is incompatible with Kubernetes v1.26.4+k3s1

Please if anyone has a proper document of k3s and rancher?

Hi Team, 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/ (edited)

ignore me for the moment, I spotted 2.7.3

Hello everyone, Hope you'll are doing well!

Need some help here I'm using v1.6 and unable to establish connection between the hosts getting the below error using - ubuntu 20.04 Can someone help me with this.. Thanks!