Skip to content

[RELEASE 0.13] Backport fixes to minScale behavior.#7272

Merged
knative-prow-robot merged 4 commits intoknative:release-0.13from
markusthoemmes:backport-minscale-0.13
Mar 17, 2020
Merged

[RELEASE 0.13] Backport fixes to minScale behavior.#7272
knative-prow-robot merged 4 commits intoknative:release-0.13from
markusthoemmes:backport-minscale-0.13

Conversation

@markusthoemmes
Copy link
Copy Markdown
Contributor

Fixes for #6733 to be backported onto 0.13.

Release Note

Fixes a bug where a revision would be scaled down to 0 even if it has minScale applied to it.

/assign @mattmoor

tanzeeb and others added 4 commits March 16, 2020 19:51
* Test minScale during update to configuration

* Add route label to LatestCreatedRevision

* Use impl.Enqueue instead of tracker.OnChanged in labeler reconciler

* Update minscale readiness e2e test

* faster polling (250 ms)
* more descriptive error for ensureDesiredScale
* inlined latestCreatedRevisionName check

* Enqueue route instead of config in labeler reconciler

* Only label configurations of RunLatest traffic targets

* Label configuration if it or it's revision is in a route

* Only pull config for runLatest in labeler
* Some cleanups in the e2e test

* Some cleanups in the e2e test

* fix nit
The only error returned from the function is when we fail to actually verify the scale.
So return boolean instead.
* Test minscale stability when configuration is created

* Check both .spec.traffic and .status.traffic for resources to label

* Inline condition

* Inline owner reference check
@googlebot
Copy link
Copy Markdown

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added the cla: no Indicates the PR's author has not signed the CLA. label Mar 16, 2020
@knative-prow-robot knative-prow-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. area/API API objects and controllers labels Mar 16, 2020
Copy link
Copy Markdown
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.

Details

In response to this:

Fixes for #6733 to be backported onto 0.13.

Release Note

Fixes a bug where a revision would be scaled down to 0 even if it has minScale applied to it.

/assign @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-prow-robot knative-prow-robot added the area/test-and-release It flags unit/e2e/conformance/perf test issues for product features label Mar 16, 2020
@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 16, 2020
@markusthoemmes
Copy link
Copy Markdown
Contributor Author

@vagababov @tanzeeb please leave your consent if you agree with this backport.

@mattmoor
Copy link
Copy Markdown
Member

The fix portion of this is relatively contained and has had a fair number of eyeballs on it at HEAD.

/lgtm
/approve

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 16, 2020
@knative-prow-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

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

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@tanzeeb
Copy link
Copy Markdown
Contributor

tanzeeb commented Mar 16, 2020

@googlebot I consent.

@vagababov
Copy link
Copy Markdown
Contributor

@googlebot I consent

@googlebot
Copy link
Copy Markdown

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: yes Indicates the PR's author has signed the CLA. and removed cla: no Indicates the PR's author has not signed the CLA. labels Mar 17, 2020
@knative-prow-robot knative-prow-robot merged commit 0795709 into knative:release-0.13 Mar 17, 2020
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/test-and-release It flags unit/e2e/conformance/perf test issues for product features cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants