Ports

By default applications are exposed through Traefik over HTTP(S) using Domains. When you need to reach a service directly over a raw TCP or UDP port — for example a game server, an SMTP relay, a database that should be publicly reachable, or any non-HTTP protocol — you can publish ports.

How it works

A published port maps a port on the host (the published port) to a port inside your container (the target port). Skitflow configures this through the Docker Swarm routing mesh, so the port is reachable on every node of the cluster when using ingress mode.

Configuration

Each port mapping has the following fields:

• Published Port — the external port clients connect to on the server.
• Target Port — the port your container listens on internally.
• Protocol — tcp (default) or udp.
• Publish Mode:
  • ingress (default) — routed through the Swarm routing mesh and load-balanced across all replicas/nodes.
  • host — bound directly to the node the container runs on, bypassing the routing mesh.

Managing ports

You can add multiple port mappings to a single application, and update or delete them at any time. Changes take effect on the next deploy or reload of the service.