Hello, I had followed the OKTA integration step using the DOC in my rancher setup, but the enable is failing with 403 error and reroute to rancher default login page i tried with okta credentials but it is not passing anyone can help me with that ?.

Has anybody had success in trying the new Rancher setup AMI image? I’ve tried it a couple times and have run into problems. I get the system spun up, and logged in. But every step in the wizard gives an error. I can’t seem to find if there are minimum VM requirements or network setup.

This is what I get when I click anything in the Wizard:

Hi, i try to install a downstream RKE2 cluster on my rancher 2.6.7 cluster. But everytime i got the message about non ready bootstrap machine. I got this working one time. Now try it again for 2 days. But no succes. Running rhel8 with firewalld disabled

Hi Everyone! Not sure if this would be the best place to ask these questions but I'm having an issue with Rancher and the UI. After some exploring it looks like I might be missing the install of Rancher or something close to that. I can't find the Rancher pods running anywhere on my cluster. I have a number of apps running in different namespaces and can't resolve any of them. I guess there was an activity that messed up the underlying IP addresses on the VMs running. This all got fixed and re-configured but now for some reason I'm missing the Rancher UI and the apps running in separate namespaces can't be accessed. I keep receiving a 504 bad gateway error. I can get more details tomorrow if someone is in the America time zone? Really strange issue...

Is the IP or name different you use to get to it?

rancher doesn’t like it when you change names/ips

Hi Everyone, I am trying to make a checklist for setting up a rancher RKE2 downstream cluster with a mix of windows and linux nodes, do we have any articles floating around for such a setup

Hi everyone, has anyone here tested node autoscaler on Rancher ( backend nodes are on VMware Esxi and Azure) as far as document goes it says that it supports EC2 autoscaling on Amazon, would like to know if anyone has been able to get it working on Vmware and Azure

Hi everyone, I want to create a new RKE2 cluster through the cli interface. How can a receive the registration commands through the CLI without logging into the Web UI?.

If I deploy an nginx controller in my downstream cluster, how can I ensure it gets an external IP address since rancher nodes don't have a LB?

ingress-nginx   service/ingress-nginx-controller             LoadBalancer   10.43.221.102   <pending>     80:31241/TCP,443:31873/TCP   58m

For rke2 and rancher v2.7, for production it is recommended between these alternatives: openSUSE Leap 15.4 CentOS 7.9 Rocky Linux 8.6 ubuntu 22.04 on aws ec2

or like a survey, which one do you use?

Hello, Can I set up the Rancher Server frontend in a webserver and the backend API server in a k3s cluster? so that I can have my web frontend scaled separately rather than scaling the number of k3s servers.

Hi, anyone finds any mistake? It is not working.

apiVersion: <http://argoproj.io/v1alpha1|argoproj.io/v1alpha1>
kind: Application
metadata: 
  name: rancher
  namespace: argocd

  finalizers:
    - <http://resources-finalizer.argocd.argoproj.io|resources-finalizer.argocd.argoproj.io>
spec:
  project: default
  source:
    repoURL: '<https://releases.rancher.com/server-charts/stable>'
    targetRevision: 2.7.0
    helm:
      parameters:
        - name: hostname
          value: "<http://rancher.example.com|rancher.example.com>"
        - name: ingress.tls.source
          value: "letsEncrypt"
        - name: letsEncrypt.email
          value: "<mailto:example@gmail.com|example@gmail.com>"
        - name: letsEncrypt.ingress.class
          value: "traefik"
        - name: replicas
          value: "3"
         
    chart: rancher
  destination:
    server: '<https://kubernetes.default.svc>'
    namespace: cattle-system
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
      - CreateNamespace=true

@mysterious-wire-57288 has left the channel

Hi, Is it possible to create virtual cluster in Rancher like Loft does? Thank you.

@https://rancher-users.slack.com/archives/C01GKHKAG0K/p1674589425265959

@brave-breakfast-33682 has left the channel

Hello all, I am in the process of installing Rancher and Rancher Desktop to learn some k8s concepts. I am following the instructions here: https://docs.rancherdesktop.io/how-to-guides/rancher-on-rancher-desktop and I am getting a 404 error message when I go to the IP address and nothing when I go to https://rancher.rd.localhost/ A couple of the pods in cattle-system had some restarts early on but haven't restarted for a while.

I also have another question. If I build an image with the Rancher-Desktop ui, it doesn't show up when executing "docker ps" and when I build using the cli, it doesn't show up under the Rancher-Desktop list of images, you also can't use cli built images in kubectl deployments. Is there a flag or a way to import those into Rancher-Desktop?

Hi I have successfully configured rke ha setup with 3 nodes. Realized that kubectl config points to node 3. I'm testing my ha setup. I powered down nodes 2 and 3, realized June config is still pointing to 3rd node

Any idea how to overcome this and point to node 1 which is still alive?

Hi, Is it possible to install RKE2 cluster with Kube-vip from within rancher instead installing RKE2 with kube-vip prior rancher is installed on the nodes? If so, would you happen to have a video and steps? Thank you.

I'm trying to install Rancher Desktop Version: 1.7.0 in windows 11 this has WSL-2 enabled and running without problems. When I install Rancher Desktop in windows the app does start but reports a networking issue:

The application cannot reach the general internet for updated kubernetes versions and other components, but can still operate.

Error: ENOENT: no such file or directory, open '\\wsl$\rancher-desktop-data\etc\hosts'

The images tab reports:

Waiting for image manager to be ready

wsl version shows:

WSL version: 1.1.3.0

Kernel version: 5.15.90.1

WSLg version: 1.0.49

MSRDC version: 1.2.3770

Direct3D version: 1.608.2-61064218

DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp

Windows version: 10.0.22623.1325

I would appreciate any pointers on how best to debug this issue

Hi, the

cattle-system

namespace has been stuck in

terminating

for days. How can I get rid of it at once? Thanks in advance.

Rancher v2.7.0 with downstream RKE2 cluster. Not able to import an orphaned cluster into a new instance of Rancher. Import Existing -> Import any Kubernetes cluster. After issuing the import command on the cluster several pods go into CrashLoop and do not recover:

/var/lib/rancher/rke2/bin/kubectl         --kubeconfig /etc/rancher/rke2/rke2.yaml apply -f <https://rancher75182.senode.dev/v3/import/xhctfcnbbt56xvxh6jptq7lzvpw9svd2drkbj5pvm466t5r7zlplqv_c-m-zqcvzlgn.yaml>
<http://clusterrole.rbac.authorization.k8s.io/proxy-clusterrole-kubeapiserver|clusterrole.rbac.authorization.k8s.io/proxy-clusterrole-kubeapiserver> unchanged
<http://clusterrolebinding.rbac.authorization.k8s.io/proxy-role-binding-kubernetes-master|clusterrolebinding.rbac.authorization.k8s.io/proxy-role-binding-kubernetes-master> unchanged
namespace/cattle-system unchanged
serviceaccount/cattle unchanged
<http://clusterrolebinding.rbac.authorization.k8s.io/cattle-admin-binding|clusterrolebinding.rbac.authorization.k8s.io/cattle-admin-binding> unchanged
secret/cattle-credentials-ad9a794 created
<http://clusterrole.rbac.authorization.k8s.io/cattle-admin|clusterrole.rbac.authorization.k8s.io/cattle-admin> unchanged
Warning: spec.template.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].key: <http://beta.kubernetes.io/os|beta.kubernetes.io/os> is deprecated since v1.14; use "<http://kubernetes.io/os|kubernetes.io/os>" instead
deployment.apps/cattle-cluster-agent configured
service/cattle-cluster-agent unchanged

NAMESPACE             NAME                                                    READY   STATUS             RESTARTS      AGE
calico-system         calico-kube-controllers-f75c97ff6-fvb66                 1/1     Running            0             19m
calico-system         calico-node-6vxmh                                       1/1     Running            0             19m
calico-system         calico-node-d9t8n                                       0/1     Running            0             17m
calico-system         calico-node-khhpr                                       1/1     Running            0             19m
calico-system         calico-node-nmcds                                       0/1     Running            0             17m
calico-system         calico-typha-d65458ffc-97pn9                            1/1     Running            0             17m
calico-system         calico-typha-d65458ffc-p9cj2                            1/1     Running            0             19m
cattle-fleet-system   fleet-agent-6c857b85b5-zff2l                            1/1     Running            0             17m
cattle-system         cattle-cluster-agent-6f588568-dj7ql                     0/1     CrashLoopBackOff   4 (49s ago)   4m9s
cattle-system         cattle-cluster-agent-6f588568-zl55k                     0/1     CrashLoopBackOff   4 (29s ago)   3m53s
kube-system           cloud-controller-manager-sempre1-ctrl                   1/1     Running            0             20m
kube-system           cloud-controller-manager-sempre1-etcd                   1/1     Running            0             20m
kube-system           etcd-sempre1-etcd                                       1/1     Running            0             19m
kube-system           helm-install-rke2-calico-7dxlb                          0/1     Completed          2             20m
kube-system           helm-install-rke2-calico-crd-wzffm                      0/1     Completed          0             20m
kube-system           helm-install-rke2-coredns-zs9rl                         0/1     Completed          0             20m
kube-system           helm-install-rke2-ingress-nginx-gtkv8                   0/1     CrashLoopBackOff   6 (40s ago)   20m
kube-system           helm-install-rke2-metrics-server-blcf4                  0/1     CrashLoopBackOff   6 (51s ago)   20m
kube-system           kube-apiserver-sempre1-ctrl                             1/1     Running            0             20m
kube-system           kube-controller-manager-sempre1-ctrl                    1/1     Running            0             20m
kube-system           kube-proxy-sempre1-ctrl                                 1/1     Running            0             20m
kube-system           kube-proxy-sempre1-etcd                                 1/1     Running            0             20m
kube-system           kube-proxy-sempre1-wrk1                                 1/1     Running            0             17m
kube-system           kube-proxy-sempre1-wrk2                                 1/1     Running            0             17m
kube-system           kube-scheduler-sempre1-ctrl                             1/1     Running            0             20m
kube-system           rke2-coredns-rke2-coredns-58fd75f64b-kfb69              1/1     Running            0             19m
kube-system           rke2-coredns-rke2-coredns-58fd75f64b-rzpsg              1/1     Running            0             20m
kube-system           rke2-coredns-rke2-coredns-autoscaler-768bfc5985-hcf4b   1/1     Running            0             20m
tigera-operator       tigera-operator-586758ccf7-rc9tq                        1/1     Running            0             19m

Looking the logs seems cluster agent is unable to ping the rancher server, but if I do a curl on the same URL it responds with a pong.
ERROR: <https://rancher75182.senode.dev/ping> is not accessible (Could not resolve host: rancher75182.senode.dev)

helm pods report error as well:
/var/lib/rancher/rke2/bin/kubectl --kubeconfig /etc/rancher/rke2/rke2.yaml logs helm-install-rke2-ingress-nginx-gtkv8 -n cattle-system
Error from server (NotFound): pods "helm-install-rke2-ingress-nginx-gtkv8" not found
/var/lib/rancher/rke2/bin/kubectl --kubeconfig /etc/rancher/rke2/rke2.yaml logs helm-install-rke2-metrics-server-blcf4 -n cattle-system
Error from server (NotFound): pods "helm-install-rke2-metrics-server-blcf4" not found

Hello I’m doing the new Rancher academy course. So far so good, but I’m locked on an ssl part and the videos seem to be missing out on the ssl part. They are showing to add cert manager and install cert manager in namespace then install rancher with a temp fqdn pointing to something.127.0.0.1.sslip.io And then it just jumps further, no guidelines on how to handle the SSL cert for that url. In the browser it works by accepting the insecure connection, but a few lessons further it’s talking about using rancher CLI and this is locking up and --skip-verify is not working. command: rancher login https://something.127.0.0.1.sslip.io --token token-xxxxxx --skip-verify output: FATA[0000] Get "https://something.127.0.0.1.sslip.io/v3": x509: "something.127.0.0.1.sslip.io" certificate is not trusted So what next?

Hi everyone, I'm raising again the question. We have deployed the Rancher monitoring on our clusters. We have set a dedicated ingress for Grafana and configure azureAD authentication. We have disabled the anonymous logging and so Rancher integration is obviously no more working. I'm trying to find a way to keep the Rancher integration as it is really convenient. Did someone run into the same and is able to help? Many thanks in advance.