Federated Pod AutoScaler feature

[dhilipkumars]

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

[fgrzadkowski]

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

[DirectXMan12]

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

[mwielgus]

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

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

[kevin-wangzefeng]

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

[idvoretskyi]

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

[irfanurrehman]

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

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

[idvoretskyi]

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

[irfanurrehman]

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

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

[ghost]

kubernetes/website#5487

…

On Fri, Sep 15, 2017 at 12:00 PM, Jaice Singer DuMars < ***@***.***> wrote: @irfanurrehman <https://github.com/irfanurrehman> any update on docs? PR is due today. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#257 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJ6NAXPUj0E2vSXEgpTFefPmvg3cT4c5ks5sisk-gaJpZM4NE-Ir> .

-- Quinton Hoole quinton@hoole.biz

[jdumars]

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

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

[fejta-bot]

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

[fejta-bot]

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