Open seanogor opened 3 years ago
Confirmed that this issue occurs when substituting podman in as the container cli, so it is most likely permission based
Hi @seanogor, thanks for reporting the issue. May I know what node scenario is being run and the kubernetes version? Asking to make sure it doesn't require talking to the ROKS cloud as it's not supported as of now, it's needed for things like node shutdown/terminate etc. but not for kubelet/node crash since they just involve talking to the kube API irrespective of the cloud.
From the logs, looks like it's an issue with Kubernetes auth like you mentioned, can we try the following to see if it fixes it?
$ kubectl create clusterrolebinding serviceaccounts-cluster-admin \ --clusterrole=cluster-admin \ --group=system:serviceaccounts
Kraken find node is not authorized after logging into the cluster on ROKS: