NodePorts cannot always be reached about helm-charts

[micw]

I did some work to make mailu independent of the type of ingress controller (especially by moving all internals like authentication into the internal nginx), so taht it can be used with nginx, traefik 1/2,AWS and whatever. This change is for http/s ingress only. The current master branch works with standard ingress annotations without any ingress-controller specific extra annotations.

For the mail ports, things are completely different because there is (afaik) no standard for specifying it as a kubernetes resource. If you are using the kuberneres yamls we provide, you can easily remove the nodePorts and add your own ingress stuff. If you plan to use the (not yet official) helm chart, I can add an option to disable node ports.

How does Azure deal with tcp ingress? Do you need to deploy a special ingress controllers or do they provide kind of tcp load balancer that can be pointed to a service?

[WebSpider]

I understand your efforts to make mailu independent of ingress type, and I agree with the move! 👍🏾

Ingress for generic tcp services you can usually do 3 ways:

• l7/4 using ingress/loadbalancer
• l4 using services/loadbalancer
• l4 using nodeport

Azure supports l4 using service/loadbalancer. I'll put in some work to add Azure support for these helm charts, and test it.

[micw]

It would make sense to add a second (external) service for this case because not all service ports must be reached externally.

[micw]

@WebSpider how can we proceed with this? I'd like to see this fixed and/or closed ;-)

[micw]

Closing due to inactivity

[WebSpider]

Completely forgot about reporting back for this.

I did the research, and Azure basically can use any controller that supports spinning up an Azure loadbalancer, either internal only or external, and can map TCP/UDP ports through that loadbalancer to a nodeport. The nodeports themselves are not directly accessible.

[micw]

I have still no idea what needs to be changed to solve this

[masterkain]

I deploy on EKS and Kapsule and I would like to try this chart out.

regarding the option to disable node ports, is that already available?
would that then work with the posted link regarding nginx balancing tcp/udp services?
I guess that might depend on the public provider balancer we have in front. EKS might be out of question since I don't use/intend to use a tcp balancer. Kapsule by Scaleway might work I have to try.

thanks 👍