Distinguish between the Agent hostname and binds address
The issue was reported on our mailing list.
Configuration of STORK_AGENT_HOST required special handling. Within the Kea container, I do not know what the IP address will be. Setting it to 0.0.0.0 allows Stork Agent to bind, but Stork Server will naturally never be able to connect to this. Stork Server communicates with Kea via a ClusterIP service pointing to Kea pod(s). However, within the Kea pod, Stork Agent cannot bind to this ClusterIP service. In the end, I had to resort to DNS trickery: I let the Stork Server pod resolve the ClusterIP service name as normal, though within the Kea pod this ClusterIP service resolves to 0.0.0.0, which is sufficient for Stork Agent to bind. (For those interested, I used hostAliases in the deployment YAML to override the pod DNS.) Could another environment variable be introduced to distinguish between the Stork Agent hostname as called by Stork Server and what Stork Agent binds to?