Skip to content
This repository has been archived by the owner on Oct 10, 2023. It is now read-only.

Carvelize the autoscaler deployment being #2320

Open
4 of 10 tasks
saji-pivotal opened this issue May 5, 2022 · 0 comments
Open
4 of 10 tasks

Carvelize the autoscaler deployment being #2320

saji-pivotal opened this issue May 5, 2022 · 0 comments
Assignees
Labels
area/cli kind/feature Categorizes issue or PR as related to a new feature not-core-cli

Comments

@saji-pivotal
Copy link
Contributor

(This is used to request new product features)

Describe the feature request

  • As a user, I want autoscaler available as an optional package on the TKG cluster. There should be no regressions from previous editions of TKG
  • The user must have a choice to enable or disable autoscaler
  • If autoscaler is enabled, the TKG cluster must install the autoscaler package, and it must run with the parameters specified by the user
  • The tricky bit is that the autoscaler package must be installed on the management cluster only when we're in the process of installing a workload cluster. We do not need to install it otherwise

Describe alternatives you've considered

  • Installing the autoscaler package irrespective of the workload cluster being available. This is not feasible because we want to maintain a 1:1 relationship between autoscaler deployments and workload clusters

Affected product area (please put an X in all that apply)

  • APIs
  • Addons
  • CLI
  • Docs
  • IAM
  • Installation
  • Plugin
  • Security
  • Test and Release
  • User Experience

Additional context

@saji-pivotal saji-pivotal added kind/feature Categorizes issue or PR as related to a new feature needs-triage Indicates an issue or PR needs to be triaged labels May 5, 2022
@saji-pivotal saji-pivotal self-assigned this May 5, 2022
@saji-pivotal saji-pivotal added area/cli and removed needs-triage Indicates an issue or PR needs to be triaged labels May 5, 2022
@saji-pivotal saji-pivotal mentioned this issue May 5, 2022
3 tasks
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
area/cli kind/feature Categorizes issue or PR as related to a new feature not-core-cli
Projects
None yet
Development

No branches or pull requests

1 participant