-
Notifications
You must be signed in to change notification settings - Fork 285
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: when service type = clusterIP set the address to service.clusterIP #2582
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #2582 +/- ##
==========================================
- Coverage 64.11% 64.03% -0.08%
==========================================
Files 119 119
Lines 18561 18640 +79
==========================================
+ Hits 11901 11937 +36
- Misses 5880 5918 +38
- Partials 780 785 +5 ☔ View full report in Codecov by Sentry. |
we'll also need to update the logic in gateway/internal/status/gateway.go Line 30 in d44f4be
ClusterIP is updated in the statusthe if/else will need to be refactored a bit
|
…nvoyproxy#2166) Signed-off-by: ShyunnY <1147212064@qq.com>
Yes, I've made changes |
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
one more thing, it's not recommended to merge code from your main branch, so next time please create a new branch, thanks
/retest |
…IP (envoyproxy#2582) when service type = clusterIP set the address to service.clusterIP (envoyproxy#2166) Signed-off-by: ShyunnY <1147212064@qq.com> Signed-off-by: Stéphane Cottin <stephane.cottin@vixns.com>
What type of PR is this?
fix: when service type = clusterIP set the address to service.clusterIP
What this PR does / why we need it:
This commit solves the problem that when setting Service Type=ClusterIP and customizing the address for Gateway.spec.addresses, the address is incorrectly set to externalIPs.
I fixed it so that it can be correctly set to the ClusterIP
Which issue(s) this PR fixes:
Fixes #2166