Add feature gate for APIServingWithRoutine in v1.30
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please ask for approval from tengqm. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Pull request preview available for checking
| Name | Link |
|---|---|
| Latest commit | 59aec477d287013afa31d61017072db0e397f156 |
| Latest deploy log | https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/66a0e2fa6f268c0008da444c |
| Deploy Preview | https://deploy-preview-47253--kubernetes-io-main-staging.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Pull request preview available for checking
| Name | Link |
|---|---|
| Latest commit | 05ac0e969ab5ac07932649a3c0ce27374c8d7d02 |
| Latest deploy log | https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/66a47d2b49e18b0008734b1a |
| Deploy Preview | https://deploy-preview-47253--kubernetes-io-main-staging.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Again, LGTM for docs
- Searched for APIServingWithRoutine in Kubernetes code base
- Tracked to this code PR.
- This was implemented for https://github.com/kubernetes/kubernetes/issues/120901.
cc: @linxiulei @kubernetes/sig-api-machinery-misc
We have a LGTM from Docs - can we please get a technical review of this feature gate doc? If any details need adding for optimal clarity of this for our users, please let us know. We appreciate it, thanks!
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale