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

Document scale annotations lifetime #3461

Merged
merged 8 commits into from
Mar 26, 2019

Conversation

yanweiguo
Copy link
Contributor

Fixes #2720.

@knative-prow-robot knative-prow-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. area/autoscale labels Mar 19, 2019
Copy link
Contributor

@markusthoemmes markusthoemmes left a comment

Choose a reason for hiding this comment

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

A few rewordings. Thanks @yanweiguo 🙂


**NOTE**: These annotations apply for the full lifetime of a `revision`.
Even when a `revision` is not referenced by any `route`, the minimal pod count
specified by `autoscaling.knative.dev/minScale` will still be provided. Non-routed
Copy link
Member

Choose a reason for hiding this comment

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

I know that @rgregg finds the current behavior unintuitive and wants minScale to only apply to routeable Revisions.
This is mechanically hard, and weakens the promise of minScale, but I can empathize with why he dislikes this. I'm wondering if/how we should change this wording to anticipate and reflect the possibility of a future where this semantic changes. WDYT?

If we don't already we should also document that these annotations are specific to these Autoscaler implementations and not subject to Conformance.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

From this comment, there's reasons to keep current behavior.

I added the description that these annotations are not subject to Conformance in case we make the change in future.

Copy link
Member

@mattmoor mattmoor left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

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

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Mar 25, 2019
@yanweiguo
Copy link
Contributor Author

/test pull-knative-serving-upgrade-tests

2 similar comments
@yanweiguo
Copy link
Contributor Author

/test pull-knative-serving-upgrade-tests

@yanweiguo
Copy link
Contributor Author

/test pull-knative-serving-upgrade-tests

@yanweiguo
Copy link
Contributor Author

/test pull-knative-serving-upgrade-tests

@knative-prow-robot knative-prow-robot merged commit 1fba58e into knative:master Mar 26, 2019
@yanweiguo yanweiguo deleted the update_doc_for_minscale branch July 16, 2019 19:45
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 lgtm Indicates that a PR is ready to be merged. 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