Failed to list Pod: Unauthorized
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
It looks like there are still situations where we can try to start the informer when it would encounter authorization errors. Error looks like this:
E0703 16:18:33.323295 93883 reflector.go:125] github.com/windmilleng/tilt/internal/k8s/watch.go:175: Failed to list *v1.Pod: Unauthorized
Not sure under what circumstances this happens.
Reported by @theevocater
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at internal/k8s/watch.go:175 and trace the informer startup path associated with the reflector.go “Failed to list *v1.Pod: Unauthorized” message. Investigate which authorization circumstances trigger the attempt to start the informer; done means that path is understood and no longer produces this unauthorized listing failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100