-
Notifications
You must be signed in to change notification settings - Fork 290
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
watcher: System.Net.Http.HttpRequestException: Error while copying content to a stream. #1507
Comments
could you please put a retry outside your watcher? |
@tg123, I have a watcher recreation logic that runs after |
this seems not a client side issue, probably server side closed the connection which is out of client side's control |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Describe the bug
OnError
callback ofWatcher<T>()
reports the following error after ~40 minutes when watching for a Kubernetes resource for which no instance exists in the cluster and no new one is created during the runtime. After the error watcher is closed (OnClosed
callback is invoked).Kubernetes C# SDK Client Version
13.0.1
Server Kubernetes Version
1.26.10
Dotnet Runtime Version
net7.0
To Reproduce
After reading description of #828 I think that Kubernetes API server must close watch connection.
Expected behavior
Even if connection is closed by Kubernetes API server, the watcher should be able to recover and no attempt should be made to read past end of stream.
KubeConfig
N/A
Where do you run your app with Kubernetes SDK (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: