-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Remove the scale-to-zero checking in conformance. #13025
Remove the scale-to-zero checking in conformance. #13025
Conversation
Codecov Report
@@ Coverage Diff @@
## main #13025 +/- ##
==========================================
- Coverage 87.03% 87.00% -0.04%
==========================================
Files 197 197
Lines 14439 14439
==========================================
- Hits 12567 12562 -5
- Misses 1578 1582 +4
- Partials 294 295 +1
Continue to review full report at Codecov.
|
Conformance should be a measurement of the Knative API and runtime semantics, not the details of how those semantics are implemented. Scaling to zero is effectively a cost optimization, but should not be a requirement of a conforming implementation. For instance, if I were to set `min-scale: "1"` cluster-wide, I should still have a conformant implementation, since the key semantics of the API are still preserved.
2cc97c8
to
b064aae
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oked for removal in Slack discussion
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mattmoor, psschwei 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 |
Conformance should be a measurement of the Knative API and runtime semantics, not the details of how those semantics are implemented. Scaling to zero is effectively a cost optimization, but should not be a requirement of a
conforming implementation.
For instance, if I were to set
min-scale: "1"
cluster-wide, I should still have a conformant implementation, since the key semantics of the API are still preserved.Release Note