Fix coredns failing during custom networking tests#2844
Merged
jchen6585 merged 1 commit intoaws:masterfrom Mar 13, 2024
Merged
Conversation
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.
What type of PR is this?
testing
Which issue does this PR fix?:
N/A
What does this PR do / Why do we need it?:
Coredns pods are in a failing state during the custom networking suite due to missing security group rules. This doesn't affect the test result since the tests do not require DNS resolving but is still a good fix.
Testing done on this change:
Tested Custom Networking suite and tested test cases that use
AuthorizeSecurityGroupIngressandRevokeSecurityGroupIngress.Will this PR introduce any new dependencies?:
N/A
Will this break upgrades or downgrades? Has updating a running cluster been tested?:
N/A
Does this change require updates to the CNI daemonset config files to work?:
N/A
Does this PR introduce any user-facing change?:
No
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.