Set the endpoint for a peer

[adamc-formlogic]

Like it says on the tin, I'd like to be able to set the endpoint that the wireguard agent uses to connect to a peer. For my use case, I want the agent to be able to reach out and open a tunnel proactively instead of waiting for the client to connect in to it first.

I looked quite a bit through the code, but as far as I can tell, the peers are configured in createPeersConfiguration and there does not seem to be a way to specify an endpoint.

[jodevsa]

Hey,

what would be the uscase? how would it benefit you?

[adamc-formlogic]

I have a scenario where my cluster is behind a firewall, and I'd like to establish a connection to another host which has a public IP address (but is not appropriate for running Kubernetes on). If I can specify an endpoint on the cluster side, then I can initiate the connection from there and have it reach out to the other host.

…

On Fri, Sep 15, 2023, 5:37 PM Subhi Al Hasan ***@***.***> wrote: Hey, what would be the uscase? how would it benefit you? — Reply to this email directly, view it on GitHub <#103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7R74NY3SIHNGNANK2AY4K3X2TYF5ANCNFSM6AAAAAA42FR57I> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jodevsa]

I see. So your are trying to make wireguard provisioned using wireguard-operator to connect to another wireguard site.

Making the endpoint configurable is really easy. Do you think we'll need to add any iptable rules to allow traffic to flow from both sites?

[adamc-formlogic]

For my own purposes, allowing the client to connect to the Kubernetes server is perfectly sufficient and neither side needs to reach beyond those two endpoints.