New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
auth: Enable ClusterFirstWithHostNet dnsPolicy conditionally #24803
Conversation
/ci-eks |
/ci-eks |
/test |
This was overlooked in the below commit, my bad :(. Relates: 6d9772a Fixes: cilium#24774 Signed-off-by: Tam Mach <tam.mach@cilium.io>
dc41d0b
to
f6f00fa
Compare
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the interests of fixing the main branch, this seems like a good immediate solution.
It'd be good to also revisit questions like 'does this mean that mTLS is incompatible with EKS?' and more generally 'how can we avoid chicken&egg scenarios in SPIRE cfg bootstrapping?' after as well.
test-1.26-net-next was triggered twice as per below:
ci-datapath failure is happening in master branch as well https://github.com/cilium/cilium/actions/runs/4664037693. The change in this PR should not have any impact on datapath tests. Marking this ready to merge to fix ci-eks failure in master. |
This was overlooked in the below commit, my bad :(.
Relates: 6d9772a
Fixes: #24774