kubernetes掌舵:“失去与吊舱的连接"并且“运输正在关闭";错误 [英] kubernetes helm: "lost connection to pod" and "transport is closing" errors

查看:71
本文介绍了kubernetes掌舵:“失去与吊舱的连接"并且“运输正在关闭";错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我运行helm upgrade --install来修改kubernetes集群的状态,有时会出现如下错误:

I run helm upgrade --install to modify the state of my kubernetes cluster and I sometimes get an error like this:

22:24:34 StdErr: E0126 17:24:28.472048   48084 portforward.go:178] lost connection to pod
22:24:34 Error: UPGRADE FAILED: transport is closing

似乎我不是唯一的一个,而且似乎发生在许多不同的头盔命令中.所有这些github问题都有描述或注释,提及到pod的连接丢失"或传输正在关闭"错误(通常都是):

It seems that I am not the only one, and it seems to happen with many different helm commands. All of these github issues have descriptions or comments mentioning "lost connection to pod" or "transport is closing" errors (usually both):

  • https://github.com/kubernetes/helm/issues/1183
  • https://github.com/kubernetes/helm/issues/2003
  • https://github.com/kubernetes/helm/issues/2025
  • https://github.com/kubernetes/helm/issues/2288
  • https://github.com/kubernetes/helm/issues/2560
  • https://github.com/kubernetes/helm/issues/3015
  • https://github.com/kubernetes/helm/issues/3409

虽然通读数百个github问题评论可能很有教育意义,但通常在stackoverflow上追逐追赶更快,而且看来这个问题似乎还不存在,所以就在这里.希望能够快速解决症状,并最终在答案中得到一个或多个根本原因诊断.

While it can be educational to read through hundreds of github issue comments, usually it's faster to cut to the chase on stackoverflow, and it didn't seem like this question existed yet, so here it is. Hopefully some quick symptom fixes and eventually one or more root cause diagnoses end up in the answers.

推荐答案

内存限制对我造成了此错误.以下内容对其进行了修复:

Memory limits were causing this error for me. The following fixed it:

kubectl set resources deployment tiller-deploy --limits=memory=200Mi

这篇关于kubernetes掌舵:“失去与吊舱的连接"并且“运输正在关闭";错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆