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

Fixed check in kubectl autoscale. #26162

Merged
merged 1 commit into from
May 31, 2016

Conversation

jszczepkowski
Copy link
Contributor

Fixed check in kubectl autoscale: cpu consumption can be higher than 100%.

Analytics

Fixed check in kubectl autoscale: cpu consumption can be higher than 100%. Fixes #25815.

Fixed check in kubectl autoscale: cpu consumption can be higher than 100%. Fixes kubernetes#25815.
@jszczepkowski
Copy link
Contributor Author

CC @mwielgus @piosz

@piosz
Copy link
Member

piosz commented May 24, 2016

cc @janetkuo

@k8s-github-robot k8s-github-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. release-note-label-needed labels May 24, 2016
if max < 1 || max < min {
errs = append(errs, fmt.Errorf("--max=MAXPODS is required, and must be at least 1 and --min=MINPODS"))
}
if cpu > 100 {
errs = append(errs, fmt.Errorf("CPU utilization (%%) cannot exceed 100"))
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we keep a warning in here, or just rely on the server-side warning proposed in #18294

Copy link
Contributor Author

Choose a reason for hiding this comment

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

AFAIK, there are no warning logged to output by kubectl. So, I didn't want to introduce them.

Copy link
Contributor

Choose a reason for hiding this comment

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

ACK

@DirectXMan12
Copy link
Contributor

LGTM 👍

@jszczepkowski jszczepkowski added release-note Denotes a PR that will be considered when it comes time to generate release notes. lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed release-note-label-needed labels May 31, 2016
@piosz piosz added this to the v1.3 milestone May 31, 2016
@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented May 31, 2016

GCE e2e build/test passed for commit 47a5c17.

@k8s-github-robot
Copy link

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit c805303 into kubernetes:master May 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. 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.

6 participants