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
"services "weave-scope-app" is forbidden: User "system:serviceaccount:weave:weave-scope" cannot get resource "services" in API group "" in the namespace "weave""
"deployments.extensions "weave-scope-cluster-agent" is forbidden: User "system:serviceaccount:weave:weave-scope" cannot get resource "deployments/scale" in API group "extensions" in the namespace "weave""
"deployments.apps "weave-scope-cluster-agent" is forbidden: User "system:serviceaccount:weave:weave-scope" cannot get resource "deployments" in API group "apps" in the namespace "weave""
"pods "weave-scope-cluster-agent-84df69896b-dv5zf" is forbidden: User "system:serviceaccount:weave:weave-scope" cannot get resource "pods/log" in API group "" in the namespace "weave""
"pods "weave-scope-agent-jc4vk" is forbidden: User "system:serviceaccount:weave:weave-scope" cannot delete resource "pods" in API group "" in the namespace "weave""
"pods "weave-scope-agent-jc4vk" is forbidden: User "system:serviceaccount:weave:weave-scope" cannot get resource "pods" in API group "" in the namespace "weave""
To fix this, we should add all of these to cluster-role.yaml.
The text was updated successfully, but these errors were encountered:
fbarl
added
k8s
Pertains to integration with Kubernetes
chore
Related to fix/refinement/improvement of end user or new/existing developer functionality
labels
Apr 11, 2019
While trying to test #3589 in a local Minikube instance following the instructions from https://www.weave.works/docs/scope/latest/installing/#kubernetes-local-clone, I figured almost all K8s node details actions were being rejected based on the RBAC permission setting:
To fix this, we should add all of these to
cluster-role.yaml
.The text was updated successfully, but these errors were encountered: