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
Expected behavior
akcess list should only list ids that generated kubeconfig file and the related roles/rolebinding in the cluster.
Suggestions:
we should store accessConfig resources only when the kubeconfig is ready and roles and rolebinding are generated or only when the request is valid.
The text was updated successfully, but these errors were encountered:
Describe the bug
akcess list
display resources even whenakcess allow
command failed with namespaces not foundTo Reproduce
Steps to reproduce the behavior:
akcess allow --verb get --resource pods,pods/log -n kubes
in scenario wherekubes
namespace was not present in the cluster.Error: namespace kubes was not found: namespaces "kubes" not found
akcess list
we see theid
for the corresponding namespaces.Expected behavior
akcess list should only list ids that generated
kubeconfig
file and the relatedroles/rolebinding
in the cluster.Suggestions:
we should store accessConfig resources only when the kubeconfig is ready and roles and rolebinding are generated or only when the request is valid.
The text was updated successfully, but these errors were encountered: