You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's been requested before that the Kong Helm Charts be expanded to allow for multiple HTTP port listeners, rather than just the one. It seems the Kong Helm Chart is limited to only one HTTP port and one HTTPS port, for example, but in some cases users will want to have the Kong Proxy listen on multiple HTTP ports for network logic / routing purposes. The Kong Gateway allows for multiple HTTP and HTTPS listener ports at the application level, but it doesn't seem the Helm Chart allows for that at this time.
Specifically, the customer words it like this: The kong chart currently only allows you to configure the proxy to listen on one HTTP and one TLS port. We've found this overly restrictive as we try to consolidate on a single kong running in our environments. In particular it limits our options to accept unencrypted HTTP/1 and HTTP/2 (gRPC) as kong can not accept both types of traffic on the single unencrypted port, forcing us to carry one over TLS.
The text was updated successfully, but these errors were encountered:
It's been requested before that the Kong Helm Charts be expanded to allow for multiple HTTP port listeners, rather than just the one. It seems the Kong Helm Chart is limited to only one HTTP port and one HTTPS port, for example, but in some cases users will want to have the Kong Proxy listen on multiple HTTP ports for network logic / routing purposes. The Kong Gateway allows for multiple HTTP and HTTPS listener ports at the application level, but it doesn't seem the Helm Chart allows for that at this time.
Specifically, the customer words it like this: The kong chart currently only allows you to configure the proxy to listen on one HTTP and one TLS port. We've found this overly restrictive as we try to consolidate on a single kong running in our environments. In particular it limits our options to accept unencrypted HTTP/1 and HTTP/2 (gRPC) as kong can not accept both types of traffic on the single unencrypted port, forcing us to carry one over TLS.
The text was updated successfully, but these errors were encountered: