Network ingress

[arthurbarr]

The MQ Operator on Red Hat OpenShift Container Platform automatically creates Route resources to manage both HTTP/S and TCP network ingress. Different Kubernetes distributions have their own way to manage network ingress, and they're all a bit different. The Kubernetes Gateway API aims to improve this, but currently has a few problems, including:

1. TLSRoute is still experimental
2. Each cloud provider has a different way of enabling the Gateway API. For example, on EKS you need to use AWS VPC Lattice, which potentially reduces the number of people who could adopt it.

Due to this, the MQ Operator currently does not implement integration with any ingress options other than OpenShift Routes. However, the existing mq.ibm.com/v1beta1 API creates Route resources by default, which means you need to explicitly disable that integration, and then manually configure your own ingress.

There are currently no plans to change this, at least until TLSRoute moves to the standard channel, as the non-HTTP use case is the most important for MQ. We'd love any feedback on this, so I'm creating this discussion topic to get your opinion.