diff --git a/docs/pipeline-api.md b/docs/pipeline-api.md index 97065ad87a0..8e8e62ee84f 100644 --- a/docs/pipeline-api.md +++ b/docs/pipeline-api.md @@ -445,6 +445,117 @@ TaskSpec +
+(Appears on:PipelineTask) +
+EmbeddedTask is used to define a Task inline within a Pipeline’s PipelineTasks.
+Field | +Description | +||||
---|---|---|---|---|---|
+spec + +k8s.io/apimachinery/pkg/runtime.RawExtension + + |
+
+(Optional)
+ Spec is a specification of a custom task ++ +
|
+||||
+metadata + + +PipelineTaskMetadata + + + |
++(Optional) + | +||||
+TaskSpec + + +TaskSpec + + + |
+
+
+(Members of TaskSpec is a specification of a task + |
+
string
alias)+(Appears on:Step) +
+OnErrorType defines a list of supported exiting behavior of a container on error
+Value | +Description | +
---|---|
"continue" |
+Continue indicates continue executing the rest of the steps irrespective of the container exit code + |
+
"stopAndFail" |
+StopAndFail indicates exit the taskRun if the container exits with non-zero exit code + |
+
@@ -1359,8 +1470,8 @@ string
Name of the container specified as a DNS_LABEL. -Each container in a pod must have a unique name (DNS_LABEL). +
Name of the Sidecar specified as a DNS_LABEL. +Each Sidecar in a Task must have a unique name (DNS_LABEL). Cannot be updated.
Docker image name. +
Image reference name. More info: https://kubernetes.io/docs/concepts/containers/images This field is optional to allow higher level config management to default or override container images in workload controllers like Deployments and StatefulSets.
@@ -1389,8 +1500,8 @@ container images in workload controllers like Deployments and StatefulSets.Entrypoint array. Not executed within a shell. -The docker image’s ENTRYPOINT is used if this is not provided. -Variable references $(VAR_NAME) are expanded using the container’s environment. If a variable +The image’s ENTRYPOINT is used if this is not provided. +Variable references $(VAR_NAME) are expanded using the Sidecar’s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. “$$(VAR_NAME)” will produce the string literal “$(VAR_NAME)”. Escaped references will never be expanded, regardless @@ -1408,8 +1519,8 @@ More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
Periodic probe of container service readiness. +
Periodic probe of Sidecar service readiness. Container will be removed from service endpoints if the probe fails. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes
@@ -1576,7 +1687,7 @@ Kubernetes core/v1.ProbeStartupProbe indicates that the Pod has successfully initialized. +
StartupProbe indicates that the Pod the Sidecar is running in has successfully initialized. If specified, no other probes are executed until this completes successfully. If this probe fails, the Pod will be restarted, just as if the livenessProbe failed. This can be used to provide different probe parameters at the beginning of a Pod’s lifecycle, @@ -1596,7 +1707,7 @@ Kubernetes core/v1.Lifecycle
Actions that the management system should take in response to container lifecycle events. +
Actions that the management system should take in response to Sidecar lifecycle events. Cannot be updated.
Optional: Path at which the file to which the container’s termination message -will be written is mounted into the container’s filesystem. +
Optional: Path at which the file to which the Sidecar’s termination message +will be written is mounted into the Sidecar’s filesystem. Message written is intended to be brief final status, such as an assertion failure message. Will be truncated by the node if greater than 4096 bytes. The total message length across all containers will be limited to 12kb. @@ -1630,9 +1741,9 @@ Kubernetes core/v1.TerminationMessagePolicy
Indicate how the termination message should be populated. File will use the contents of -terminationMessagePath to populate the container status message on both success and failure. -FallbackToLogsOnError will use the last chunk of container log output if the termination -message file is empty and the container exited with an error. +terminationMessagePath to populate the Sidecar status message on both success and failure. +FallbackToLogsOnError will use the last chunk of Sidecar log output if the termination +message file is empty and the Sidecar exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.
@@ -1667,7 +1778,7 @@ Kubernetes core/v1.SecurityContextSecurityContext defines the security options the container should be run with. +
SecurityContext defines the security options the Sidecar should be run with. If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext. More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
Whether this container should allocate a buffer for stdin in the container runtime. If this -is not set, reads from stdin in the container will always result in EOF. +
Whether this Sidecar should allocate a buffer for stdin in the container runtime. If this +is not set, reads from stdin in the Sidecar will always result in EOF. Default is false.
Whether the container runtime should close the stdin channel after it has been opened by a single attach. When stdin is true the stdin stream will remain open across multiple attach -sessions. If stdinOnce is set to true, stdin is opened on container start, is empty until the +sessions. If stdinOnce is set to true, stdin is opened on Sidecar start, is empty until the first client attaches to stdin, and then remains open and accepts data until the client disconnects, -at which time stdin is closed and remains closed until the container is restarted. If this +at which time stdin is closed and remains closed until the Sidecar is restarted. If this flag is false, a container processes that reads from stdin will never receive an EOF. Default is false
@@ -1713,7 +1824,7 @@ boolWhether this container should allocate a TTY for itself, also requires ‘stdin’ to be true. +
Whether this Sidecar should allocate a TTY for itself, also requires ‘stdin’ to be true. Default is false.
Name of the container specified as a DNS_LABEL. -Each container in a pod must have a unique name (DNS_LABEL). -Cannot be updated.
+Name of the Step specified as a DNS_LABEL. +Each Step in a Task must have a unique name.
Docker image name. -More info: https://kubernetes.io/docs/concepts/containers/images -This field is optional to allow higher level config management to default or override -container images in workload controllers like Deployments and StatefulSets.
+More info: https://kubernetes.io/docs/concepts/containers/imagesEntrypoint array. Not executed within a shell. -The docker image’s ENTRYPOINT is used if this is not provided. +The image’s ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container’s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. “$$(VAR_NAME)” will @@ -1824,7 +1932,7 @@ More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
onError
OnError defines the exiting behavior of a container on error -can be set to [ continue | stopAndFail ] -stopAndFail indicates exit the taskRun if the container exits with non-zero exit code -continue indicates continue executing the rest of the steps irrespective of the container exit code
+can be set to [ continue | stopAndFail ]Docker image name. +
Image reference name. More info: https://kubernetes.io/docs/concepts/containers/images This field is optional to allow higher level config management to default or override container images in workload controllers like Deployments and StatefulSets.
@@ -2123,8 +2231,8 @@ container images in workload controllers like Deployments and StatefulSets.Entrypoint array. Not executed within a shell. -The docker image’s ENTRYPOINT is used if this is not provided. -Variable references $(VAR_NAME) are expanded using the container’s environment. If a variable +The image’s ENTRYPOINT is used if this is not provided. +Variable references $(VAR_NAME) are expanded using the Step’s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. “$$(VAR_NAME)” will produce the string literal “$(VAR_NAME)”. Escaped references will never be expanded, regardless @@ -2142,8 +2250,8 @@ More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
string
alias)+(Appears on:Step) +
+OnErrorType defines a list of supported exiting behavior of a container on error
+Value | +Description | +
---|---|
"continue" |
+Continue indicates continue executing the rest of the steps irrespective of the container exit code + |
+
"stopAndFail" |
+StopAndFail indicates exit the taskRun if the container exits with non-zero exit code + |
+
@@ -7511,8 +7642,8 @@ string
Name of the container specified as a DNS_LABEL. -Each container in a pod must have a unique name (DNS_LABEL). +
Name of the Sidecar specified as a DNS_LABEL. +Each Sidecar in a Task must have a unique name (DNS_LABEL). Cannot be updated.
Docker image name. -More info: https://kubernetes.io/docs/concepts/containers/images -This field is optional to allow higher level config management to default or override -container images in workload controllers like Deployments and StatefulSets.
+Image name to be used by the Sidecar. +More info: https://kubernetes.io/docs/concepts/containers/images
Entrypoint array. Not executed within a shell. -The docker image’s ENTRYPOINT is used if this is not provided. -Variable references $(VAR_NAME) are expanded using the container’s environment. If a variable +The image’s ENTRYPOINT is used if this is not provided. +Variable references $(VAR_NAME) are expanded using the Sidecar’s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. “$$(VAR_NAME)” will produce the string literal “$(VAR_NAME)”. Escaped references will never be expanded, regardless @@ -7560,7 +7689,7 @@ More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
Periodic probe of container service readiness. +
Periodic probe of Sidecar service readiness. Container will be removed from service endpoints if the probe fails. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes
@@ -7728,7 +7857,7 @@ Kubernetes core/v1.ProbeStartupProbe indicates that the Pod has successfully initialized. +
StartupProbe indicates that the Pod the Sidecar is running in has successfully initialized. If specified, no other probes are executed until this completes successfully. If this probe fails, the Pod will be restarted, just as if the livenessProbe failed. This can be used to provide different probe parameters at the beginning of a Pod’s lifecycle, @@ -7748,7 +7877,7 @@ Kubernetes core/v1.Lifecycle
Actions that the management system should take in response to container lifecycle events. +
Actions that the management system should take in response to Sidecar lifecycle events. Cannot be updated.
Optional: Path at which the file to which the container’s termination message -will be written is mounted into the container’s filesystem. +
Optional: Path at which the file to which the Sidecar’s termination message +will be written is mounted into the Sidecar’s filesystem. Message written is intended to be brief final status, such as an assertion failure message. Will be truncated by the node if greater than 4096 bytes. The total message length across all containers will be limited to 12kb. @@ -7782,9 +7911,9 @@ Kubernetes core/v1.TerminationMessagePolicy
Indicate how the termination message should be populated. File will use the contents of -terminationMessagePath to populate the container status message on both success and failure. -FallbackToLogsOnError will use the last chunk of container log output if the termination -message file is empty and the container exited with an error. +terminationMessagePath to populate the Sidecar status message on both success and failure. +FallbackToLogsOnError will use the last chunk of Sidecar log output if the termination +message file is empty and the Sidecar exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.
@@ -7819,7 +7948,7 @@ Kubernetes core/v1.SecurityContextSecurityContext defines the security options the container should be run with. +
SecurityContext defines the security options the Sidecar should be run with. If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext. More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
Whether this container should allocate a buffer for stdin in the container runtime. If this -is not set, reads from stdin in the container will always result in EOF. +
Whether this Sidecar should allocate a buffer for stdin in the container runtime. If this +is not set, reads from stdin in the Sidecar will always result in EOF. Default is false.
Whether the container runtime should close the stdin channel after it has been opened by a single attach. When stdin is true the stdin stream will remain open across multiple attach -sessions. If stdinOnce is set to true, stdin is opened on container start, is empty until the +sessions. If stdinOnce is set to true, stdin is opened on Sidecar start, is empty until the first client attaches to stdin, and then remains open and accepts data until the client disconnects, -at which time stdin is closed and remains closed until the container is restarted. If this +at which time stdin is closed and remains closed until the Sidecar is restarted. If this flag is false, a container processes that reads from stdin will never receive an EOF. Default is false
@@ -7865,7 +7994,7 @@ boolWhether this container should allocate a TTY for itself, also requires ‘stdin’ to be true. +
Whether this Sidecar should allocate a TTY for itself, also requires ‘stdin’ to be true. Default is false.
Name of the container specified as a DNS_LABEL. -Each container in a pod must have a unique name (DNS_LABEL). -Cannot be updated.
+Name of the Step specified as a DNS_LABEL. +Each Step in a Task must have a unique name.
Docker image name. -More info: https://kubernetes.io/docs/concepts/containers/images -This field is optional to allow higher level config management to default or override -container images in workload controllers like Deployments and StatefulSets.
+Image reference name to run for this Step. +More info: https://kubernetes.io/docs/concepts/containers/images
Entrypoint array. Not executed within a shell. -The docker image’s ENTRYPOINT is used if this is not provided. +The image’s ENTRYPOINT is used if this is not provided. Variable references $(VAR_NAME) are expanded using the container’s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. “$$(VAR_NAME)” will @@ -8135,7 +8261,7 @@ More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
Deprecated. This field will be removed in a future release. Periodic probe of container service readiness. -Container will be removed from service endpoints if the probe fails. +Step will be removed from service endpoints if the probe fails. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle#container-probes
@@ -8307,7 +8433,7 @@ Kubernetes core/v1.ProbeDeprecated. This field will be removed in a future release. -DeprecatedStartupProbe indicates that the Pod has successfully initialized. +DeprecatedStartupProbe indicates that the Pod this Step runs in has successfully initialized. If specified, no other probes are executed until this completes successfully. If this probe fails, the Pod will be restarted, just as if the livenessProbe failed. This can be used to provide different probe parameters at the beginning of a Pod’s lifecycle, @@ -8341,14 +8467,7 @@ string
Deprecated. This field will be removed in a future release. -Optional: Path at which the file to which the container’s termination message -will be written is mounted into the container’s filesystem. -Message written is intended to be brief final status, such as an assertion failure message. -Will be truncated by the node if greater than 4096 bytes. The total message length across -all containers will be limited to 12kb. -Defaults to /dev/termination-log. -Cannot be updated.
+Deprecated. This field will be removed in a future release and can’t be meaningfully used.
Deprecated. This field will be removed in a future release. -Indicate how the termination message should be populated. File will use the contents of -terminationMessagePath to populate the container status message on both success and failure. -FallbackToLogsOnError will use the last chunk of container log output if the termination -message file is empty and the container exited with an error. -The log output is limited to 2048 bytes or 80 lines, whichever is smaller. -Defaults to File. -Cannot be updated.
+Deprecated. This field will be removed in a future release and can’t be meaningfully used.
SecurityContext defines the security options the container should be run with. +
SecurityContext defines the security options the Step should be run with. If set, the fields of SecurityContext override the equivalent fields of PodSecurityContext. More info: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
onError
OnError defines the exiting behavior of a container on error -can be set to [ continue | stopAndFail ] -stopAndFail indicates exit the taskRun if the container exits with non-zero exit code -continue indicates continue executing the rest of the steps irrespective of the container exit code
+can be set to [ continue | stopAndFail ]Deprecated. This field will be removed in a future release. -DeprecatedName of the container specified as a DNS_LABEL. -Each container in a pod must have a unique name (DNS_LABEL). +Default name for each Step specified as a DNS_LABEL. +Each Step in a Task must have a unique name. Cannot be updated.
Docker image name. +
Default image name to use for each Step. More info: https://kubernetes.io/docs/concepts/containers/images This field is optional to allow higher level config management to default or override container images in workload controllers like Deployments and StatefulSets.
@@ -8694,7 +8806,7 @@ container images in workload controllers like Deployments and StatefulSets. (Optional)Entrypoint array. Not executed within a shell. The docker image’s ENTRYPOINT is used if this is not provided. -Variable references $(VAR_NAME) are expanded using the container’s environment. If a variable +Variable references $(VAR_NAME) are expanded using the Step’s environment. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. “$$(VAR_NAME)” will produce the string literal “$(VAR_NAME)”. Escaped references will never be expanded, regardless @@ -8712,8 +8824,8 @@ More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
Deprecated. This field will be removed in a future release. -Whether this container should allocate a buffer for stdin in the container runtime. If this -is not set, reads from stdin in the container will always result in EOF. +Whether this Step should allocate a buffer for stdin in the container runtime. If this +is not set, reads from stdin in the Step will always result in EOF. Default is false.
Deprecated. This field will be removed in a future release. -Whether this container should allocate a DeprecatedTTY for itself, also requires ‘stdin’ to be true. +Whether this Step should allocate a DeprecatedTTY for itself, also requires ‘stdin’ to be true. Default is false.