title: Connecting an Azure container service such as Azure Container Instances or Azure Container Apps to enable clustering EMQX REDIS with varying ports
body: <p>I am trying to architect a container group in azure for utilizing a cluster of EMQX nodes.</p>
  <p>To achieve this, I need to be able to setup containers with separate internal IP's/FQDN's in the same subnet network.</p>
  <p>As well, I need to be able to communicate over TCP through various ports, both internally and externally that are layer 7 such as http/s and mqtt/s. The internal is for the &quot;clustering&quot; of Redis and mqtt/emqx and the external are for the devices on the mqtt client &lt;-&gt; broker relationship.</p>
  <p>What in the Azure service products can accomplish this goal that is not Azure Kubernetes Service or straight VM's?</p>
  <p>From my analysis, I see that Azure Container Apps has an ingress limitation that limits layer-7 to only http/s and no other ports can work. So, from my perspective this can't work. However, in looking at setting up a VNET with an internal load balancer would I be able to open ports on that ILB and open ports on the internal containers. I don't think I can but would want to confirm.</p>
  <p>For Azure Container Instances, there is no way to use a load balancer but I do have more control over the ports. Again, is there anyway to utilize a load balancer that would or anything that could take an internal container group and communicate in a subnet/vnet that would allow each other?</p>
  <p>If there is nothing possible than I think AKS it is but I wanted to confirm.</p>