Change:
The test create custome EndpointSlices to validate some behaviors sending traffic, so it is clear that it expects the EndpointSlices to be ready, The API doc is vague about this situation and leaves room to interpret the "unknown behavior", quoting Since the test expects the EndpointSlices to be Ready we should set them, if we decide to change the API behavior, then we should add an additional e2e test to validate this behavior, but not use the same test to validate two different things /kind bug /kind failing-testing /sig network Slack thread
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : The test create custome EndpointSlices to validate some behaviors sending traffic, so it is clear that it expects the EndpointSlices to be ready, /kind failing-testing /sig network Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
GitHub didn't allow me to assign the following users: aauren. Note that only with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see <detailsIn response to : /assign Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Thanks I'll take this one and draft up a PR this weekend. (this comment should hopefully allow the k8s ci robot to assign this to me as well)
if you are planning to contribute more often you should apply as org member

Discussion:
}}, AddressType: addressType, Endpoints: []discoveryv1.Endpoint{ <del> {Addresses: []string{pod.Status.PodIP}}, </del> <ins> { Addresses:  []string{pod.Status.PodIP}, Conditions: discoveryv1.EndpointConditions{Ready: &readyCondTrue}, }, </ins> }, }

// create custom endpoint slices tcpProtocol := v1.ProtocolTCP <ins> readyCondTrue := true </ins> epsTemplate := &discoveryv1.EndpointSlice{ ObjectMeta: metav1.ObjectMeta{GenerateName: "e2e-custom-slice", Labels: map[string]string{

ginkgo.By("creating") eps1 := epsTemplate.DeepCopy() eps1.Endpoints = []discoveryv1.Endpoint{ <del> {Addresses: []string{pod1.Status.PodIP}}, </del> <ins> { Addresses:  []string{pod1.Status.PodIP}, Conditions: discoveryv1.EndpointConditions{Ready: &readyCondTrue}, }, </ins> } eps1.Ports = []discoveryv1.EndpointPort{{ Name:     pointer.String("port80"),

framework.ExpectNoError(err) eps2 := epsTemplate.DeepCopy() eps2.Endpoints = []discoveryv1.Endpoint{ <del> {Addresses: []string{pod2.Status.PodIP}}, </del> <ins> { Addresses:  []string{pod2.Status.PodIP}, Conditions: discoveryv1.EndpointConditions{Ready: &readyCondTrue}, }, </ins> } eps2.Ports = []discoveryv1.EndpointPort{{ Name:     pointer.String("port81"),