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

Introduce new knob for configuring burst capacity. #4433

Merged
merged 2 commits into from
Jun 25, 2019

Conversation

vagababov
Copy link
Contributor

Introduce the new config-map setting for the target burst capacity.
For the starters it is a global setting, but we probably should at some point permi
per service overrides as annotations (;-)).

/lint

For #1846 #1409

Proposed Changes

  • new config value to configure burst capacity
  • tests

/assign @markusthoemmes @mattmoor

Introduce the new config-map setting for the target burst capacity.
For the starters it is a global setting, but we probably should at some point permi
per service overrides as annotations (;-)).

Default of 0.
@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Jun 19, 2019
@knative-prow-robot knative-prow-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jun 19, 2019
Copy link
Contributor

@knative-prow-robot knative-prow-robot left a comment

Choose a reason for hiding this comment

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

@vagababov: 0 warnings.

In response to this:

Introduce the new config-map setting for the target burst capacity.
For the starters it is a global setting, but we probably should at some point permi
per service overrides as annotations (;-)).

/lint

For #1846 #1409

Proposed Changes

  • new config value to configure burst capacity
  • tests

/assign @markusthoemmes @mattmoor

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.

@knative-metrics-robot
Copy link

The following is the coverage report on pkg/.
Say /test pull-knative-serving-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/autoscaler/config.go 96.0% 92.6% -3.4

@greghaynes
Copy link
Contributor

/lgtm

With stuff like this where were adding a config option and docs do we have a way to make sure users arent given this before it actually works? At a minimum we shouldn't merge this until after 0.7 I think.

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 20, 2019
@greghaynes
Copy link
Contributor

/hold

due to what I asked above re: not merging until 0.7

@knative-prow-robot knative-prow-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 20, 2019
@vagababov
Copy link
Contributor Author

Since it's not working ordering doesn't really matter. But we can stack them all for Tuesday.
I'll let @mattmoor decide since he's in charge of the release cutting :-)

@vagababov
Copy link
Contributor Author

/retest

@knative-prow-robot knative-prow-robot removed the lgtm Indicates that a PR is ready to be merged. label Jun 24, 2019
@mattmoor
Copy link
Member

/lgtm

Will approve post-cut tomorrow.

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 25, 2019
@mattmoor
Copy link
Member

/approve

@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mattmoor, vagababov

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

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 25, 2019
@mattmoor
Copy link
Member

/hold cancel

@knative-prow-robot knative-prow-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 25, 2019
@knative-prow-robot knative-prow-robot merged commit dac2cff into knative:master Jun 25, 2019
hohaichi pushed a commit to hohaichi/serving that referenced this pull request Jun 25, 2019
Introduce the new config-map setting for the target burst capacity.
For the starters it is a global setting, but we probably should at some point permi
per service overrides as annotations (;-)).

Default of 0.
@vagababov vagababov deleted the burst01 branch September 20, 2019 16:14
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. area/autoscale cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants