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

Make sure target annotations can exceed the configured default values. #5991

Merged
merged 1 commit into from
Nov 11, 2019

Conversation

markusthoemmes
Copy link
Contributor

Fixes #5975

Proposed Changes

Neither RPS nor concurrency based revisions can currently specify a scaling target that is higher than their respective default values. This fixes that.

Release Note

Concurrency and RPS can now be configured a higher target than their respective default values.

Neither RPS nor concurrency based revisions can currently specify a scaling target that is higher than their respective default values. This fixes that.
@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Nov 11, 2019
@knative-prow-robot knative-prow-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Nov 11, 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.

@markusthoemmes: 0 warnings.

In response to this:

Fixes #5975

Proposed Changes

Neither RPS nor concurrency based revisions can currently specify a scaling target that is higher than their respective default values. This fixes that.

Release Note

Concurrency and RPS can now be configured a higher target than their respective default values.

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-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: markusthoemmes

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. area/API API objects and controllers area/autoscale labels Nov 11, 2019
@markusthoemmes
Copy link
Contributor Author

/assign @vagababov

@markusthoemmes
Copy link
Contributor Author

/assign @yanweiguo

Copy link
Contributor

@vagababov vagababov left a comment

Choose a reason for hiding this comment

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

/lgtm

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

/lgtm

@knative-prow-robot knative-prow-robot merged commit 2c5a7da into knative:master Nov 11, 2019
Copy link

@andyyin andyyin left a comment

Choose a reason for hiding this comment

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

https://github.com/markusthoemmes/knative-serving/blob/6dc21bc497ebc3a057b99b9b685f564170558b5c/pkg/reconciler/autoscaling/resources/target.go#L51

But here only solve the problem of concurrency, how to deal with RPS?
I mean the current value (total and tu) of RPS is from autoscaler.Config. This configuration is a global configuration. All Revisons are the same value. How do I set different values ​​for different Revision settings?

@yanweiguo
Copy link
Contributor

https://github.com/markusthoemmes/knative-serving/blob/6dc21bc497ebc3a057b99b9b685f564170558b5c/pkg/reconciler/autoscaling/resources/target.go#L51

But here only solve the problem of concurrency, how to deal with RPS?
I mean the current value (total and tu) of RPS is from autoscaler.Config. This configuration is a global configuration. All Revisons are the same value. How do I set different values ​​for different Revision settings?

For PRS:

  1. Use default first: https://github.com/markusthoemmes/knative-serving/blob/6dc21bc497ebc3a057b99b9b685f564170558b5c/pkg/reconciler/autoscaling/resources/target.go#L36
  2. If annotation is there, use annotation: https://github.com/markusthoemmes/knative-serving/blob/6dc21bc497ebc3a057b99b9b685f564170558b5c/pkg/reconciler/autoscaling/resources/target.go#L50

@andyyin
Copy link

andyyin commented Nov 12, 2019

https://github.com/markusthoemmes/knative-serving/blob/6dc21bc497ebc3a057b99b9b685f564170558b5c/pkg/reconciler/autoscaling/resources/target.go#L51
But here only solve the problem of concurrency, how to deal with RPS?
I mean the current value (total and tu) of RPS is from autoscaler.Config. This configuration is a global configuration. All Revisons are the same value. How do I set different values ​​for different Revision settings?

For PRS:

  1. Use default first: https://github.com/markusthoemmes/knative-serving/blob/6dc21bc497ebc3a057b99b9b685f564170558b5c/pkg/reconciler/autoscaling/resources/target.go#L36
  2. If annotation is there, use annotation: https://github.com/markusthoemmes/knative-serving/blob/6dc21bc497ebc3a057b99b9b685f564170558b5c/pkg/reconciler/autoscaling/resources/target.go#L50

I see, thank you

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/API API objects and controllers 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.

How different PodAutoScaler configure RPS in Autoscale
6 participants