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

Allow to configure --scale-down-unneeded-time #37

Merged

Conversation

ingvagabund
Copy link
Member

It takes 10 minutes before a cluster is scalled down (default value of --scale-down-unneeded-time).
Allowing to override the option allows to decrease the time spend waiting
on scale down operation in both testing and development environment.

Also can help customer to scale down sooner.

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Feb 7, 2019
examples/clusterautoscaler.yaml Outdated Show resolved Hide resolved
It takes 10 minutes before a cluster is scalled down (default value of --scale-down-unneeded-time).
Allowing to override the option allows to decrease the time spend waiting
on scale down operation in both testing and development environment.

Also can help customer to scale down sooner.
@@ -96,6 +97,10 @@ func ScaleDownArgs(sd *v1alpha1.ScaleDownConfig) []string {
ScaleDownDelayAfterFailureArg.Value(sd.DelayAfterFailure),
}

if sd.UnneededTime != "" {
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's also add a unit test case that validates a config with/without this value.

Copy link
Contributor

Choose a reason for hiding this comment

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

We should actually probably add omitEmpty to all of the scale down argument fields in the resource, or even make them pointers. Then fix the Value() method here to return an empty string if it gets nil or an empty string. Not sure if we do that here or in a follow up.

Copy link
Contributor

Choose a reason for hiding this comment

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

I would vote in a follow-up.

@enxebre
Copy link
Member

enxebre commented Feb 7, 2019

/hold
please hold until pivot is done, we have no e2e tests here so we don't want to introduce any unnecessary risk

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 7, 2019
Copy link
Contributor

@bison bison left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 8, 2019
@enxebre enxebre removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 8, 2019
@enxebre
Copy link
Member

enxebre commented Feb 8, 2019

/approve

@ingvagabund ingvagabund added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 8, 2019
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: enxebre

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

@ingvagabund
Copy link
Member Author

/retest

1 similar comment
@ingvagabund
Copy link
Member Author

/retest

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 413f349 into openshift:master Feb 9, 2019
@ingvagabund ingvagabund deleted the scale-down-unneeded-time branch February 11, 2019 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants