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

Graduate the kube-scheduler ComponentConfig to v1beta1 #785

Open
luxas opened this Issue Jan 30, 2019 · 2 comments

Comments

Projects
None yet
7 participants
@luxas
Copy link
Member

luxas commented Jan 30, 2019

Enhancement Description

  • One-line enhancement description (can be used as a release note): Usage of the kube-scheduler configuration file has graduated from experimental, as the API version now is v1beta1
  • Primary contact (assignee): @luxas
  • Responsible SIGs: @kubernetes/sig-scheduling-api-reviews @kubernetes/wg-component-standard
  • Design proposal link (community repo): N/A
  • Link to e2e and/or unit tests:
  • Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @bsalamat @k82cn
  • Approver (likely from SIG/area to which enhancement belongs): @bsalamat @k82cn
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (x.y)
    • Beta release target (x.y) 1.14
    • Stable release target (x.y) 1.15

The kube-scheduler ComponentConfig is currently in v1alpha1. The spec needs to be graduated to v1beta1 and beyond in order to be usable widely.
/assign @bsalamat @k82cn

@sttts

This comment has been minimized.

Copy link
Contributor

sttts commented Jan 31, 2019

We need a thorough API review of the kube-scheduler component config in the light of unifying them for all components. Moving what we have to beta in the 1.14 time frame feels like rushing in the light of us having just started with component-base.

@claurence

This comment has been minimized.

Copy link

claurence commented Feb 5, 2019

@luxas I don't see a KEP for this issue links in the description. I'm removing it from the 1.14 milestone - to have it added back please file an exception request.

@claurence claurence removed this from the v1.14 milestone Feb 5, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment