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
{{ message }}
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.
Describe the bug
Using a Kubeconfig file for a GKE cluster from Rancher and adding impersonation headers to it for RBAC causes failure when running rio commands: FATA[0000] {"Code":{"Code":"Forbidden","Status":403},"Message":"clusters.management.cattle.io \"c-ghd74\" is forbidden: User \"rio-admin\" cannot get resource \"clusters\" in API group \"management.cattle.io\" at the cluster scope","Cause":null,"FieldName":""} (get rioinfos.admin.rio.cattle.io rio)
To Reproduce
Use Rancher to create a GKE cluster
After the cluster has been provisioned, save the KUBECONFIG file locally. Update the users.user section to also have:
as: rio-admin
as-groups:
- rio:admin
Run rio info or any rio command that reaches out to the cluster. It will fail
Expected behavior
Proxy the impersonation header through so as to have RBAC in rio.
Kubernetes version & type (GKE, on-prem): kubectl version
Describe the bug
Using a Kubeconfig file for a GKE cluster from Rancher and adding impersonation headers to it for RBAC causes failure when running rio commands:
FATA[0000] {"Code":{"Code":"Forbidden","Status":403},"Message":"clusters.management.cattle.io \"c-ghd74\" is forbidden: User \"rio-admin\" cannot get resource \"clusters\" in API group \"management.cattle.io\" at the cluster scope","Cause":null,"FieldName":""} (get rioinfos.admin.rio.cattle.io rio)
To Reproduce
users.user
section to also have:rio info
or any rio command that reaches out to the cluster. It will failExpected behavior
Proxy the impersonation header through so as to have RBAC in rio.
Kubernetes version & type (GKE, on-prem):
kubectl version
Type:
Rio version:
rio info
The text was updated successfully, but these errors were encountered: