Open toVersus opened 10 months ago
/balancer
cc @mwielgus
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
/area balancer
Which component are you using?:
Balancer
Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:
Since the HPA controller overwrites Balancer's
spec.replicas
, specifying it is mandatory, which means you have to update your manifests and apply changes each time the HPA controller changes the number of replicas for Balancer.Describe the solution you'd like.:
Change Balancer's replicas field to be optional. The default value is 1 unless
minReplicas
intargets
is specified. Otherwise, it will sum the values ofminReplicas
.Describe any alternative solutions you've considered.:
Update your manifests and apply changes each time the HPA controller changes the number of replicas for Balancer.
Additional context.:
xref: https://github.com/kubernetes/kubernetes/issues/121211