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

Remove the scale-to-zero checking in conformance. #13025

Merged
merged 1 commit into from
Jun 13, 2022

Conversation

mattmoor
Copy link
Member

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

API conformance no longer checks for scaling to zero in the presence of runtime probes

@knative-prow knative-prow bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. area/test-and-release It flags unit/e2e/conformance/perf test issues for product features labels Jun 12, 2022
@codecov
Copy link

codecov bot commented Jun 12, 2022

Codecov Report

Merging #13025 (b064aae) into main (2f7b6db) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            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     
Impacted Files Coverage Δ
pkg/reconciler/configuration/configuration.go 83.67% <0.00%> (-1.54%) ⬇️
pkg/activator/net/revision_backends.go 92.19% <0.00%> (-0.58%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2f7b6db...b064aae. Read the comment docs.

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.
@knative-prow knative-prow bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jun 12, 2022
@mattmoor
Copy link
Member Author

/cc @dprotaso
/assign @dprotaso

Copy link
Contributor

@psschwei psschwei left a comment

Choose a reason for hiding this comment

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

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Jun 13, 2022
@knative-prow
Copy link

knative-prow bot commented Jun 13, 2022

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 13, 2022
@knative-prow knative-prow bot merged commit d54ad4c into knative:main Jun 13, 2022
@mattmoor mattmoor deleted the remove-scale-to-zero-check branch June 13, 2022 14:40
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/test-and-release It flags unit/e2e/conformance/perf test issues for product features 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.

3 participants