Timeout of Step

    You need to upgrade to version 1.5+ to use the timeout feature.

    This section introduces how to add timeout to workflow steps in KubeVela.

    timeout follows the duration format, e.g. 30s, 1m, etc. You can refer to Golang’s parseDuration.

    If a step is not completed within the specified time, KubeVela will set the status of the step to failed and the Reason of the step will be set to Timeout.

    Use vela status to check the status of the Application:

    1. $ vela status timeout-example
    2. About:
    4.   Name:         timeout-example
    5.   Namespace:    default
    6.   Created at:   2022-06-25 00:51:43 +0800 CST
    7.   Status:       workflowTerminated
    9. Workflow:
    11.   mode: StepByStep
    12.   finished: true
    13.   Terminated: true
    14.   Steps
    15.   - id:1f58n13qdp
    16.     name:apply-comp1
    17.     type:apply-component
    18.     phase:succeeded
    19.     message:
    20.   - id:1pfije4ugt
    21.     name:suspend
    22.     type:suspend
    23.     phase:failed
    25.     name:apply-comp2
    26.     type:apply-component
    27.     phase:skipped
    28.     message:
    30. Services:
    32.   - Name: comp1
    33.     Cluster: local  Namespace: default
    34.     Type: webservice
    35.     Healthy Ready:1/1
    36.     No trait applied

    As you can see, when the first component is successfully deployed, the workflow is suspended on the second suspend step. The suspend step is set with a timeout of five seconds. If the workflow is not resumed within five seconds, the step will fail because of timeout. The third step is skipped because the previous suspend step failed.