feat: reuseport activator - #196
Draft
ctrox wants to merge 28 commits into
Draft
Conversation
ctrox
commented
Aug 9, 2026
ctrox
force-pushed
the
reuseport-activator
branch
6 times, most recently
from
August 12, 2026 05:38
8542bf1 to
c37f2fa
Compare
This adds a completely new activator that makes use of bpf_sk_select_reuseport to steer wake/probe traffic instead of a userspace proxy+port rewrites. With this, zeropod is completely out of the data path for normal app traffic.
when concurrent connections hit the wake listener, we only want to register the app listeners once.
This unifies the two activator APIs into an interface, making it possible to simply switch between them in the shim depending on the config.
This makes it more durable and also allows to migrate from the old to the new activator while keeping the same checkpoint image. This also adds bind4/bind6 programs to ensure all listeners have SO_REUSEPORT set.
ctrox
force-pushed
the
reuseport-activator
branch
from
August 14, 2026 05:59
c37f2fa to
e5bf065
Compare
ctrox
force-pushed
the
reuseport-activator
branch
from
August 14, 2026 06:28
3a0ed0b to
c975767
Compare
This adds a new binary zeropod-netinfo with a single purpose: it extracts the [activator.Listeners] from a criu snapshot for when we migrate from an older version where the snapshot did not contain a zeropod_listeners.json. This is done in a saparate binary as importing the crit grpc defs would balloon the binary and memory usage of the shim. Additionally, the old activator will also discover and write the listeners before checkpointing.
With the new reuseport-activator we need to wait for the expected ports to be listening before returning from restore, else we risk sending traffic nowhere.
Else the activator might think we're already restored if it receives an immediate request.
Double closing the wake fds caused some really bad bugs, especially during capacity eviction.
instead of during restore where we potentially wipe activity data
Otherwise it's not relevant
ctrox
force-pushed
the
reuseport-activator
branch
3 times, most recently
from
August 19, 2026 19:19
ad88c92 to
7938a32
Compare
ctrox
force-pushed
the
reuseport-activator
branch
from
August 19, 2026 19:30
7938a32 to
5e78ac6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds a completely new activator that makes use of bpf_sk_select_reuseport to steer wake/probe traffic instead of a userspace proxy+port rewrites. With this, zeropod is completely out of the data path for normal app traffic.