WIP: Stop leaking goroutines in newMultiWatch #50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes a goroutine leak in cases where Watch() is called again without a new List() inbetween Watch() calls. This happens when one of the underlying watches returns a ConnectionRefused error. See https://github.com/kubernetes/client-go/blob/3fe2abece89efc7b3a2da0ff549525f20f435263/tools/cache/reflector.go#L286
Note that I stumbled upon this leak while fixing another bug; this probably has other implications, so I'll mark it WIP for now.