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

Enable GKE node-pool autoscaling options #1273

Merged
merged 1 commit into from Jul 31, 2018

Conversation

richardsliu
Copy link
Contributor

@richardsliu richardsliu commented Jul 27, 2018

This change is Reviewable

@richardsliu
Copy link
Contributor Author

/assign @ankushagarwal
/assign @jlewi

@richardsliu
Copy link
Contributor Author

/retest

1 similar comment
@richardsliu
Copy link
Contributor Author

/retest

@@ -38,6 +38,13 @@ check_install uuidgen

PRIVATE_CLUSTER=${PRIVATE_CLUSTER:-false}

# GKE autoscale parameters
ENABLE_AUTOSCALE=${ENABLE_AUTOSCALE:-false}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't want to expose options in multiple places. The single source of truth should be the K8s deployment configs.
If people want to change the options they should modify those YAMl files. They can run deploy.sh once and not setup the cluster (by setting setup) false to create the configs and then run it again to actually deploy it.


# Update the cluster if autoscaling is desired.
if ${ENABLE_AUTOSCALE}; then
gcloud container clusters update ${DEPLOYMENT_NAME} --enable-autoscaling --min-nodes ${DEFAULT_MIN_NODES} --max-nodes ${DEFAULT_MAX_NODES} --zone ${ZONE} --node-pool default-pool
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We want all configuration to be declarative. Can we add this to the CPU & GPU node pools respectively
https://github.com/kubeflow/kubeflow/blob/master/scripts/gke/deployment_manager_configs/cluster.jinja#L116

@richardsliu
Copy link
Contributor Author

Done.

@jlewi jlewi changed the title Enable GKE autoscaling options Enable GKE node-pool autoscaling options Jul 30, 2018
@jlewi
Copy link
Contributor

jlewi commented Jul 30, 2018

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jlewi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jlewi
Copy link
Contributor

jlewi commented Jul 30, 2018

@richardsliu I think you want to rebase off the latest master to fix the tests.

@richardsliu
Copy link
Contributor Author

/retest

1 similar comment
@richardsliu
Copy link
Contributor Author

/retest

Move autoscale configurations to jinja and yaml files
@richardsliu
Copy link
Contributor Author

/retest

@richardsliu
Copy link
Contributor Author

/lgtm

@k8s-ci-robot
Copy link
Contributor

@richardsliu: you cannot LGTM your own PR.

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ankushagarwal
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot merged commit db91925 into kubeflow:master Jul 31, 2018
@richardsliu
Copy link
Contributor Author

fixes #1033

@richardsliu richardsliu deleted the autoscale branch July 31, 2018 00:45
saffaalvi pushed a commit to StatCan/kubeflow that referenced this pull request Feb 11, 2021
Move autoscale configurations to jinja and yaml files
yanniszark pushed a commit to arrikto/kubeflow that referenced this pull request Feb 15, 2021
* Add proposal for custom CRD in Trial Template

* Fix

* Modify doctoc

* Doc fixes

* Rename header

* Fixes

* Change doc

* Remove comma

* Fix Implementation
surajkota pushed a commit to surajkota/kubeflow that referenced this pull request Jun 13, 2022
…ubeflow#1273)

* image gcr.io/kubeflow-images-public/pytorch-operator:vmaster-gd596e904
* Image built from kubeflow/kubeflow@d596e904
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants