Adding e2e tests covering EndpointSlice and Endpoints Controllers#84208
Adding e2e tests covering EndpointSlice and Endpoints Controllers#84208k8s-ci-robot merged 1 commit intokubernetes:masterfrom
Conversation
|
/retest |
|
/assign freehan |
4e75d70 to
287060b
Compare
|
/retest |
287060b to
b480bc2
Compare
|
The integration test appears to be a flaky failure, but the other e2e tests are failing due to EndpointSlices not being enabled by default. At this point I think that's intended behavior and will be resolved by an upcoming PR to graduate EndpointSlices to beta and enable them by default. |
b480bc2 to
8f39fac
Compare
|
/retest |
test/e2e/network/endpointslice.go
Outdated
There was a problem hiding this comment.
consider moving this into expectEndpointsAndSlices
There was a problem hiding this comment.
I ended up leaving it where it is since those functions are relying on the same set of pods existing, whereas they are each looking for unique sets of Endpoints and EndpointSlices. Hopefully with how things have been restructured now the separation makes a bit more sense, but happy to move things around if not.
test/e2e/network/endpointslice.go
Outdated
There was a problem hiding this comment.
Consider having a overarching poll, instead of waiting per object.
This may be more fault tolerant.
wait.Poll(
pod is ready?
getEndpoints
getEndpointSlice
getMatchingEndpoint
parse
)
There was a problem hiding this comment.
Good idea. Mostly did this, except split it up into one for both pods, and one for Endpoints and EndpointSlices for each test case, hopefully that makes sense.
8f39fac to
4878332
Compare
|
/retest |
test/e2e/network/endpointslice.go
Outdated
|
LGTM overall |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: freehan, robscott The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest Review the full test history for this PR. Silence the bot with an |
Since EndpointSlices and Endpoints are expected to be enabled by default for some time, it's important to have tests covering the functionality of both controllers. With some consumers relying on Endpoints and others relying on EndpointSlices, it's important to ensure both resources are generated in a timely manner with consistent attributes.
4878332 to
6d2fc09
Compare
|
/retest |
1 similar comment
|
/retest |
|
/lgtm |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Since EndpointSlices and Endpoints are expected to be enabled by default for some time, it's important to have tests covering the functionality of both controllers. With some consumers relying on Endpoints and others relying on EndpointSlices, it's important to ensure both resources are generated in a timely manner with consistent attributes.
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig network
/priority important-longterm