04/05/2023, 7:53 PM
This appears to be a common problem when initially deploying Rancher on an EKS cluster, but I’m not finding anywhere how to fix the IAM privilege settings to solve this issue. I’m sure there is a need to do something with IAM, but do not see any docs anywhere. Any pointer would be appreciated.
2023/04/05 19:42:54 [FATAL] <|> is forbidden: User "system:serviceaccount:cattle-system:rancher" cannot list resource "clusters" in API group "<|>" at the cluster scope


04/17/2023, 7:30 AM
Facing the same issue. Any luck with this error?
We found out that Rancher helm chart didn't create a ClusterRoleBinding.


04/17/2023, 3:14 PM
yea, I was able to get past this problem, but I do not know what I did to get past it. I just kept tweaking the values.yaml going into the helm chart and it started working. Make sure you setup the TLS stuff perfectly, or things are not going to work as you move up the functionality stack.