-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move APIServingWithRoutine to alpha and disabled by default. #126470
Move APIServingWithRoutine to alpha and disabled by default. #126470
Conversation
/kind regression |
This should also be cherry-picked to 1.30. The failure modes are subtle and it's safer to disable entirely versus continue to try to plug gaps. @benluddy please place an item on the sig-apimachinery agenda next week to discuss the long-term maintenance impacts of this change and try to make contact with the original author to attend. /lgtm |
LGTM label has been added. Git tree hash: 6d008760969f028f83ea13148c206b213435edfc
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: benluddy, deads2k The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
/cc @wojtek-t I will attend sig-apimachinery meeting next week |
Changelog suggestion -Disabled the feature APIServingWithRoutine by default and changed its stage from Beta to Alpha.
+Disabled a previously on-by-default optimization for the API server where each **watch** response
+used a dedicated goroutine.
+The `APIServingWithRoutine` feature gate has been demoted from beta to alpha, and is now off
+by default. |
/triage accepted |
…6470-kubernetes-release-1.30 Automated cherry pick of #126470: Move APIServingWithRoutine to alpha and disabled by default.
It also make APF mutating_work_estimator.go get wrong |
@chenk008: Are you still seeing this with the feature gate disabled? We just started noticing an issue in APF with watches in our 1.31 distribution (with this feature gate disabled) and it may be due to this feature's related changes to the "get" handler itself. The gate only controls whether or not the extra filter is added to the filter chain. |
What type of PR is this?
/sig api-machinery
/sig scalability
What this PR does / why we need it:
Two regressions have been discovered related to the interaction between the APIServingWithRoutine feature and other apiserver filters whose deferred functions expect to execute only after handling a request.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Related issues:
Discussion: https://kubernetes.slack.com/archives/C0EG7JC6T/p1722358348712859
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: