implement job allocation completions index enhancement

[fudali113]

Enhancement Description

• One-line enhancement description (can be used as a release note): implement job allocation completions index enhancement
• Kubernetes Enhancement Proposal: implement job allocation completions index enhancement #1072
• Primary contact (assignee): @soltysh @janetkuo
• Responsible SIGs: sig-job
• Enhancement target (which target equals to which milestone):
  • Alpha release target (1.16)
  • Beta release target (1.17 or later)
  • Stable release target (1.18 or later)

Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement

/sig job

[kacole2]

/stage alpha
/milestone v1.16

Hi @fudali113, I'm the 1.16 Enhancement Lead. I've added this to the 1.16 Tracking Spreadsheet.

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.

[kacole2]

@lachie83 @justaugustus can we get a label added for sig/job? is that a SIG? I'm not familiar with that one.

[justaugustus]

@kacole2 -- I think this is supposed to be SIG Scheduling or SIG Apps.

@bsalamat @kubernetes/sig-scheduling-feature-requests @janetkuo @soltysh @kubernetes/sig-apps-misc -- can you confirm and relabel as necessary?
/sig scheduling apps

[fudali113]

@kacole2
this is k/k PR:
kubernetes/kubernetes#66105

[kacole2]

@fudali113 this is a reminder that Enhancement Freeze is tomorrow and this keep needs to be merged by EOD. If not, it will be removed from the milestone. Thanks

[kacole2]

@fudali113

Enhancement Freeze has passed for 1.16. The KEP at #1072 was never merged and now this is being removed from the 1.16 milestone. If this would like to be re-added, please file an exception and it will require approval from the release lead.

/milestone clear

[fudali113]

ok , can i add this enhancement to 1.17 ?

btw , why not reviewers to review my #1072 ?

@kacole2

[mrbobbytables]

Hey there @fudali113 -- 1.17 Enhancements lead here. I wanted to check in and see if you think this Enhancement will be graduating to alpha/beta/stable in 1.17?

Just a reminder that for it to be accepted -- the KEP must be merged, in an implementable state and have both a test plan and graduation criteria defined before the Enhancement Freeze.

The current release schedule is:

• Monday, September 23 - Release Cycle Begins
• Tuesday, October 15, EOD PST - Enhancements Freeze
• Thursday, November 14, EOD PST - Code Freeze
• Tuesday, November 19 - Docs must be completed and reviewed
• Monday, December 9 - Kubernetes 1.17.0 Released

If you do, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

[jeremyrickard]

Hey there @fudali113, 1.17 enhancements team checking in again 👋. We're quickly approaching the enhancements freeze (EOD PT, October 15th). As a reminder, your KEP needs to be merged by Oct 15th to make it into the 1.17 release, with the following criteria satisfied:

• KEP must be in the implementable state

[mrbobbytables]

@fudali113 -- Unfortunately the deadline for the 1.17 Enhancement freeze has passed and the KEP still isn't merged. For now this is being removed from the milestone and 1.17 tracking sheet. If there is a need to get this in, please file an enhancement exception.

/milestone clear

[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

[palnabarun]

/remove-lifecycle stale

[johnbelamaric]

Hey there @fudali113 -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to alpha in 1.18?

The current release schedule is:

Monday, January 6th - Release Cycle Begins
Tuesday, January 28th EOD PST - Enhancements Freeze
Thursday, March 5th, EOD PST - Code Freeze
Monday, March 16th - Docs must be completed and reviewed
Tuesday, March 24th - Kubernetes 1.18.0 Released

To be included in the release, this enhancement must have a merged KEP in the implementable status. The KEP must also have graduation criteria and a Test Plan defined.

If you would like to include this enhancement, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancements
Thanks!

[soltysh]

@johnbelamaric I don't think any work will happen for 1.18 here.

[fudali113]

Hey there @fudali113 -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to alpha in 1.18?

The current release schedule is:

Monday, January 6th - Release Cycle Begins
Tuesday, January 28th EOD PST - Enhancements Freeze
Thursday, March 5th, EOD PST - Code Freeze
Monday, March 16th - Docs must be completed and reviewed
Tuesday, March 24th - Kubernetes 1.18.0 Released

To be included in the release, this enhancement must have a merged KEP in the implementable status. The KEP must also have graduation criteria and a Test Plan defined.

If you would like to include this enhancement, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancements
Thanks!

sorry，i just saw this comment now；so i miss this Enhancement alpha in 1.18 ; What can i do to continue this Enhancement ? @mattfarina

[johnbelamaric]

@fudali113 I will target it to 1.19 and we will start bugging you about that soon!!

/milestone v1.19

[fudali113]

@fudali113 I will target it to 1.19 and we will start bugging you about that soon!!

/milestone v1.19

ok，i'm ready and i will reopen k/k pr @johnbelamaric

[fudali113]

@fudali113 I will target it to 1.19 and we will start bugging you about that soon!!

/milestone v1.19

hi, i'm reopen k/k pr kubernetes/kubernetes#89640
Let's discuss it together

@johnbelamaric

[harshanarayana]

Hey there @fudali113, 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19?

In order to have this part of the release:

1. The KEP PR must be merged in an implementable state
2. The KEP must have test plans
3. The KEP must have graduation criteria.

The current release schedule is:

• Monday, April 13: Week 1 - Release cycle begins
• Tuesday, May 19: Week 6 - Enhancements Freeze
• Thursday, June 25: Week 11 - Code Freeze
• Thursday, July 9: Week 14 - Docs must be completed and reviewed
• Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

[harshanarayana]

Hey @fudali113, I'm following up on my previous update on this Enhancement being part of the v1.19 release.

Do you happen to have any update on the possiblity of this being included in the release v1.19?

Thanks again for your time and contributions. 🖖

[harshanarayana]

Hey @fudali113 / @janetkuo / @soltysh, I'm following up on my previous update on this Enhancement being part of the v1.19 release.

Do you happen to have any update on the possiblity of this being included in the release v1.19?

Thanks again for your time and contributions. 🖖

[harshanarayana]

Hey @fudali113 / @janetkuo / @soltysh, any plans for the Enhancements to be included in v1.19? Please let me know so that I can update the tracking sheet to show the inclusion state.

Enhancements freeze is on May 19

Note that recently the KEP format has changed. Additionally, #1620 merged recently, adding production readiness review questions to the KEP template.
Please take this opportunity to reformat your KEP and also answer the questions added to the template in that PR.

Thanks,
🖖

[harshanarayana]

Hey @fudali113 / @janetkuo / @soltysh, Unfortunately the deadline for the 1.19 Enhancement freeze has passed and the KEP for it is still in flight. For now this is being removed from the milestone and 1.19 tracking sheet. If there is a need to get this in, please file an enhancement exception.

[palnabarun]

/milestone clear

[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

[palnabarun]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @fudali113

Enhancements Lead here. Any plans for this in 1.20?

Thanks!
Kirsten

[Huang-Wei]

/remove-sig scheduling

[kikisdeliveryservice]

Hi @fudali113

Following up: 1.20 Enhancements Freeze is October 6th. Could you let us know if you have plans for 1.20? I don't currently see a KEP attached to this issues.

To be included in the milestone:
The KEP must be merged in an implementable state
The KEP must have test plans (missing)
The KEP must have graduation criteria (missing)

As a note, the format of KEPs has changed. If you could please update and include the missing sections noted above that would be great. See for ref https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template

Thanks,
Kirsten

[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

[soltysh]

This is currently being tracked in #2214
/close

[k8s-ci-robot]

@soltysh: Closing this issue.

In response to this:

This is currently being tracked in #2214
/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.