Currently our non-http/https services must live on Convox gen1. I believe if gen2 supported Network Load Balancers, we could move those services over to gen2 and drop gen1 altogether.
6 Likes
I second this request. I’m trying to run a rabbitmq service and need to to expose both 5672 (TCP) and 15672 (HTTPS).
I believe that in order to make this possible Convox will need to be able to create Network Load Balancers and not just Application Load Balancers.
Unrelated, but another option may be the addition of a rabbitmq resource?
1 Like
We’re facing the same situation. So I agree with OP.
+1 for either TCP connections on Gen2 or a RabbitMQ resource type
What’s the status on this. Is there a workaround? This is a serious limitation that requires an official response.
TCP/UDP load balancing will not be coming to existing Gen 2 applications.
The new Kubernetes-based Racks have the ability to create custom load balancers which do support arbitrary TCP.
I’m guessing the answer is no, but can we expose ports to containers in Gen 2 racks? I’d like to cluster my elixir nodes but I need to open port 4369 and 9000 to internal traffic. Is this possible with Gen 2 racks?
I’d love this feature in Gen 2 racks:
Just for curiosity: what are the main reasons why people don’t move from Rack gen2 to Rack gen3 yet?
1 Like
- Price. Gen 3 has 3 NLB which add up.
- Metrics. With Gen 2, I can see the metrics at the load balancer in AWS, so I can see if AWS is sending back 50x before they even reach my app server. NLB don’t provide the same metrics. Instead, I have to hook up Datadog which is an added cost.
- No subdomain wildcard support
@alon Sadly, I never figured it out. I wish I could!
1 Like