Graham McIntire 4804bd16be Add distributed Erlang clustering for single APRS-IS connection ... Implement leader election to ensure only one APRS-IS connection across multiple Kubernetes replicas. This prevents duplicate packet processing and respects APRS-IS usage policies. Key changes: - Add leader election using :global registry - Create connection manager for dynamic APRS-IS management - Implement packet distribution from leader to all nodes - Add Kubernetes headless service for node discovery - Configure DNS-based clustering with libcluster - Update deployment to support 3 replicas with clustering 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>		2025-07-25 10:30:29 -05:00
..
connection_manager.ex	Add distributed Erlang clustering for single APRS-IS connection	2025-07-25 10:30:29 -05:00
leader_election.ex	Add distributed Erlang clustering for single APRS-IS connection	2025-07-25 10:30:29 -05:00
packet_distributor.ex	Add distributed Erlang clustering for single APRS-IS connection	2025-07-25 10:30:29 -05:00
packet_receiver.ex	Add distributed Erlang clustering for single APRS-IS connection	2025-07-25 10:30:29 -05:00
topology.ex	Add distributed Erlang clustering for single APRS-IS connection	2025-07-25 10:30:29 -05:00