Update values.yaml defaults to match real default values

[Niksko]

Conventionally, commented out values in the values.yaml file should match the default values for the commented out parameters. Some of the parameters here didn't match, so I've corrected them, as per the documented defaults in the FAQ.

It's likely worth discussing whether this section should either be supplemented to include all of the defaults, or whether it should just link to the documentation of the flags in the FAQ. However for now, the defaults listed match their real default values.

[k8s-ci-robot]

Welcome @Niksko!

It looks like this is your first PR to kubernetes/autoscaler 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/autoscaler has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[gjtempleton]

Hi, thanks for the PR!

As you mention, I think it's worth linking out to the CA's FAQ for the flags and their default values for any other flags that aren't already listed in the values file to minimise us having to keep the values file up to date.

[gjtempleton]

/assign

[Niksko]

Updated with a link to the FAQ section

[Niksko]

/retest

[k8s-ci-robot]

@Niksko: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[Niksko]

Hi, can somebody please re-run the integration tests for me. They seem to have failed due to Docker rate limiting:

docker: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit.

[gjtempleton]

/ok-to-test

[gjtempleton]

/retest

[gjtempleton]

/lgtm

I can't re-trigger the Travis build, however, you're not touching any of the code that would affect the Travis build so I'm happy enough to merge as is. I'll see if I can get someone who can retrigger it to do so.

/approve

[gjtempleton]

@Niksko The other option we have is you retriggering a Travis build by effectively pushing a new event to trigger it. Can you do a squash of your commits and force push that up? That should be enough to trigger a rebuild.

[gjtempleton]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gjtempleton, Niksko

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:

• charts/OWNERS [gjtempleton]

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