knative-extensions/serving-progressive-rollout
Knative Serving extension to roll out the revision progressively
GoApache-2.0
Issues
- 2
USE with caution for resourceUtil rollout strategy, any way to alleviate??????
#190 opened by houshengbo - 9
Can there be an approach to terminate the last pod of the previous revision when most pods of new revision is up
#200 opened by gavrissh - 5
With the resourceUtil strategy, traffic transfer does not occur during an update when deployment hits quota limit
#203 opened by AyushSawant18588 - 2
During a service update, delayed resource release causes new revision pods to encounter errors and restart until resources are freed.
#204 opened by AyushSawant18588 - 1
With the resourceUtil strategy, graceful traffic transfer does not occur during consecutive update requests.
#202 opened by AyushSawant18588 - 0
- 1
If there is only one pod, or overratio set to 100, using resourceUtil strategy won't directly kill the old pods immediately
#191 opened by houshengbo - 2
Traffic Proportion Metrics
#106 opened by wSedlacek - 3
NewObservedGenFailure will pop up once upgrading the images of serving progressive rollout
#193 opened by houshengbo - 1
When rollout a new revision, scale down the previous revisions with error down to 0
#135 opened by houshengbo - 2
Route traffic percent gets updated for the revision that is not in the ready status
#83 opened by yuzisun - 1
Feature request: Resource effective mode support in the Progressive Rollout
#160 opened by houshengbo - 0
Clean up the SPA, when the revision is deleted
#162 opened by houshengbo - 3
- 0
Removal of RO leading to incorrect calculation of the target replicas for the revisions
#134 opened by houshengbo - 0
- 0
The replica from old revision terminated before the new revision is fully ready
#84 opened by yuzisun - 1
the new revision pods immediately get into Terminating state after bumping from 4 to 40
#85 opened by yuzisun - 1
How to port the existing knative services into the serving progressive rollout
#67 opened by houshengbo - 0
SPA for the revisions scaling down do not pick up the latest values for the RO.spec
#66 opened by houshengbo - 0
When each stage times out, we need to verify if there is failures, errors, etc with launching the new revision
#60 opened by houshengbo - 0
When there are multiple existing revisions, enable the support of the transition from many to one target revision
#61 opened by houshengbo - 0
- 0
Set up e2e test framework for this repo
#29 opened by houshengbo - 0
Sync-up service and autoscaling KPA in the Knative Serving repos with CI prows
#9 opened by houshengbo