Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

akcess list display resources even when akcess allow command failed with namespaces not found #20

Open
akankshakumari393 opened this issue Jun 20, 2022 · 0 comments

Comments

@akankshakumari393
Copy link

Describe the bug
akcess list display resources even when akcess allow command failed with namespaces not found

To Reproduce
Steps to reproduce the behavior:

  • Run akcess allow --verb get --resource pods,pods/log -n kubes in scenario where kubes namespace was not present in the cluster.
  • we got this error with no kubeconfig file being generated

Error: namespace kubes was not found: namespaces "kubes" not found

  • Then if we run akcess list we see the id for the corresponding namespaces.
- id: fbe82f34-2ef6-4328-b1dc-bc4767deba4f
  createdAt: 2022-06-20T12:19:35.564442209+05:30
  namespace: kubes

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant