You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we tested upgrading our Argo managed install of Karpenter from 0.37.0 to 0.37.4, it produced errors in the controller about missing role permissions for the service account.
example error: k8s.io/[email protected]/tools/cache/reflector.go:232: Failed to watch *v1.ConfigMap: failed to list *v1. │ │ ConfigMap: configmaps is forbidden: User \"system:serviceaccount:kube-system:karpenter\" cannot list resource \"configmaps\" in API group \"\" in the namespace \"kube-system\".
Webhooks are disabled in the chart configuration.
Not sure if it's related, but when I tried to manage Karpenter chart install with Kustomize, it produced another set of errors with missing role and rolebindings for the kube-node-lease namespace.
The text was updated successfully, but these errors were encountered:
Description
When we tested upgrading our Argo managed install of Karpenter from 0.37.0 to 0.37.4, it produced errors in the controller about missing role permissions for the service account.
example error:
k8s.io/[email protected]/tools/cache/reflector.go:232: Failed to watch *v1.ConfigMap: failed to list *v1. │ │ ConfigMap: configmaps is forbidden: User \"system:serviceaccount:kube-system:karpenter\" cannot list resource \"configmaps\" in API group \"\" in the namespace \"kube-system\"
.Webhooks are disabled in the chart configuration.
Not sure if it's related, but when I tried to manage Karpenter chart install with Kustomize, it produced another set of errors with missing role and rolebindings for the kube-node-lease namespace.
The text was updated successfully, but these errors were encountered: