Skip to content

Conversation

@knative-prow-robot
Copy link
Contributor

@knative-prow-robot knative-prow-robot commented Nov 24, 2022

This is an automated cherry-pick of #13501

Scaling to zero now works when target-burst-capacity is zero.

The autoscaler sends a probe to detect the activator is in the data
path. This probe was inadvertently passed to the user container which
was preventing scale to 0.
@knative-prow knative-prow bot added area/autoscale area/networking area/test-and-release It flags unit/e2e/conformance/perf test issues for product features size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Nov 24, 2022
@codecov
Copy link

codecov bot commented Nov 24, 2022

Codecov Report

Base: 86.57% // Head: 86.53% // Decreases project coverage by -0.03% ⚠️

Coverage data is based on head (2636f88) compared to base (311dc7c).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@               Coverage Diff               @@
##           release-1.7   #13504      +/-   ##
===============================================
- Coverage        86.57%   86.53%   -0.04%     
===============================================
  Files              196      196              
  Lines            14515    14515              
===============================================
- Hits             12566    12561       -5     
- Misses            1651     1654       +3     
- Partials           298      300       +2     
Impacted Files Coverage Δ
pkg/queue/sharedmain/main.go 0.61% <0.00%> (ø)
pkg/reconciler/revision/background.go 90.90% <0.00%> (-1.82%) ⬇️
pkg/reconciler/configuration/configuration.go 83.67% <0.00%> (-1.54%) ⬇️
pkg/autoscaler/statserver/server.go 78.10% <0.00%> (+0.72%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@dprotaso
Copy link
Member

/lgtm
/approve

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

knative-prow bot commented Nov 24, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, knative-prow-robot

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

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 24, 2022
@knative-prow knative-prow bot merged commit eb814ed into knative:release-1.7 Nov 24, 2022
nak3 pushed a commit to nak3/serving that referenced this pull request Nov 30, 2022
knative#13504)

The autoscaler sends a probe to detect the activator is in the data
path. This probe was inadvertently passed to the user container which
was preventing scale to 0.

Co-authored-by: dprotaso <dprotaso@gmail.com>
openshift-merge-robot pushed a commit to openshift-knative/serving that referenced this pull request Nov 30, 2022
knative#13504) (#49)

The autoscaler sends a probe to detect the activator is in the data
path. This probe was inadvertently passed to the user container which
was preventing scale to 0.

Co-authored-by: dprotaso <dprotaso@gmail.com>

Co-authored-by: Knative Prow Robot <knative-prow-robot@google.com>
Co-authored-by: dprotaso <dprotaso@gmail.com>
openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/knative-serving that referenced this pull request Nov 30, 2022
knative#13504)

The autoscaler sends a probe to detect the activator is in the data
path. This probe was inadvertently passed to the user container which
was preventing scale to 0.

Co-authored-by: dprotaso <dprotaso@gmail.com>
openshift-merge-robot pushed a commit to openshift-knative/serving that referenced this pull request Dec 6, 2022
knative#13504) (#50)

The autoscaler sends a probe to detect the activator is in the data
path. This probe was inadvertently passed to the user container which
was preventing scale to 0.

Co-authored-by: dprotaso <dprotaso@gmail.com>

Co-authored-by: Knative Prow Robot <knative-prow-robot@google.com>
Co-authored-by: dprotaso <dprotaso@gmail.com>
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 area/networking 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.

2 participants