-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
tests: create ServiceEntry
with multiple VIPs in DNSTestCases
#51995
Conversation
Skipping CI for Draft Pull Request. |
/test all |
2 similar comments
/test all |
/test all |
/test integ-pilot |
@jewertow: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/test integ-pilot-multicluster |
/test integ-pilot-istiodremote-mc |
2 similar comments
/test integ-pilot-istiodremote-mc |
/test integ-pilot-istiodremote-mc |
/test all |
1 similar comment
/test all |
/test all |
0eb1cc6
to
e9acede
Compare
4ece551
to
bab7c41
Compare
/test all |
bab7c41
to
9ab5a3c
Compare
/test all |
/test integ-pilot |
1 similar comment
/test integ-pilot |
/test integ-pilot |
1 similar comment
/test integ-pilot |
/test all |
/test all |
/test integ-pilot |
2 similar comments
/test integ-pilot |
/test integ-pilot |
/test all |
ServiceEntry
with multiple VIPs in DNSTestCases
Signed-off-by: Jacek Ewertowski <[email protected]>
6ca8dfd
to
4375453
Compare
🤔 🐛 You appear to be fixing a bug in Go code, yet your PR doesn't include updates to any test files. Did you forget to add a test? Courtesy of your friendly test nag. |
} else if v4 { | ||
expectedIPv4 = []string{"1.2.3.4", "1.2.3.5"} | ||
expectedIPv6 = []string{"1234:1234:1234::1234:1234:1234"} | ||
} else { | ||
expectedIPv4 = []string{"1.2.3.4"} | ||
expectedIPv6 = []string{"1234:1234:1234::1234:1234:1234", "1235:1235:1235::1235:1235:1235"} | ||
} |
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.
Why is this the expected behavior? It seems a bit un-intuitive that when we are in "v4 only mode" we still return IPv6 addresses, just not all of them?
It may be correct, just not clear why -- a comment would help
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.
Right, it is not intuitive. These semantics comes from GetAllAddressesForProxy
. That function tries to return all available addresses if ambient or dual-stack mode is enabled. Otherwise, it returns all of the addresses for the supported IP family. If there is no IP for the supported family, it fallbacks to the default (first) address.
DNS proxy uses GetAllAddressesForProxy
to build name table, so it has the same semantics, i.e. in IPv4-only stack it will return all IPv4 addresses for A query and first IPv6 address for AAAA query.
It may be correct - to be honest, I am not sure if this is correct, but this is backward compatible.
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.
TBH this behavior seems totally broken. Can we open an issue to track it?
For now doesn't need to block the PR though, good to test our behavior even if its wrong
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.
Can we open an issue to track it?
Of course, I will do it.
Please provide a description of this PR:
It turned out that #30282 was fixed in #51967. However, I found another bug (?) related to
ServiceEntry
with multiple VIPs and described it in a comment. If we agree that the described bug should be fixed, I can create an issue with reproducing steps.