Skip to content
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

fix: explicitly set ip family and family policy in gateway spec #5019

Merged
merged 3 commits into from
Jan 7, 2025

Conversation

tekulvw
Copy link
Contributor

@tekulvw tekulvw commented Jan 7, 2025

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #5004

Release Notes: Yes/No

@tekulvw tekulvw requested a review from a team as a code owner January 7, 2025 00:44
@arkodg
Copy link
Contributor

arkodg commented Jan 7, 2025

the PR looks good @tekulvw !
can we make sure there is a test for this and a unique service is generated https://github.com/envoyproxy/gateway/blob/main/internal/infrastructure/kubernetes/proxy/resource_provider_test.go

Copy link

codecov bot commented Jan 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.69%. Comparing base (c534621) to head (86411cc).
Report is 9 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5019      +/-   ##
==========================================
- Coverage   66.73%   66.69%   -0.05%     
==========================================
  Files         209      209              
  Lines       32058    32264     +206     
==========================================
+ Hits        21394    21518     +124     
- Misses       9385     9445      +60     
- Partials     1279     1301      +22     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@tekulvw tekulvw force-pushed the set-ev-proxy-ipfamily branch from 76ae649 to 12ecb06 Compare January 7, 2025 02:40
@tekulvw
Copy link
Contributor Author

tekulvw commented Jan 7, 2025

Should be good to go @arkodg

@tekulvw tekulvw changed the title Explicitly set ip family and family policy in gateway spec fix: explicitly set ip family and family policy in gateway spec Jan 7, 2025
@arkodg
Copy link
Contributor

arkodg commented Jan 7, 2025

thanks @tekulvw , can you also add a test case to TestService ?

@tekulvw
Copy link
Contributor Author

tekulvw commented Jan 7, 2025

@arkodg added, that look okay?

Signed-off-by: Will Tekulve <[email protected]>
@tekulvw tekulvw force-pushed the set-ev-proxy-ipfamily branch from 318acb2 to 32f94db Compare January 7, 2025 20:02
@arkodg
Copy link
Contributor

arkodg commented Jan 7, 2025

@tekulvw I was referring to this function

, by adding a test case here, you'd also need to add a corresponding testdata file in https://github.com/envoyproxy/gateway/tree/main/internal/infrastructure/kubernetes/proxy/testdata/services for both ipFamily: DualStack and ipFamily: IPv6, this is visually an easier way to catch regressions

@tekulvw
Copy link
Contributor Author

tekulvw commented Jan 7, 2025

Yeah I just realized, are there docs for setting up local test envs?

The new files I added should suffice.

@arkodg
Copy link
Contributor

arkodg commented Jan 7, 2025

Yeah I just realized, are there docs for setting up local test envs?

The new files I added should suffice.

you can verify locally using make test , https://gateway.envoyproxy.io/contributions/develop/ should have more info

Copy link
Contributor

@arkodg arkodg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM thanks !

@arkodg arkodg requested review from a team January 7, 2025 20:19
@arkodg arkodg merged commit 4d5d3f0 into envoyproxy:main Jan 7, 2025
25 checks passed
@tekulvw tekulvw deleted the set-ev-proxy-ipfamily branch January 7, 2025 22:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

IPv6 dual stack support not working as intended
3 participants