Skip to content
This repository has been archived by the owner on Jan 19, 2023. It is now read-only.

unable to get Lister for /v1, Resource=secrets, watcher was unable to start #3358

Open
pawankkamboj opened this issue Oct 31, 2022 · 1 comment

Comments

@pawankkamboj
Copy link

Describe the problem/challenge you have
Not able to list resources both in cluster scope or namespace scope. Assign limited RBAC so that only user can access only limited resources, only issue is with secrets, have disable secrets access so that user can not see secret data. Tried without cluster scope as well but cannot see. UI load the application page, but when try to open any application getting error.
Similarly Cluster Overview and Namespace Overview also not working. Ideally it should load the resources if there is access to secrets is forbidden.

2022-10-31T11:23:06.088+0530	ERROR	describer/describer.go:95	LoadObjects	{"err": "List: CacheKey[Namespace='xxxx', APIVersion='v1', Kind='Secret'] (error: unable to get Lister for /v1, Resource=secrets, watcher was unable to start)"}

Environment:
Octant version (use octant version): 0.25.1.0
Kubernetes version (use kubectl version): v1.21

@CharlieReitzel
Copy link

I'm getting zillions of these errors if I look in the logs. For all but the default namespace, I see no objects. Other folks connected to the same cluster can see objects (deployments, etc.). I do have the go compiler installed. Otherwise, we're all using Windows 10. Could that have an effect? Octant version 0.25.1.0. Don't know version of Kubernetes cluster (PKS).

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

No branches or pull requests

2 participants