Promoting EndpointSlices to beta#84390
Conversation
9aa67f8 to
e7765ad
Compare
e7765ad to
7fa5469
Compare
|
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
a6d8ee0 to
0dc1296
Compare
|
/retest |
0dc1296 to
97c59f9
Compare
da92b2c to
16a0728
Compare
|
/cc |
656b7b0 to
fa5fa08
Compare
|
Do we wait for the other PRs to merge before going with this?
…On Wed, Nov 13, 2019 at 1:32 PM Kubernetes Prow Robot < ***@***.***> wrote:
@robscott <https://github.com/robscott>: The following tests *failed*,
say /retest to rerun them all:
Test name Commit Details Rerun command
pull-kubernetes-e2e-gce-device-plugin-gpu 656b7b0
<656b7b0>
link
<https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/84390/pull-kubernetes-e2e-gce-device-plugin-gpu/1194726483218665472/> /test
pull-kubernetes-e2e-gce-device-plugin-gpu
pull-kubernetes-bazel-build 656b7b0
<656b7b0>
link
<https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/84390/pull-kubernetes-bazel-build/1194726483164139522> /test
pull-kubernetes-bazel-build
pull-kubernetes-e2e-gce 656b7b0
<656b7b0>
link
<https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/84390/pull-kubernetes-e2e-gce/1194726483197693953/> /test
pull-kubernetes-e2e-gce
pull-kubernetes-integration 656b7b0
<656b7b0>
link
<https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/84390/pull-kubernetes-integration/1194726483218665475> /test
pull-kubernetes-integration
pull-kubernetes-conformance-kind-ipv6 656b7b0
<656b7b0>
link
<https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/84390/pull-kubernetes-conformance-kind-ipv6/1194726483185111040/> /test
pull-kubernetes-conformance-kind-ipv6
Full PR test history
<https://prow.k8s.io/pr-history?org=kubernetes&repo=kubernetes&pr=84390>. Your
PR dashboard <https://gubernator.k8s.io/pr/robscott>. Please help us cut
down on flakes by linking to
<https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/kubernetes/kubernetes/issues?q=is:issue+is:open> when
you hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://go.k8s.io/bot-commands>.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#84390?email_source=notifications&email_token=ABKWAVCZS3UO4DVAFBMEYVTQTRW7FA5CNFSM4JFKNIHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOED7XLLQ#issuecomment-553612718>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKWAVEAPBNUCJC25Z7HDWLQTRW7FANCNFSM4JFKNIHA>
.
|
pkg/proxy/winkernel/proxier_test.go
Outdated
There was a problem hiding this comment.
At what stage do we add EPSlice support to Windows proxiers?
There was a problem hiding this comment.
Hopefully soon, maybe 1.18. I'll try to reach out to some of the people who are more familiar with that side of things to see if we can work together to get EndpointSlice integration in place.
fa5fa08 to
3929007
Compare
3929007 to
a7e589a
Compare
|
@thockin I don't think the order matters too much between this and the related proxy PR, I'd say whichever is ready first can go in first and then the other can update based on that. I'm going to be doing the final EndpointSlice + dual stack work on kube-proxy as well, so either way, it'll be me that has to deal with whichever one gets in first. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: robscott, thockin 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 |
| ) | ||
|
|
||
| func startEndpointSliceController(ctx ControllerContext) (http.Handler, bool, error) { | ||
| if !ctx.AvailableResources[discoveryv1alpha1.SchemeGroupVersion.WithResource("endpointslices")] { |
There was a problem hiding this comment.
still need to check if the beta API is available... beta APIs can be turned off and components should tolerate that.
There was a problem hiding this comment.
and check if the EndpointSlice feature is enabled before running
Got it compiling again by removing discovery/v1alpha1 from SDK See kubernetes/kubernetes#84390
Got it compiling again by removing discovery/v1alpha1 from SDK See kubernetes/kubernetes#84390
Promoting EndpointSlices to beta Kubernetes-commit: 64f4be5
What type of PR is this?
/kind feature
What this PR does / why we need it:
EndpointSlices provide significant scalability improvements as an alternative to Endpoints. The alpha release has proved itself well through a wide variety of scale testing, including tests up to 50k endpoints in 4k node clusters. Graduating EndpointSlices to beta will ensure that network endpoints are scalable and performant by default in Kubernetes.
Special notes for your reviewer:
The KEP outlines the graduation criteria for a beta release of EndpointSlices in 1.17. Presently all requirements are merged or have PRs ready for final review/approval. I'll keep this updated with the current status of each requirement:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig network api-machinery
/priority important-soon
/milestone v1.17