Create v2 GC settings#8615
Conversation
knative-prow-robot
left a comment
There was a problem hiding this comment.
@whaught: 0 warnings.
Details
In response to this:
Issue #8208
Proposed Changes
- Creates a new setting for allowing users to specify a maximum number of revisions to retain.
- Currently we aggressively delete all stale revisions after a given amount of time. This will allow users to instead specify a number they would like to keep around and potentially reduce the time-bounds to zero.
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.
|
/hold still needs unit test coverage for validation |
| cm.AsDuration("stale-revision-timeout", &c.StaleRevisionTimeout), | ||
| cm.AsDuration("stale-revision-lastpinned-debounce", &c.StaleRevisionLastpinnedDebounce), | ||
|
|
||
| cm.AsInt64("stale-revision-maximum-generations", &c.StaleRevisionMaximumGenerations), |
There was a problem hiding this comment.
some validation below is probably in order:
0 seems invalid value (with current -1 sentinel)
all negative but -1 are invalid as well.
Also max cannot be less than min?
There was a problem hiding this comment.
0 is actually a valid value. This is a count of inactive revisions only (not including actively referenced ones). The system will never consider active revisions for deletion and setting 0 would mean "delete everything as soon as it's not serving).
Similarly a min 0 would mean "delete everything that isn't active as soon as the staleness times have elapsed"
|
ugh :) you've repushed with validation |
Co-authored-by: Victor Agababov <vagababov@gmail.com>
|
The following jobs failed:
Failed non-flaky tests preventing automatic retry of pull-knative-serving-unit-tests: and 2 more. |
|
/unhold |
|
The following is the coverage report on the affected files.
|
Co-authored-by: Matt Moore <mattmoor@vmware.com>
mattmoor
left a comment
There was a problem hiding this comment.
/lgtm
/approve
I'm still puzzled by why the missing quotes didn't blow up our tests, but they look right and it's not your change's fault if they aren't 😅
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mattmoor, whaught The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Issue #8208
Proposed Changes