Nginx.ingress.kubernetes.io/proxy-body-size 不工作
Nginx.ingress.kubernetes.io/proxy-body-size not working
我想增加 post Ingress 中每个请求正文的大小。所以我添加了
nginx.ingress.kubernetes.io/proxy-body-size: 8m
在 yaml 文件入口中(在 view/edit 牧场主的 yaml 文件中)但它不起作用。当我使用 kubectl 获得入口描述时,我没有看到添加的注释,但我看到了新添加的映射。
这是配置:
YAML 文件:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
annotations:
ingress.kubernetes.io/configuration-snippet: |-
set $test_host "testdms.test.com"
if ($host == $test_host) {
return 301 $scheme://$test_host/webui/;
}
nginx.ingress.kubernetes.io/proxy-body-size: 8m
creationTimestamp: 2018-09-11T12:19:02Z
generation: 116
name: test-dms
namespace: test-dms
resourceVersion: "95490045"
selfLink: /apis/extensions/v1beta1/namespaces/test-dms/ingresses/test-dms
uid: de7c4c1b-b5bc-11e8-84c0-005056bf6431
spec:
rules:
- host: testdms.test.com
http:
paths:
- backend:
serviceName: ingress-e5a45b0dc688c653b79d4b5942ebbe7c
servicePort: 80
path: /test
status:
loadBalancer:
ingress:
- {}
- ip: 198.100.101.171
- ip: 198.100.101.172
- ip: 198.100.101.173
- ip: 198.100.101.61
描述结果:
Annotations:
configuration-snippet: set $test_host "testdms.test.com"
if ($host == $test_host) {
return 301 $scheme://$test_host/webui/;
}
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal UPDATE 36s (x38 over 2h) nginx-ingress-controller Ingress test-dms/test-dms
Normal UPDATE 21s (x47 over 23d) nginx-ingress-controller Ingress test-dms/test-dms
Normal UPDATE <invalid> (x47 over 23d) nginx-ingress-controller Ingress test-dms/test-dms
Normal UPDATE <invalid> (x84 over 64d) nginx-ingress-controller Ingress test-dms/test-dms
Normal UPDATE <invalid> (x39 over 12d) nginx-ingress-controller Ingress test-dms/test-dms
修改K8s中的ingress对象有时会出现异常,所以建议重新创建而不是编辑。
如果仍然无效,请尝试使用 configmap
为所有入口规则全局设置此值
apiVersion: v1
kind: ConfigMap
metadata:
name: nginx
namespace: ingress-nginx
labels:
app: ingress-nginx
data:
proxy-body-size: "8m"
您需要添加引号(例如 "8m"
),如下所示:
nginx.ingress.kubernetes.io/proxy-body-size: "8m"
注解
nginx.ingress.kubernetes.io/proxy-body-size: 8m
被忽略可能是使用错误的 nginx-ingress 控制器实现的结果。不确定是否是这种情况,在这里。您使用了哪种实现方式?
详情见this answer by ololoepepe。
我想增加 post Ingress 中每个请求正文的大小。所以我添加了
nginx.ingress.kubernetes.io/proxy-body-size: 8m
在 yaml 文件入口中(在 view/edit 牧场主的 yaml 文件中)但它不起作用。当我使用 kubectl 获得入口描述时,我没有看到添加的注释,但我看到了新添加的映射。 这是配置:
YAML 文件:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
annotations:
ingress.kubernetes.io/configuration-snippet: |-
set $test_host "testdms.test.com"
if ($host == $test_host) {
return 301 $scheme://$test_host/webui/;
}
nginx.ingress.kubernetes.io/proxy-body-size: 8m
creationTimestamp: 2018-09-11T12:19:02Z
generation: 116
name: test-dms
namespace: test-dms
resourceVersion: "95490045"
selfLink: /apis/extensions/v1beta1/namespaces/test-dms/ingresses/test-dms
uid: de7c4c1b-b5bc-11e8-84c0-005056bf6431
spec:
rules:
- host: testdms.test.com
http:
paths:
- backend:
serviceName: ingress-e5a45b0dc688c653b79d4b5942ebbe7c
servicePort: 80
path: /test
status:
loadBalancer:
ingress:
- {}
- ip: 198.100.101.171
- ip: 198.100.101.172
- ip: 198.100.101.173
- ip: 198.100.101.61
描述结果:
Annotations:
configuration-snippet: set $test_host "testdms.test.com"
if ($host == $test_host) {
return 301 $scheme://$test_host/webui/;
}
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal UPDATE 36s (x38 over 2h) nginx-ingress-controller Ingress test-dms/test-dms
Normal UPDATE 21s (x47 over 23d) nginx-ingress-controller Ingress test-dms/test-dms
Normal UPDATE <invalid> (x47 over 23d) nginx-ingress-controller Ingress test-dms/test-dms
Normal UPDATE <invalid> (x84 over 64d) nginx-ingress-controller Ingress test-dms/test-dms
Normal UPDATE <invalid> (x39 over 12d) nginx-ingress-controller Ingress test-dms/test-dms
修改K8s中的ingress对象有时会出现异常,所以建议重新创建而不是编辑。
如果仍然无效,请尝试使用 configmap
为所有入口规则全局设置此值 apiVersion: v1
kind: ConfigMap
metadata:
name: nginx
namespace: ingress-nginx
labels:
app: ingress-nginx
data:
proxy-body-size: "8m"
您需要添加引号(例如 "8m"
),如下所示:
nginx.ingress.kubernetes.io/proxy-body-size: "8m"
注解
nginx.ingress.kubernetes.io/proxy-body-size: 8m
被忽略可能是使用错误的 nginx-ingress 控制器实现的结果。不确定是否是这种情况,在这里。您使用了哪种实现方式?
详情见this answer by ololoepepe。