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.

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

Add support for a cluster pool auto scaler #159

Closed
bassam opened this issue Nov 23, 2018 · 3 comments
Closed

Add support for a cluster pool auto scaler #159

bassam opened this issue Nov 23, 2018 · 3 comments
Labels
roadmap Issues that have priority and are included in the roadmap, or are candidates to add to the roadmap

Comments

@bassam
Copy link
Member

bassam commented Nov 23, 2018

We should support a new controller (a cluster autoscaler) that can automatically create Kubernetes clusters on as needed basis, and remove any idle clusters.

The autoscaler would watch Workloads and look for ones that are unschedulable or have reached capacity/limits on existing clusters, and react by creating new Kubernetes clusters from defined pools. For example:

 apiVersion: compute.crossplane.io/v1alpha1
 kind: KubernetesClusterPool
 metadata:
   name: default-pool
   namespace: crossplane-system
 spec:
   minCluster: 1
   maxCluster: 10
   clusterSpec:
      clusterVersion: 1.10
      nodePools:
      - name: default
        machineType: n1-standard-1
        autoScale: true
        minNodes: 1
        maxNodes: 10
@erwbgy
Copy link

erwbgy commented May 25, 2019

This is a great idea, but the cluster autoscaler terminology could be confusing because the Kubernetes cluster autoscaler "is a tool that automatically adjusts the size of the Kubernetes cluster" so scales the nodes in an existing cluster, whereas this feature is about scaling clusters rather than nodes. Maybe change the title and description to _cluster pool autoscaler_to match the kind?

@jbw976 jbw976 changed the title Add support for a cluster auto scaler Add support for a cluster pool auto scaler May 28, 2019
@jbw976
Copy link
Member

jbw976 commented May 28, 2019

good suggestion @erwbgy! i updated the title to reflect that

@jbw976 jbw976 added the roadmap Issues that have priority and are included in the roadmap, or are candidates to add to the roadmap label Jun 10, 2019
@jbw976 jbw976 removed this from the v0.3 milestone Jun 10, 2019
@negz
Copy link
Member

negz commented Jul 8, 2021

I don't think this is especially relevant with where Crossplane is at today - we can reopen if and when we invest more in native or day two workload support.

@negz negz closed this as completed Jul 8, 2021
luebken pushed a commit to luebken/crossplane that referenced this issue Aug 3, 2021
Remove Crossplane prefix from name in app.yaml
plumbis added a commit to plumbis/crossplane that referenced this issue Oct 31, 2023
Updates the /docs redirect to always go to latest
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
roadmap Issues that have priority and are included in the roadmap, or are candidates to add to the roadmap
Projects
None yet
Development

No branches or pull requests

4 participants