zalando-incubator / zalando-incubator/stackset-controller
Detect when controller loses connection to API server
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 183
- Forks
- 29
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 5
Description
We see this in the logs when API servers are rolled (presumably):
W0304 09:48:56.883806 1 reflector.go:340] pkg/mod/k8s.io/client-go@v0.0.0-20191202165906-e3970fe37d8a/tools/cache/reflector.go:108: watch of *v1.StackSet ended with: an error on the server ("unable to decode an event from the watch stream: context deadline exceeded (Client.Timeout or context cancellation while reading body)") has prevented the request from succeeding
This currently wouldn't be catched by the previous PRs https://github.com/zalando-incubator/stackset-controller/pull/204 and https://github.com/zalando-incubator/stackset-controller/pull/203
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 by reviewing PRs 204 and 203, then examine the reflector.go watch error shown in the logs. Determine how the controller should detect this API-server connection loss and define completion as handling this failure case without leaving the controller unaware.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100