Skip to content
This repository has been archived by the owner on Oct 26, 2021. It is now read-only.

Latest commit

 

History

History
36 lines (29 loc) · 3.88 KB

NodeStatus.md

File metadata and controls

36 lines (29 loc) · 3.88 KB
Raw

NodeStatus

NodeStatus contains status information about an individual node in the workflow

Properties

Name Type Description Notes
boundaryID String BoundaryID indicates the node ID of the associated template root node in which this node belongs to [optional]
children List<String> Children is a list of child node IDs [optional]
daemoned Boolean Daemoned tracks whether or not this node was daemoned and need to be terminated [optional]
displayName String DisplayName is a human readable representation of the node. Unique within a template boundary [optional]
finishedAt org.joda.time.DateTime [optional]
hostNodeName String HostNodeName name of the Kubernetes node on which the Pod is running, if applicable [optional]
id String ID is a unique identifier of a node within the worklow It is implemented as a hash of the node name, which makes the ID deterministic
inputs Inputs [optional]
memoizationStatus MemoizationStatus [optional]
message String A human readable message indicating details about why the node is in this condition. [optional]
name String Name is unique name in the node tree used to generate the node ID
outboundNodes List<String> OutboundNodes tracks the node IDs which are considered &quot;outbound&quot; nodes to a template invocation. For every invocation of a template, there are nodes which we considered as &quot;outbound&quot;. Essentially, these are last nodes in the execution sequence to run, before the template is considered completed. These nodes are then connected as parents to a following step. In the case of single pod steps (i.e. container, script, resource templates), this list will be nil since the pod itself is already considered the &quot;outbound&quot; node. In the case of DAGs, outbound nodes are the &quot;target&quot; tasks (tasks with no children). In the case of steps, outbound nodes are all the containers involved in the last step group. NOTE: since templates are composable, the list of outbound nodes are carried upwards when a DAG/steps template invokes another DAG/steps template. In other words, the outbound nodes of a template, will be a superset of the outbound nodes of its last children. [optional]
outputs Outputs [optional]
phase String Phase a simple, high-level summary of where the node is in its lifecycle. Can be used as a state machine. [optional]
podIP String PodIP captures the IP of the pod for daemoned steps [optional]
resourcesDuration Map<String, Long> ResourcesDuration is indicative, but not accurate, resource duration. This is populated when the nodes completes. [optional]
startedAt org.joda.time.DateTime [optional]
storedTemplateID String StoredTemplateID is the ID of stored template. DEPRECATED: This value is not used anymore. [optional]
synchronizationStatus NodeSynchronizationStatus [optional]
templateName String TemplateName is the template name which this node corresponds to. Not applicable to virtual nodes (e.g. Retry, StepGroup) [optional]
templateRef TemplateRef [optional]
templateScope String TemplateScope is the template scope in which the template of this node was retrieved. [optional]
type String Type indicates type of node
workflowTemplateName String WorkflowTemplateName is the WorkflowTemplate resource name on which the resolved template of this node is retrieved. DEPRECATED: This value is not used anymore. [optional]