e2e: add e2e test for MergeGateways feature#2665
Conversation
Signed-off-by: shawnh2 <shawnhxh@outlook.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2665 +/- ##
==========================================
- Coverage 66.51% 64.60% -1.92%
==========================================
Files 161 122 -39
Lines 22673 21147 -1526
==========================================
- Hits 15080 13661 -1419
+ Misses 6720 6638 -82
+ Partials 873 848 -25 ☔ View full report in Codecov by Sentry. |
liorokman
left a comment
There was a problem hiding this comment.
LGTM
Maybe also add a test-case where there is some conflict between the gateways?
good point |
cnvergence
left a comment
There was a problem hiding this comment.
looks good, I am happy to see it!
Signed-off-by: shawnh2 <shawnhxh@outlook.com>
there is an issue while implementing this test, and it seems related to #2668 |
|
#2672 is merged, plz go ahead, thanks. |
Signed-off-by: shawnh2 <shawnhxh@outlook.com>
Signed-off-by: shawnh2 <shawnhxh@outlook.com>
|
/retest all the unstable conformance tests will be investigated via #2269 |
Signed-off-by: shawnh2 <shawnhxh@outlook.com>
Signed-off-by: shawnh2 <shawnhxh@outlook.com>
|
/retest |
Signed-off-by: shawnh2 <shawnhxh@outlook.com>
Yes. But this test seems a little unstable. |
| namespace: gateway-conformance-infra | ||
| spec: | ||
| gatewayClassName: merge-gateways | ||
| listeners: |
There was a problem hiding this comment.
is the instability because you are using the same listener name and port b/w merged-gateway-4 & merged-gateway-3
cc @cnvergence
There was a problem hiding this comment.
the merged-gateway-4 is deliberately collide with merged-gateway-3. the test case for merged-gateway-4 is to make sure the right status will be surfaced if the merge gateway is conflict with another.
Signed-off-by: shawnh2 <shawnhxh@outlook.com>
Signed-off-by: shawnh2 <shawnhxh@outlook.com>
Signed-off-by: shawnh2 <shawnhxh@outlook.com>
Signed-off-by: shawnh2 <shawnhxh@outlook.com>
Signed-off-by: shawnh2 <shawnhxh@outlook.com>
… able to run Signed-off-by: shawnh2 <shawnhxh@outlook.com>
|
hi @arkodg, I think this PR is good to go. If we running into any flakiness caused by this e2e test case, we can submit an issue to report anytime :) |
|
/retest |
3 similar comments
|
/retest |
|
/retest |
|
/retest |
|
raise #3262 to track flaky e2e test: EnvoyShutdown |
|
/retest |
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #2029