![]() ![]() ![]() nginx-ingress-controller version lower than nginx-0.32.0-rancher1.A Rancher Kubernetes Engine (RKE) CLI or Rancher v2.x provisioned Kubernetes cluster.The configuration request will be repeatedly retried, resulting in increased CPU usage by the nginx-ingress-controller pods. As a result, if the configuration data is greater than 10m the request will fail (in the log entry above the configuration body is 10696855 bytes, which is equal to ~10.2m). In nginx-ingress-controller versions lower than nginx-0.26.0 the client_max_body_size for this endpoint is hardcoded to 10m. ![]() The nginx-ingress-controller dynamically updates its configuration by POST'ing the data to the /configuration endpoint. Logs of the nginx-ingress-controller pods reveal error messages of the following format: T19:06:19.696272452Z 2 19:06:19 5832#5832: *28190476 client intended to send too large body: 10696855 bytes, client: unix:, server:, request: "POST /configuration/servers HTTP/1.1", host: "nginx-status" Nginx-ingress-controller pods fail to load configuration successfully, resulting in failure for some Ingress resources.
0 Comments
Leave a Reply. |