Open
Conversation
Contributor
Author
|
Left on a comment on what seems like a similar type of multi cast issue on the harden runner repo. We can track any fixes for our use case and remove the work around in future. Harden Runner issue: step-security/harden-runner#228 (comment) |
moshevayner
approved these changes
May 6, 2026
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
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.
Summary
devboxin CI workflowsindex.docker.iofor the docker build workflow under harden-runnerblockmodeblockby pre-creating an IPv4-only shared Dockerkindnetwork beforectlptl/kind runs*.linodeobjects.com:443for object-storage e2e coverage under harden-runnerblockmodeProblem
The original failure was
e2e-test (all) / all-e2e-testsstopping inInstall devbox, which pointed to missing bootstrap egress rather than a cache issue.After fixing the devbox bootstrap allowlist, e2e still failed before the suite started while Docker/kind created the management cluster:
failed to advertise addresses: write ip ::1->ff02::1: sendmsg: operation not permittedOur goal here was to keep harden-runner on
egress-policy: block, not relax it toaudit.Approach
devboxkindnetwork as IPv4-only in the e2e workflows*.linodeobjects.com:443for the object-storage e2e traffic that showed up in the next block-mode runValidation
Install devboxpassed underblockafter the allowlist update: https://github.com/linode/cluster-api-provider-linode/actions/runs/25401633761quicke2e underblockreached and ran the suite after the IPv4-onlykindnetwork change: https://github.com/linode/cluster-api-provider-linode/actions/runs/25455607906e2e-selector=allunderblock: https://github.com/linode/cluster-api-provider-linode/actions/runs/25457168014