Skip to content

Chart to allow for multiple HTTP ports for Proxy #655

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
d19dotca opened this issue Aug 2, 2022 · 1 comment · May be fixed by #1265
Open

Chart to allow for multiple HTTP ports for Proxy #655

d19dotca opened this issue Aug 2, 2022 · 1 comment · May be fixed by #1265

Comments

@d19dotca
Copy link
Contributor

d19dotca commented Aug 2, 2022

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.

@tcrowder-koerber
Copy link

tcrowder-koerber commented Mar 7, 2025

We use this to enable arbitrary listeners -- hoping the PR is worthwhile

#1265

kong-dp:
  proxy:
    additionalListeners:
      - serviceName: http2-tls
        enabled: true
        servicePort: 9443
        containerPort: 9443
        protocol: TCP
        parameters: ["http2", "ssl"]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants