Application-gateway-kubernetes-ingress: Is it possible to open a port other than 80/443 for listening?

[chriskinsman]

Looking to indicate a new listener port other than 80/443.

[asridharan]

@chriskinsman we will need to add a listener specific annotation for this since ingress resource itself doesn't support this.

[yamansama]

Hi, any news on this feature ?

[DreamRivulet]

Any update on this ? Could we customize listener port ?

[olafkfreund]

Any update on this ?

[MCKLMT]

Any news on this issue? My customer requests the same and this issue is opened since one year. Thanks

[sbkg0002]

@akshaysngupta any word on this?

[schlickspringer]

we require this as well to be able to use public and private ip on different ports as AppGW does not support different IPs on one port.

[kamilzzz]

@akshaysngupta Any ideas when this might be merged?
Would be useful to have this so we can expose HTTP/HTTPS workloads using both Public and private IPs (right now when I have HTTPS configured for Public IP then I cannot expose any HTTPS service over Private IP).

[sbkg0002]

Any updates on this?

[mcarlsen]

Seems to be released in 1.4.0 (annotation appgw.ingress.kubernetes.io/override-frontend-port).

Can we get an update of the Feature Roadmap so that it reflects current reality?

Thanks!