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
I was not be able to run Kail for just a namespace with a service account that has the full access for the given namespace.
There is away to have this on place?
./kail -n mynamespace
time="2020-11-20T13:48:22Z" level=error msg="client list: listing pods in : pods is forbidden: User "system:serviceaccount:mynamespace:mysa" cannot list pods at the cluster scope: no RBAC policy matched" cmp=lister
| time="2020-11-20T13:48:22Z" level=error msg="lister error: client list: listing pods in : pods is forbidden: User "system:serviceaccount:mynamespace:system:serviceaccount:mynamespace:mysa" cannot list pods at the cluster scope: no RBAC policy matched" cmp=controller
| kail: error: Unable to initialize data source
I dont want to run that with cluster role, I just want to run the Kail in single namespace with a service account that has the full access in that namespace.
The text was updated successfully, but these errors were encountered:
Hello,
I was not be able to run Kail for just a namespace with a service account that has the full access for the given namespace.
There is away to have this on place?
./kail -n mynamespace
time="2020-11-20T13:48:22Z" level=error msg="client list: listing pods in : pods is forbidden: User "system:serviceaccount:mynamespace:mysa" cannot list pods at the cluster scope: no RBAC policy matched" cmp=lister
| time="2020-11-20T13:48:22Z" level=error msg="lister error: client list: listing pods in : pods is forbidden: User "system:serviceaccount:mynamespace:system:serviceaccount:mynamespace:mysa" cannot list pods at the cluster scope: no RBAC policy matched" cmp=controller
| kail: error: Unable to initialize data source
I dont want to run that with cluster role, I just want to run the Kail in single namespace with a service account that has the full access in that namespace.
The text was updated successfully, but these errors were encountered: