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