Skip to content
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

Add Azure support to cluster-autoscaler #514

Closed
feiskyer opened this issue Nov 16, 2017 · 16 comments
Closed

Add Azure support to cluster-autoscaler #514

feiskyer opened this issue Nov 16, 2017 · 16 comments
Assignees
Labels
area/provider/azure Issues or PRs related to azure provider kind/feature Categorizes issue or PR as related to a new feature. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Milestone

Comments

@feiskyer
Copy link
Member

Feature Description

  • One-line feature description (can be used as a release note): Add Azure support to cluster-autoscaler.
  • Primary contact (assignee): @feiskyer
  • Responsible SIGs: sig-autoscaling
  • Design proposal link (community repo): Add Azure support autoscaler#449
  • Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @mwielgus @brendandburns
  • Approver (likely from SIG/area to which feature belongs): @mwielgus @MaciekPytel
  • Feature target (which target equals to which milestone):
    • Alpha release target v1.10
    • Beta release target v1.11
    • Stable release target v1.12
@feiskyer feiskyer self-assigned this Nov 16, 2017
@feiskyer feiskyer added this to the next-milestone milestone Nov 16, 2017
@feiskyer feiskyer added sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. area/provider/azure Issues or PRs related to azure provider labels Nov 16, 2017
@idvoretskyi
Copy link
Member

@feiskyer @kubernetes/sig-autoscaling-feature-requests still on track for 1.10?

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 15, 2018
@feiskyer feiskyer modified the milestones: next-milestone, v1.10 Jan 15, 2018
@feiskyer
Copy link
Member Author

@idvoretskyi Yep, working in progress. Setting milestone back to v1.10.

@idvoretskyi idvoretskyi added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Jan 22, 2018
@idvoretskyi idvoretskyi added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jan 29, 2018
@feiskyer feiskyer modified the milestones: v1.10, v1.11 Mar 27, 2018
@justaugustus
Copy link
Member

@feiskyer
Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

  • Description
  • Milestone
  • Assignee(s)
  • Labels:
    • stage/{alpha,beta,stable}
    • sig/*
    • kind/feature

cc @idvoretskyi

@feiskyer
Copy link
Member Author

/stage beta

@feiskyer feiskyer added stage/beta Denotes an issue tracking an enhancement targeted for Beta status and removed stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels Apr 17, 2018
@justaugustus
Copy link
Member

Thanks for the update, @feiskyer!

@mdlinville
Copy link

@feiskyer please fill out the appropriate line item of the
1.11 feature tracking spreadsheet
and open a placeholder docs PR against the
release-1.11 branch
by 5/25/2018 (tomorrow as I write this) if new docs or docs changes are
needed and a relevant PR has not yet been opened.

@justaugustus
Copy link
Member

@feiskyer -- We're doing one more sweep of the 1.11 Features tracking spreadsheet.
Would you mind filling in any incomplete / blank fields for this feature's line item?

@feiskyer
Copy link
Member Author

feiskyer commented Jun 5, 2018

@justaugustus Already updated. Thanks

@feiskyer feiskyer modified the milestones: v1.11, v1.12 Jul 11, 2018
@justaugustus justaugustus removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jul 18, 2018
@justaugustus
Copy link
Member

@feiskyer --

It looks like this feature is currently in the Kubernetes 1.12 Milestone.

If that is still accurate, please ensure that this issue is up-to-date with ALL of the following information:

  • One-line feature description (can be used as a release note):
  • Primary contact (assignee):
  • Responsible SIGs:
  • Design proposal link (community repo):
  • 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):
  • Feature target (which target equals to which milestone):
    • Alpha release target (x.y)
    • Beta release target (x.y)
    • Stable release target (x.y)

Set the following:

  • Description
  • Assignee(s)
  • Labels:
    • stage/{alpha,beta,stable}
    • sig/*
    • kind/feature

Once this feature is appropriately updated, please explicitly ping @justaugustus, @kacole2, @robertsandoval, @rajendar38 to note that it is ready to be included in the Features Tracking Spreadsheet for Kubernetes 1.12.


Please note that the Features Freeze is July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.

In addition, please be aware of the following relevant deadlines:

  • Docs deadline (open placeholder PRs): 8/21
  • Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.

Happy shipping!

@justaugustus
Copy link
Member

/remove-stage beta
/stage stable

@k8s-ci-robot k8s-ci-robot added stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status and removed stage/beta Denotes an issue tracking an enhancement targeted for Beta status labels Jul 29, 2018
@justaugustus justaugustus added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jul 29, 2018
@zparnold
Copy link
Member

Hey there! @feiskyer 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?

justaugustus pushed a commit to justaugustus/enhancements that referenced this issue Sep 3, 2018
@justaugustus
Copy link
Member

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

@feiskyer
Copy link
Member Author

feiskyer commented Sep 6, 2018

@justaugustus Yep, still tracked for v1.12 and docs are added in kubernetes/autoscaler repo.

@justaugustus
Copy link
Member

Thanks for the update!

@feiskyer
Copy link
Member Author

GA and done now. Let's close it.

/close

@k8s-ci-robot
Copy link
Contributor

@feiskyer: Closing this issue.

In response to this:

GA and done now. Let's close it.

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

@kacole2 kacole2 removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Oct 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/provider/azure Issues or PRs related to azure provider kind/feature Categorizes issue or PR as related to a new feature. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Projects
None yet
Development

No branches or pull requests

7 participants