enhancements
enhancements copied to clipboard
kubernetes
[KEP] Graduate metrics.k8s.io API to GA
Enhancement Description
- One-line enhancement description (can be used as a release note): Promote metrics.k8s.io API from beta to stable
- Kubernetes Enhancement Proposal: Promote Resource Metrics API to GA
- Discussion Link: Agenda 2021-11-11 [shuaichen] KEP: Promote k8s resource metrics API to GA
- Primary contact (assignee): @shuaich
- Responsible SIGs: sig-instrumentation
- Enhancement target (which target equals to which milestone):
- Alpha release target (x.y): NA
- Beta release target (x.y): NA
- Stable release target (x.y): 1.25
- [ ] Alpha
- [ ] KEP (
k/enhancements) update PR(s): - [ ] Code (
k/k) update PR(s): - [ ] Docs (
k/website) update PR(s):
- [ ] KEP (
Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
Can we combine https://github.com/kubernetes/enhancements/issues/3135 and https://github.com/kubernetes/enhancements/issues/3134 into this KEP? I don't see any reason to do them all separately, it'll just be more paperwork.
Since all the APIs require some changes before graduating I don't think we should merge the KEPs as it will only make it harder for the reviewers.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and 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 issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
@dgrisonnet: GitHub didn't allow me to assign the following users: raptorsun.
Note that only kubernetes members, 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 the contributor guide
In response to this:
/unassign @shuaich /assign @raptorsun
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and 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 issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Closing in favor of opening a dedicated issue in k/k to graduate the API to stable.
/close
@dgrisonnet: Closing this issue.
In response to this:
Closing in favor of opening a dedicated issue in k/k to graduate the API to stable.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.