简体   繁体   English

错误:创建:创建失败:服务器响应状态码 413 但未返回更多信息

[英]Error: create: failed to create: the server responded with the status code 413 but did not return more information

My helm was properly working and I have been working with it this morning for a couple of hours.我的舵机工作正常,今天早上我已经用它工作了几个小时。 Then, suddenly it stopped working and the only error I get is Error: create: failed to create: the server responded with the status code 413 but did not return more information .然后,它突然停止工作,我得到的唯一错误是Error: create: failed to create: server respond with the status code 413 but didn't return more information

Any ideas?有任何想法吗?

Ok, I found it.好的,我找到了。 I, without paying much attention or caring about the location of the file, was saving some log data from a couple of Kubernetes pods in the same directory as my template files.我没有太在意或关心文件的位置,而是将一些来自 Kubernetes pod 的日志数据保存在与我的模板文件相同的目录中。 Once I deleted the log file, which was apparently quite large, I got rid of the error and my helm install command was working.一旦我删除了显然很大的日志文件,我就摆脱了错误并且我的 helm install 命令正在工作。 I guess HELM cares about the sizes of the files even if they have nothing to do with your helm installation.我猜 HELM 关心文件的大小,即使它们与您的 helm 安装无关。 This was my case though, your case could be different.这是我的情况,你的情况可能会有所不同。 But I hope this post helps you in any way.但我希望这篇文章对你有任何帮助。 It was a weird one in this case.在这种情况下,这很奇怪。

I guess the same thing could happen if your charts grew too much.我想如果你的图表增长太多,同样的事情也会发生。

Cheers.干杯。

I had this error message when trying to install kube-prometheus-stack.尝试安装 kube-prometheus-stack 时出现此错误消息。

I have an nginx load balancer in front of kube-apiserver for high availability.我在 kube-apiserver 前面有一个 nginx 负载均衡器以实现高可用性。
Note: don't confuse this with nginx ingress controler.注意:不要将此与 nginx 入口控制器混淆。

By default nginx has client_max_body_size 1m .默认情况下 nginx 有client_max_body_size 1m
To solve the problem I had to increase this setting by editing /etc/nginx/nginx.conf in my ubuntu VM:为了解决这个问题,我必须通过在我的 ubuntu VM 中编辑/etc/nginx/nginx.conf来增加这个设置:

http {
    client_max_body_size 10m;
}

And if you're using Rancher you need to edit the nginx-ingress-controller's configMap from the local cluster where Rancher is installed and add:如果您使用的是 Rancher,则需要从安装 Rancher 的local集群中编辑 nginx-ingress-controller 的 configMap 并添加:

data:
  proxy-body-size: 10m

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 错误:升级失败:无法创建资源:版本“v1”中的 ConfigMap 无法作为 ConfigMap 处理 - Error: UPGRADE FAILED: failed to create resource: ConfigMap in version "v1" cannot be handled as a ConfigMap Kubernetes 部署失败,在 GKE 中显示“创建 pod 沙箱失败” - Kubernetes deploy failed with "Failed create pod sandbox" in GKE 安装失败并出现错误 create: failed to create: Secret "sh.helm.release.v1.<release> .v1" 无效:数据:太长:最多必须有 1048576 字节</release> - Install fails with error create: failed to create: Secret "sh.helm.release.v1.<release>.v1" is invalid:data:Too long:must have at most 1048576 bytes Spinnaker - “创建LoadBalancer”期间出错 - Spinnaker - Error during 'Create LoadBalancer' EKS 上的 Spark 运算符 Apache spark 无法创建临时目录 - Spark-operator on EKS Apache spark failed to create temp directory 头盔升级:无法在Google Container Builder上创建补丁 - helm upgrade: failed to create patch on google container builder Gitlab Runner - HELM - 错误:作业失败:退出代码 1 - Gitlab Runner - HELM - ERROR: Job failed: exit code 1 测试失败时的 Helm 部署状态 - Helm deployment status if tests failed 如何调试 helm secret status=failed - how to debug helm secret status=failed 错误 503 后端获取失败 Guru Meditation: XID: 45654 Varnish 缓存服务器 - Error 503 Backend fetch failed Guru Meditation: XID: 45654 Varnish cache server
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM