(tcp) Enable multi port/protocol support about tyk-helm-chart HOT 2 CLOSED

This is more for the ingress controller itself as it's a function of API definitions rather than deployment configuration. Probably requires CRDs to be usable and requires mutation of services.

For each API with a non-standard port it must be declared on the service dynamically every time API definition is changed (this is also subject to availability on the underlying infrastructure, i.e. whether a load balancer on a specific provider supports it). Raw TCP/TLS routing is not supported by k8s ingresses so most definitely needs CRDs (well, the spec can probably be abused with some annotations, but there's no standard way in k8s for this).

from tyk-helm-chart.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs, please comment if you would like this issue to remain open. Thank you for your contributions.

from tyk-helm-chart.