-
Notifications
You must be signed in to change notification settings - Fork 347
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
ci: enable ipv6/dual test #4550
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4550 +/- ##
==========================================
- Coverage 65.47% 65.45% -0.02%
==========================================
Files 211 212 +1
Lines 31858 31902 +44
==========================================
+ Hits 20859 20882 +23
- Misses 9755 9774 +19
- Partials 1244 1246 +2 ☔ View full report in Codecov by Sentry. |
@zirain Do we also need to configure Kubernetes and Github nodes for IPv6/Dual-stack support? |
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.
LGTM thanks !
cc @juwon8891, when the ipFamily listener e2e tests are added, we'll need to only run it on the ipv6 and dual enabled clusters |
After envoyproxy/ratelimit#748 merged still need some code change to pass ipv6 test. |
thanks @zirain, can we track this with a issue - "Global Ratelimit doesnt working for ipv6 only cluster", and add the ipv6 only element in the matrix then |
the dual stack actually didn't work as expected, because RateLimit only work in IPv4 mode, it's not a real dual. |
Should we cherry-pick this to v1.2 branch and upgrade the ratelimit image after envoyproxy/ratelimit#748 ? |
I don't think envoyproxy/ratelimit#748 will be merged soon. |
Error: failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s):
error decoding 'service.telemetry': failing to parse metrics address "fd00:10:244::16:8888": address fd00:10:244::16:8888: too many colons in address
2024/10/29 01:07:28 collector server run finished with error: failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s):
error decoding 'service.telemetry': failing to parse metrics address "fd00:10:244::16:8888": address fd00:10:244::16:8888: too many colons in address |
More errors:
|
|
Signed-off-by: zirain <[email protected]>
Signed-off-by: zirain <[email protected]>
Signed-off-by: zirain <[email protected]>
Signed-off-by: zirain <[email protected]>
Signed-off-by: zirain <[email protected]>
Signed-off-by: zirain <[email protected]>
…nd namespace (envoyproxy#4533)" This reverts commit 3e8730f. Signed-off-by: zirain <[email protected]>
Signed-off-by: zirain <[email protected]>
No description provided.