Merged
Conversation
andreeaalexandra
approved these changes
Apr 21, 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
2 participants
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.
Removing launch_config_drift check as this wasn't working before and results in aws cli rate limiting when every node is making aws api calls.
Updating local_dns_resolver script to first query for the node-local-dns pod ip and use that in the test. This is required if we want to run on the hostNetwork as our CiliumRedirectPolicy doesn't affect dns queries from the hostNetwork.
The
NODE_NAMEenv var will be injected into the pod. Through IRSA, then assume a role and use aws cli to get the info we need.Removing aws cli from the docker image as it is no longer needed.
Also, bumping base image while I'm here.