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.

Sign up for GitHub

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

Jump to bottom

Federated Pod AutoScaler feature #257

Closed
dhilipkumars opened this issue Apr 22, 2017 · 16 comments
Closed

Federated Pod AutoScaler feature #257

dhilipkumars opened this issue Apr 22, 2017 · 16 comments
Assignees
@irfanurrehman
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status
Projects
Kubernetes 1.7 features
Milestone
v1.8

Comments

@dhilipkumars
Copy link

dhilipkumars commented Apr 22, 2017 •
edited by kevin-wangzefeng

Feature Description

  • One-line feature description (can be used as a release note): Horizontal Workload Scaling across Federation
  • Primary contact (assignee): @irfanurrehman
  • Responsible SIGs: @kubernetes/sig-autoscaling-feature-requests @kubernetes/sig-federation-feature-requests
  • Design proposal link (community repo): [Federation] Federated hpa design community#593
  • Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @quinton-hoole @madhusudancs
  • Approver (likely from SIG/area to which feature belongs): @quinton-hoole
  • Feature target (which target equals to which milestone):
    • Alpha release target (1.7): Initial implementation of the Desing along with respective API
@ghost ghost assigned irfanurrehman Apr 24, 2017
@ghost ghost added the sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. label Apr 24, 2017
@ghost ghost added this to the v1.7 milestone Apr 24, 2017
@ghost ghost added sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels Apr 24, 2017
@fgrzadkowski
Copy link

@kubernetes/sig-autoscaling-feature-requests @mwielgus @DirectXMan12

@DirectXMan12
Copy link
Contributor

This really needs to be discussed further in SIG autoscaling, IMO.

@mwielgus
Copy link
Contributor

@DirectXMan12 - I did a couple review iterations of the draft proposal. It makes sense but I also agree that it should be more broadly discussed at SIG autoscaling.

@idvoretskyi
Copy link
Member

@irfanurrehman I've updated the feature description to fit the new template. Please, fill the empty fields in the new template (their actual state was unclear).

@idvoretskyi idvoretskyi added this to Action required in Kubernetes 1.7 features May 3, 2017
@kevin-wangzefeng
Copy link
Member

@irfanurrehman I've updated the feature description according to the status AFAIK, correct me if anything is inaccurate.

@csbell csbell modified the milestones: v1.7, next-milestone Jun 5, 2017
@idvoretskyi idvoretskyi moved this from Action required to In Progress in Kubernetes 1.7 features Jun 15, 2017
@ghost ghost modified the milestones: 1.8, next-milestone Jul 13, 2017
@idvoretskyi
Copy link
Member

@quinton-hoole @irfanurrehman milestone has been updated to 1.8. Which stage will this feature target for 1.8?

@idvoretskyi idvoretskyi added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 25, 2017
@irfanurrehman
Copy link

@idvoretskyi Do you mean to ask the timeline by stage? (Probably I don't really understand the k8s release stages well).
The feature as a whole might be completed soon.
The design is already approved kubernetes/community#593.
The api is merged quite some time back kubernetes/kubernetes#38976.
The controller pr already has gone under couple of rounds of review kubernetes/kubernetes#45993.
Things like documenting the feature will also soon follow.

@ghost
Copy link

ghost commented Jul 25, 2017

@idvoretskyi @irfanurrehman stage/alpha, as per the label, still applies.

@irfanurrehman irfanurrehman mentioned this issue Jul 26, 2017
Closed
@idvoretskyi
Copy link
Member

@irfanurrehman @kubernetes/sig-federation-feature-requests any updates for 1.8? Is this feature still on track for the release?

@irfanurrehman
Copy link

irfanurrehman commented Sep 5, 2017 •
edited

@idvoretskyi Yes the feature is partially merged (controller implemented in kubernetes/kubernetes#45993) and usable on master. Some additional stuff is needed, for the feature to be complete for alpha, which is in kubernetes/kubernetes#49950 (which is already lgtmed, waiting for an approve).

@jdumars
Copy link
Member

jdumars commented Sep 15, 2017

@irfanurrehman any update on docs? PR is due today.

@ghost
Copy link

ghost commented Sep 15, 2017 via email

@jdumars
Copy link
Member

jdumars commented Sep 18, 2017

@quinton-hoole thanks!!

This was referenced Oct 27, 2017
Closed
Closed
@fejta-bot
Copy link

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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 6, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 9, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

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

@irfanurrehman irfanurrehman

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status
Projects
No open projects
Kubernetes 1.7 features
In Progress
Milestone
v1.8
Development

No branches or pull requests