kubernetes-ingress-controller

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

2.5.1.0

Current Behavior

When calling kong.response.exit(), the function automatically sets the Content-Length header on the response even if the Transfer-Encoding header is present. This is in violation of RFC 7230 3.3.2:

A sender MUST NOT send a Content-

Version

1.10.x (beta)

Is your feature request related to a problem? Please describe.

We have customer requests to expose the following HCM properties:

• headers_with_underscores_action
• max_requests_per_connection

It sounds like they are now available on the go-control-plane version we use.

EDIT: additional note: https://www.envoyproxy.io/docs/envoy/latest/api-v3/ex

Hello everyone!

For a sake of consistency we can improve our AWS policy JSON document:

Instead of https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/e7bc45885e052b6734056fea7497bdfd2fb46e81/docs/install/iam_policy.json#L6

        {
            "Effect": "Allow",
            "Action": "iam:CreateServiceLinkedRole",
            "Resource": "*",
            "Cond

NOTE: GitHub issues are reserved for bug reports only.
For anything else, please join the conversation
in Kong Nation https://discuss.konghq.com/c/kubernetes.