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

Scheduler checks feasibility and scores a subset of all cluster nodes #593

Open
bsalamat opened this Issue Jul 25, 2018 · 13 comments

Comments

Projects
None yet
8 participants
@bsalamat
Contributor

bsalamat commented Jul 25, 2018

Feature Description

  • One-line feature description (can be used as a release note): Scheduler checks feasibility and scores a subset of all cluster nodes.
  • Primary contact (assignee): @bsalamat
  • Responsible SIGs: scheduling
  • Design proposal link (community repo): kubernetes/kubernetes/issues/66627
  • 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:
  • Approver (likely from SIG/area to which feature belongs): @k82cn
  • Feature target (which target equals to which milestone):1.12
    • Alpha release target (x.y)1.12
    • Beta release target (x.y)1.13
    • Stable release target (x.y) 1.14

@bsalamat bsalamat self-assigned this Jul 25, 2018

@bsalamat bsalamat added this to the v1.12 milestone Jul 25, 2018

@justaugustus

This comment has been minimized.

Member

justaugustus commented Jul 26, 2018

Thanks for the update! This has been added to the 1.12 Tracking sheet.

@zparnold

This comment has been minimized.

Member

zparnold commented Aug 20, 2018

Hey there! @bsalamat I'm the wrangler for the Docs this release. Is there any chance I could have you open up a docs PR against the release-1.12 branch as a placeholder? That gives us more confidence in the feature shipping in this release and gives me something to work with when we start doing reviews/edits. Thanks! If this feature does not require docs, could you please update the features tracking spreadsheet to reflect it?

@bsalamat

This comment has been minimized.

Contributor

bsalamat commented Aug 22, 2018

@zparnold Here is the PR for the doc 👆

@zparnold

This comment has been minimized.

Member

zparnold commented Aug 25, 2018

Thanks!

@justaugustus

This comment has been minimized.

Member

justaugustus commented Sep 5, 2018

@bsalamat --
Any update on docs status for this feature? Are we still planning to land it for 1.12?
At this point, code freeze is upon us, and docs are due on 9/7 (2 days).
If we don't here anything back regarding this feature ASAP, we'll need to remove it from the milestone.

cc: @zparnold @jimangel @tfogo

@bsalamat

This comment has been minimized.

Contributor

bsalamat commented Sep 8, 2018

@justaugustus this feature has been merged a while ago. The document has been pending review for a while.

@justaugustus

This comment has been minimized.

Member

justaugustus commented Sep 11, 2018

@bsalamat -- please follow-up on the docs PR. We need to get this merged ASAP.

@ameukam

This comment has been minimized.

Contributor

ameukam commented Oct 5, 2018

Hi folks,
Kubernetes 1.13 is going to be a 'stable' release since the cycle is only 10 weeks. We encourage no big alpha features and only consider adding this feature if you have a high level of confidence it will make code slush by 11/09. Are there plans for this enhancement to graduate to alpha/beta/stable within the 1.13 release cycle? If not, can you please remove it from the 1.12 milestone or add it to 1.13?

We are also now encouraging that every new enhancement aligns with a KEP. If a KEP has been created, please link to it in the original post. Please take the opportunity to develop a KEP.

@kacole2

This comment has been minimized.

Contributor

kacole2 commented Oct 8, 2018

/milestone v1.13
/stage beta

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.12, v1.13 Oct 8, 2018

@AishSundar

This comment has been minimized.

AishSundar commented Oct 17, 2018

@bsalamat what work is left for this to land in Beta in 1.13? Is there a list of pending PRs we are tracking for this?

@bsalamat

This comment has been minimized.

Contributor

bsalamat commented Oct 17, 2018

Nothing is left to be done in 1.13 to move this to beta. It is just our guarantees to support this feature that changes in 1.13. This feature is already landed in 1.12.

@tfogo

This comment has been minimized.

Member

tfogo commented Nov 3, 2018

Hi @bsalamat, will there be any updates to the docs necessary for 1.13? The deadline for placeholder PRs for the 1.13 release is November 8. So it's important to make a docs PR as soon as possible if needed.

@bsalamat

This comment has been minimized.

Contributor

bsalamat commented Nov 6, 2018

@tfogo Thanks for the reminder. There is no need for updating documents in 1.13.

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