Skip to content

Conversation

@dpeckett
Copy link
Collaborator

@dpeckett dpeckett commented Oct 31, 2025

Get enough infrastructure in place that integrating with the apiserver works.

Couple outstanding todos/issues:

If multiple relay connections publish the same route, netstack will use a round robin source address for the route. ATM we choose the destination for packets solely based on there destination address, this can result in packets with different source addresses than expected which will end up in a packet drop on the other end.

I need to extend icx's allowed_ips semantics to allowed_srcs / allowed_dsts or something of that nature. Will allow the icx handler to make smart routing decisions.

If the relay dies there is no garbage collection for connections on the tunnelagent object. One option is to mark connections with some kind of periodically updated lastupdated timestamp/heartbeat and when no more updates heard (from the relay owning the connection). The TunnelAgent reconciler of the apiserver can nuke them, idk. Maybe a throttled lastheardrx timestamp or other vnet stats.

While the relay is alive it does garbage collect it's own connections.

@dpeckett dpeckett requested a review from dilyevsky October 31, 2025 08:14
@dpeckett dpeckett changed the title [icxtunnel/cmd] add support for getting tunnel details from k8s [icxtunnel] Wire up controllers and integrate with kubernetes. Nov 1, 2025
@dpeckett dpeckett merged commit 5e84a7f into main Nov 7, 2025
1 check passed
@dpeckett dpeckett deleted the dpeckett/icx-k8s-support branch November 7, 2025 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants