Skip to content

UDP Proxy with Service Activation Support for Swiftwave

License

Notifications You must be signed in to change notification settings

swiftwave-org/udpproxy

Folders and files

NameName
Last commit message
Last commit date

Latest commit

6e61c9e · Apr 28, 2024

History

26 Commits
Apr 28, 2024
Feb 6, 2024
Feb 6, 2024
Apr 28, 2024
Mar 17, 2024
Feb 8, 2024
Feb 9, 2024
Apr 19, 2024
Apr 19, 2024
Feb 9, 2024
Feb 9, 2024
Feb 8, 2024
Feb 9, 2024
Feb 6, 2024

Repository files navigation

UDP Proxy with Service Activation Support

Why required -

Swiftwave uses HAProxy as ingress and it can handle TCP/HTTP traffic. But it can't handle UDP traffic. So, we need a UDP proxy to handle UDP traffic.

You may thought why we not using Docker Swarm Ingress for UDP traffic.

The reason is

  • we need some control over the port mapping.
  • we need something which can monitor traffic and can take action based on that. (future requirement)
  • we have some feature in our roadmap which required UDP proxy. (future requirement)

How it works -

  • It will listen on a port and forward the traffic to the destination based on the configuration.
  • It will have a backup mechanism to alert swiftwave if service is unreachable. (future requirement)
  • Will support runtime configuration change.
  • Will only managed over unix socket.

Environment Variables -

  • SOCKET_PATH - Path of the unix socket. Default: /etc/udpproxy/api.sock
  • RECORDS_PATH - Path of the records file. Default: /var/lib/udpproxy/records