Use gateway name as Proxy fleet name for Gateway Namespace mode#6135
Use gateway name as Proxy fleet name for Gateway Namespace mode#6135zirain merged 1 commit intoenvoyproxy:mainfrom
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #6135 +/- ##
==========================================
- Coverage 70.62% 70.58% -0.04%
==========================================
Files 219 219
Lines 36500 36511 +11
==========================================
- Hits 25777 25772 -5
- Misses 9195 9210 +15
- Partials 1528 1529 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
internal/infrastructure/kubernetes/proxy/resource_provider_test.go
Outdated
Show resolved
Hide resolved
internal/infrastructure/kubernetes/proxy/testdata/gateway-namespace-mode/deployment.yaml
Outdated
Show resolved
Hide resolved
706dfc7 to
9a8ce26
Compare
There was a problem hiding this comment.
ha, can we decorate this with comments, mentioning that we need the IR key here to set in serviceCluster
another option is to pass the IR key into
and eventually pass the context here ?There was a problem hiding this comment.
the root cause there's two type thing in this name field
- In controller namspace mode, it's
ns/name(equal to irKey) - In gateway namespace mode, it's just the name.
we'd better clean this in a follow up PR.
There was a problem hiding this comment.
can we avoid this ? looks like its following alphabetical order ?
There was a problem hiding this comment.
Before, it's hand made. Now it's part of make go.testdata.complete, which is better IMO.
arkodg
left a comment
There was a problem hiding this comment.
LGTM thanks !
added one comment
Signed-off-by: zirain <zirain2009@gmail.com>
fixes: #6131