Nova gets wrong service account about nova HOT 3 CLOSED

Can you share more details of how you are logging in via service account, and which service account you are trying to use in your command? I am not familiar with kubelogin, and we do not login with service accounts.

from nova.

We tried to login without kubelogin also, just getting admin credentials using the following command:
az aks get-credentials --resource-group <rg_name> --name <cluster_name> --file <k8s_config_path> --admin

This is executed inside gitlab runner. And unfortunately getting the same error:
F0707 15:48:55.093188 134 root.go:272] error getting helm releases: could not detect helm 3 charts: list: failed to list: secrets is forbidden: User "system:serviceaccount:gitlab:default" cannot list resource "secrets" in API group "" at the cluster scope: Azure does not have opinion for this user.

Also tried to specify the name of the k8s context in nova’s config file. Got the exact same error.

from nova.

ok, looks like this is something between Docker file config and nova. If I set something like this:

USER user
WORKDIR /home/user
CMD ["nova"]

this isn't work, I have previously mentioned error, but if I explicitly set KUBECONFIG with full path, like
KUBECONFIG=/home/user/.kube/config
it works as expected

from nova.