英文:
Helm/Kube Error: query: failed to query with labels: stream error
问题
有人遇到过helm的类似问题吗?即使使用helm list命令,我也会得到以下错误信息:
查询失败,原因可能是读取响应正文时出现流错误,可能是由于连接关闭引起的。请重试。原始错误:流错误:流ID 3;INTERNAL_ERROR;来自对等方的接收。
英文:
Anyone faced similar issue with helm, even with helm list I get that
query: failed to query with labels: stream error when reading response body, may be caused by closed connection. Please retry. Original error: stream error: stream ID 3; INTERNAL_ERROR; received from peer
答案1
得分: 3
在我的情况下,我发现这是一个超时问题。
以下是我调试和修复问题的方法。
调试:
helm ls --debug
删除旧版本:
kubectl get secrets --all-namespace | grep -i <helm chart的名称>
kubectl delete secret <在这里输入名称>
解决方法:我增加了超时时间,这暂时解决了问题:
helm install <名称> <文件夹> --wait --timeout 10m0s --debug
我相信这个问题的根本原因是apiserver的限流问题,我需要进一步检查以找到缓慢的根本原因。
英文:
In my case I found that it was a timeout issues.
Below are the ways I debuged and fixed the issue.
debug
helm ls --debug
delete older versions
kubectl get secrets --all-namespace | grep -i <name of your helm chart>
kubectl delete secret <name here>
Workaround: I increased the timeout and this helped for now:
helm install <name> <folder> --wait --timeout 10m0s --debug
I believe the root cause of this issue is with the apiserver throttle which, I need to check more to find the root cause for slowness.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库,让每个人都能够通过互相帮助和分享经验来进步。
评论