Higher level HPA Preferences API and controller about kubefed HOT 13 CLOSED

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

from kubefed.

what is the status of this feature? Is there a way to achieve the v1 ""federation.kubernetes.io/hpa-preferences" annotation behavior in current Federation version?

from kubefed.

@a0144 this was put out on the backlog to be explored if an user requirement comes up, or interested user/users show up with a relevant use case. Do you have a use case which can substantiate the need of this feature?

from kubefed.

@irfanurrehman yes, I have two on-prem kubeadm clusters, where under normal circumstances only one is used to run the workloads. The pods for each service are scaled up by HPA locally in cluster1 as long as there are enough resources to do so. If not, they should be scaled into the second cluster. If you have some ideas of other ways to make it work I'd be really glad to get some tips.

from kubefed.

@a0144. I am not aware of any alternative behaviours to make this work as of now. I would recommend you join the kubefed work group sync tomorrow @ 7:30 PT at https://zoom.us/my/k8s.mc to talk about your use case. I can add an agenda item if you confirm your presence.

from kubefed.

@irfanurrehman Thanks for the info. I'll join the meeting tomorrow

from kubefed.

Hi @irfanurrehman @a0144. Do you have any news on this, like design proposals?

from kubefed.

@sancyx this issue is waiting for more evidence of the utility. If you have a reasonable use case then we can talk further about it. Talking about it at the community meeting as mentioned here is a good first step.

from kubefed.

/remove-lifecycle stale

from kubefed.

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

from kubefed.

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

from kubefed.

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

from kubefed.

@fejta-bot: Closing this issue.

from kubefed.