I am running an AWS EKS cluster to which I am deploying HAPRoxy ingress, specifically https://github.com/jcmoraisjr/haproxy-ingress.

If I have 3 nodes, I can only deploy 3 haproxy ingress pods, one on each node. So if I scale up the number of pods to 4, the 4th pod will remain in pending status until a 4th node is created which the haproxy will be scheduled to. If I describe the pending pod, here's what I get:

Events:           
Type     Reason            Age                From                Message
----     ------            ----               ----                -------
Warning  FailedScheduling  21s (x2 over 22s)  default-scheduler   0/3 nodes are available: 3 node(s) didn't have free ports for the requested pod ports.
Normal   TriggeredScaleUp  19s                cluster-autoscaler  pod triggered scale-up: [{eks-zoneb-a4bf12c4-e990-4d84-8b5b-68dd161aa140 1->2 (max: 4)}]

My question is, is there a way to configure haproxy such that multiple haproxy pods can be deployed to the same node?