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
In pre/post-deploment task or evaluation phases as well as promotion phase we have a failure mechanism to fail the phase either after certain amount of retries or after a timeout. We should be implement similar functionality for the WorkloadDeployment phase.
Details
We should introduce .status.DeploymentStartTime into KeptnWorkloadVersion CRD. Afterwards we should adapt the logic of KeptnWorkloadVersionRecolciler to set the .status.DeploymentStartTime and periodically check that the current time is not beyond the start time + timeout.
The value of the timeout will be set by a new parameter in KeptnConfig
odubajDT
changed the title
Incroduce failure mechanism for WorkloadDeployment phase
Introduce failure mechanism for WorkloadDeployment phase
Feb 27, 2024
Description
In pre/post-deploment task or evaluation phases as well as promotion phase we have a failure mechanism to fail the phase either after certain amount of retries or after a timeout. We should be implement similar functionality for the
WorkloadDeployment
phase.Details
We should introduce
.status.DeploymentStartTime
intoKeptnWorkloadVersion
CRD. Afterwards we should adapt the logic ofKeptnWorkloadVersionRecolciler
to set the.status.DeploymentStartTime
and periodically check that the current time is not beyond the start time + timeout.The value of the timeout will be set by a new parameter in
KeptnConfig
A small PoC is available here.
DoD
KeptnConfig
has a new parameter forDeploymentTimeout
KeptnConfig
is reconciled byKeptnConfigReconciler
KeptnWorkloadVersionRecolciler
is adaptedNote
Please try to provide the implementation in multiple small PRs and not a single big PR
The text was updated successfully, but these errors were encountered: