You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As soon as a Freight is successfully promoted into a Stage, it is immediately verified to go to downstream Stages. This is often too fast for users. Instead, they wish for there to be a minimum "soak" or "bake" time before it can automatically go downstream (e.g. 1h, 1d).
We could introduce a verificationDelay option in a Stage where a Freight must be running in a Stage for some minimum amount of time, before it is qualified to downstream
Motivation
Users want automated promotions, but don't want for it to be immediate.
Suggested Implementation
Delay the marking of a Freight to be verifiedIn a stage until it passes the user specified time.
There is a workaround for now, which is to reference an AnalysisTemplate that has an initialDelay. e.g.:
apiVersion: argoproj.io/v1alpha1kind: AnalysisTemplatemetadata:
name: soakspec:
metrics:
- name: soakcount: 1initialDelay: 1hprovider:
web:
url: https://example.com # Choose a URL that will return 200
The text was updated successfully, but these errors were encountered:
I'm interested on this feature as I'm building POC using Kargo to deploy EKS clusters using Kubernetes Controllers like CAPI/ACK/Crossplane, and soak/bake time is important when rolling out upgrades in waves, with different soak time criteria. for example:
after env/dev is deployed, we want to wait 6hrs before starting deploying env/test
Your comment (@csantanapr) makes me wonder if our actual desire is not to delay the verification process, but rather to delay the (automatic) creation of the promotion for the next Stage based on a set of options.
I think this would also be the superior option, as it puts the consumer in control over their "delayed rollout" desires instead of the producer. I.e., in a scenario where you have A -> [B, C], both B and C can define their unique soak desires instead of it being forced upon them by A.
Proposed Feature
As soon as a Freight is successfully promoted into a Stage, it is immediately verified to go to downstream Stages. This is often too fast for users. Instead, they wish for there to be a minimum "soak" or "bake" time before it can automatically go downstream (e.g. 1h, 1d).
We could introduce a
verificationDelay
option in a Stage where a Freight must be running in a Stage for some minimum amount of time, before it is qualified to downstreamMotivation
Users want automated promotions, but don't want for it to be immediate.
Suggested Implementation
Delay the marking of a Freight to be verifiedIn a stage until it passes the user specified time.
There is a workaround for now, which is to reference an AnalysisTemplate that has an initialDelay. e.g.:
The text was updated successfully, but these errors were encountered: