-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Description
What problem will this feature address?
At the moment when configuring an application the dokploy interface lets you publish a service port by setting the published port and the target port, but does not let you select in which mode the port is being published.
By default the port gets handled by the routing mesh and any worker node running said service may respond on any request to it even if on they're on a different physical node, which is by design from docker but causes my application to suffer significant latency changes as the nodes are in completely separate regions.
https://docs.docker.com/engine/swarm/services/#publish-ports
Describe the solution you'd like
For my specific configuration i need to be able to set the published port mode to host via the interface, otherwise if i change it only via the cli any subsequent deployment will override the configuration change and set back it to ingress mode.
So just a mode selector when publishing a port via the dokploy interface would be necessary
Describe alternatives you've considered
Currently to avoid the request to be sent to the other nodes in the cluster i had to remove each node from the swarm and have a separate copy of the application running on each one of them.
Additional context
No response
Will you send a PR to implement it?
No