-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
curl: (56) Recv failure: Connection reset by peer #2439
Comments
After a discussion on Gitter, I think I understand the issue now. Problem is that client is doing PATCH with YAML object even after there are no new changes in
|
Hi @rohanKanojia, Is there any timeline for this issue fix? Thanks, |
I would try to fix it along with #2399 |
Discussion for this issue is open in #2454. please share your thoughts there. |
Hi,
I am trying to create deployment and service using below code - This works first time, if I do curl on service external endpoint I get the reply back. If I update the yaml with updated docker image say: v2 and try curl again, I am getting this error: curl: (56) Recv failure: Connection reset by peer. If I check k8 service logs before and after 2nd deployment, NodePort and Service Endpoints are different. If I try this same scenario using kubectl CLI it works fine. Please let me know what I am doing wrong from code.
List<HasMetadata> allResources = client.load(stream).get(); client.resourceList(allResources).inNamespace("default").createOrReplaceAnd().waitUntilReady(5, TimeUnit.MINUTES);
Thanks,
Swarda
The text was updated successfully, but these errors were encountered: