Some use cases require tight control over the entire service spec (see https://github.com/l7mp/stunner-gateway-operator/issues/32), including the target port. One reason for that would be to route a TCP/TLS Gateway listener opened externally on port 443 to a non-privileged port (>1024) at the data plane pods.
The plan is to add yet another annotation, say, stunner.l7mp.io/targetport, to the Gateway that would allow for setting the target port on a per-listener basis. This would be similar to the stunner.l7mp.io/nodeport annotation, just affecting the target port instead of the node port, see https://github.com/l7mp/stunner/blob/main/docs/GATEWAY.md#load-balancer-configuration.
Some use cases require tight control over the entire service spec (see https://github.com/l7mp/stunner-gateway-operator/issues/32), including the target port. One reason for that would be to route a TCP/TLS Gateway listener opened externally on port 443 to a non-privileged port (>1024) at the data plane pods.
The plan is to add yet another annotation, say,
stunner.l7mp.io/targetport, to the Gateway that would allow for setting the target port on a per-listener basis. This would be similar to thestunner.l7mp.io/nodeportannotation, just affecting the target port instead of the node port, see https://github.com/l7mp/stunner/blob/main/docs/GATEWAY.md#load-balancer-configuration.