[Bug]: Mergable Ingreseses - Minion Ingress shows incorrect port.

[jo-carter]

Version

3.5.2

What Kubernetes platforms are you running on?

Other

Steps to reproduce

Kubectl get ingress <ingress> output for Minion Ingresses shows an incorrect port value (80 only), when TLS enabled in the Master. The Master ingress shows the correct ports value 80, 443.

This can be reproduced using the Mergeable Ingresses example.

[github-actions]

Hi @jo-carter thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!

[j1m-ryan]

Hi @jo-carter, thanks for reporting. We've replicated this and will look into to it further.
With the mergeable ingress example we get this currently

NAME                         CLASS   HOSTS              ADDRESS   PORTS     AGE
cafe-ingress-coffee-minion   nginx   cafe.example.com             80        32s
cafe-ingress-master          nginx   cafe.example.com             80, 443   32s
cafe-ingress-tea-minion      nginx   cafe.example.com             80        32

[j1m-ryan]

It's not ideal but I don't think we can affect this programmatically. For printing ingresses, Kubernetes looks at the ingress spec.
If you add a TLS section to a minion, it will show up here, but will not make any difference in NIC.