Graduate the kube-scheduler ComponentConfig to GA

[luxas]

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): @alculquicondor
• Responsible SIGs: @kubernetes/sig-scheduling-api-reviews @kubernetes/wg-component-standard
• KEP: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/785-scheduler-component-config-api
• 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.19
  • Stable release target (x.y) 1.25

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]

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]

@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.

[kacole2]

@luxas I'm the enhancement lead for 1.15. I don't see a KEP filed for this enhancement and per the guidelines, all enhancements will require one. Please let me know if this issue will have any work involved for this release cycle and update the original post reflect it. Thanks!

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[mtaufen]

/remove-lifecycle stale
/lifecycle frozen

[fejta-bot]

Enhancement issues opened in kubernetes/enhancements should never be marked as frozen.
Enhancement Owners can ensure that enhancements stay fresh by consistently updating their states across release cycles.

/remove-lifecycle frozen

[mrbobbytables]

Hey there @luxas, I'm one of the 1.16 Enhancement Shadows. Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.16 Tracking Spreadsheet. If not's graduating, I will remove it from the milestone and change the tracked label.

Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly.

As a reminder, every enhancement requires a KEP in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements.

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

[bsalamat]

@mrbobbytables given that this issue does not have an owner and we didn't plan it for 1.16 in SIG scheduling, I doubt if this can make it to 1.16, but given that we still have another ~10 days before enhancement freeze, we may still be able to squeeze this in. If I find an owner for this, I will update it and will let you know.
Let's remove this from 1.16 for now.

[jfbai]

@bsalamat I’d like to work on this if you have not assign to anyone.

[bsalamat]

@jfbai Please go ahead and send a KEP as soon as possible. The KEP must be merged by the end of July for this to be considered for 1.16.

[jfbai]

@jfbai Please go ahead and send a KEP as soon as possible. The KEP must be merged by the end of July for this to be considered for 1.16.

@bsalamat Are there any big changes against kube-scheduler configuraions when graduating to v1beta1? Or, just keep it same as v1alpha1?

According to Moving ComponentConfig API types to staging repos, ComponentConfig is to split component config to internal and external with version, and move external versioned config to staging/, so, my understanding is there is no structure changes will be introduced.

If I missed something important, could you please provide suggestion to accomplish this work, since I am lack of knowledge about related works.

[bsalamat]

@bsalamat Are there any big changes against kube-scheduler configuraions when graduating to v1beta1? Or, just keep it same as v1alpha1?

Initially we didn't plan to make any changes, but now we should make sure that fields are optional as is proposed by: #1173

We need to wait for that KEP to be implemented. For that reason, we cannot promote the scheduler config to beta in 1.16.

[jfbai]

@bsalamat Are there any big changes against kube-scheduler configuraions when graduating to v1beta1? Or, just keep it same as v1alpha1?

Initially we didn't plan to make any changes, but now we should make sure that fields are optional as is proposed by: #1173

We need to wait for that KEP to be implemented. For that reason, we cannot promote the scheduler config to beta in 1.16.

I see, thanks a lot.

[ahg-g]

/remove-lifecycle stale

[kerthcet]

I'd like to take this as graduate CC to GA, mentioned by @alculquicondor before kubernetes/kubernetes#108444 (comment)

[kerthcet]

Tracking TODOs:

• Updating samples in the website to use the v1 API.

[Priyankasaggu11929]

Hello @kerthcet, @alculquicondor 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 23, 2022.

For note, This enhancement is targeting for stage stable for 1.25 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable
• KEP has a updated detailed test plan section filled out
• KEP has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

For note, the status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[Priyankasaggu11929]

Hello @kerthcet 👋

Checking in once more as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 2022.

Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are fully merged by the code freeze deadline.
  • Graduate component config to stable in kube-scheduler kubernetes#110534
  • Deprecate kubescheduler ComponentConfig v1beta2 kubernetes#111547 (updated)

Please verify, if there are any additional k/k PRs besides the ones listed above.

Please plan to get the open PRs merged by the code freeze deadline. The status of the enhancement is currently marked as at-risk.

Also kindly update the issue description with the relevant links for tracking purposes. Thank you so much!

[Priyankasaggu11929]

With the code k/k PRs merged now, this enhancement is ready for the 1.25 code freeze.

(updated)
The status is now marked as tracked. Thank you!

Will wait for the following PR to merge as well before marking it as tracked:

• Deprecate kubescheduler ComponentConfig v1beta2 kubernetes#111547

[kerthcet]

FYI we have another related PR kubernetes/kubernetes#111547 here, just one log warning. @Priyankasaggu11929

[Priyankasaggu11929]

Thanks so much for pointing @kerthcet. Have updated my comments above with the open PR ^ 🙂

[Priyankasaggu11929]

With k/k PR kubernetes/kubernetes#111547 merged now, marking this enhancement as tracked for code freeze. Thank you so much @kerthcet.

[kikisdeliveryservice]

As the KEP has been marked as implemented, closing this issue.