WorkflowTemplate is the Schema for the WorkflowTemplates API. A Workflow Template is a reusable workflow configuration.
Type
CRD
Group
dataproc.gcp.upbound.io
Version
v1beta1
apiVersion: dataproc.gcp.upbound.io/v1beta1
kind: WorkflowTemplate
WorkflowTemplateSpec defines the desired state of WorkflowTemplate
No description provided.
Required. The Directed Acyclic Graph of Jobs to submit.
Optional. Job is a Hadoop job.
Optional. HCFS URIs of archives to be extracted into the working directory of each executor. Supported file types: .jar, .tar, .tar.gz, .tgz, and .zip.
Optional. The arguments to pass to the driver. Do not include arguments, such as --conf, that can be set as job properties, since a collision may occur that causes an incorrect job submission.
Optional. HCFS URIs of files to be placed in the working directory of each executor. Useful for naively parallel tasks.
Optional. HCFS URIs of jar files to be added to the Spark CLASSPATH.
Optional. The runtime log config for job execution.
Optional. Job is a Hive job.
Optional. HCFS URIs of jar files to be added to the Spark CLASSPATH.
A list of queries.
Required. The queries to execute. You do not need to end a query expression with a semicolon. Multiple queries can be specified in one string by separating each with a semicolon. Here is an example of a Dataproc API snippet that uses a QueryList to specify a HiveJob: "hiveJob": { "queryList": { "queries": } }
Optional. Job is a Pig job.
Optional. HCFS URIs of jar files to be added to the Spark CLASSPATH.
Optional. The runtime log config for job execution.
A list of queries.
Required. The queries to execute. You do not need to end a query expression with a semicolon. Multiple queries can be specified in one string by separating each with a semicolon. Here is an example of a Dataproc API snippet that uses a QueryList to specify a HiveJob: "hiveJob": { "queryList": { "queries": } }
Optional. The optional list of prerequisite job step_ids. If not specified, the job will start at the beginning of workflow.
Optional. Job is a Presto job.
Optional. Presto client tags to attach to this query
Optional. The runtime log config for job execution.
A list of queries.
Required. The queries to execute. You do not need to end a query expression with a semicolon. Multiple queries can be specified in one string by separating each with a semicolon. Here is an example of a Dataproc API snippet that uses a QueryList to specify a HiveJob: "hiveJob": { "queryList": { "queries": } }
Optional. Job is a PySpark job.
Optional. HCFS URIs of archives to be extracted into the working directory of each executor. Supported file types: .jar, .tar, .tar.gz, .tgz, and .zip.
Optional. The arguments to pass to the driver. Do not include arguments, such as --conf, that can be set as job properties, since a collision may occur that causes an incorrect job submission.
Optional. HCFS URIs of files to be placed in the working directory of each executor. Useful for naively parallel tasks.
Optional. HCFS URIs of jar files to be added to the Spark CLASSPATH.
Optional. The runtime log config for job execution.
Optional. HCFS file URIs of Python files to pass to the PySpark framework. Supported file types: .py, .egg, and .zip.
Optional. Job scheduling configuration.
Optional. Job is a Spark job.
Optional. HCFS URIs of archives to be extracted into the working directory of each executor. Supported file types: .jar, .tar, .tar.gz, .tgz, and .zip.
Optional. The arguments to pass to the driver. Do not include arguments, such as --conf, that can be set as job properties, since a collision may occur that causes an incorrect job submission.
Optional. HCFS URIs of files to be placed in the working directory of each executor. Useful for naively parallel tasks.
Optional. HCFS URIs of jar files to be added to the Spark CLASSPATH.
Optional. The runtime log config for job execution.
Optional. Job is a SparkR job.
Optional. HCFS URIs of archives to be extracted into the working directory of each executor. Supported file types: .jar, .tar, .tar.gz, .tgz, and .zip.
Optional. The arguments to pass to the driver. Do not include arguments, such as --conf, that can be set as job properties, since a collision may occur that causes an incorrect job submission.
Optional. HCFS URIs of files to be placed in the working directory of each executor. Useful for naively parallel tasks.
Optional. The runtime log config for job execution.
Optional. Job is a SparkSql job.
Optional. HCFS URIs of jar files to be added to the Spark CLASSPATH.
Optional. The runtime log config for job execution.
A list of queries.
Required. The queries to execute. You do not need to end a query expression with a semicolon. Multiple queries can be specified in one string by separating each with a semicolon. Here is an example of a Dataproc API snippet that uses a QueryList to specify a HiveJob: "hiveJob": { "queryList": { "queries": } }
Optional. Template parameters whose values are substituted into the template. Values for parameters must be provided when the template is instantiated.
Required. Paths to all fields that the parameter replaces. A field is allowed to appear in at most one parameter's list of field paths. A field path is similar in syntax to a .sparkJob.args
Optional. Validation rules to be applied to this parameter's value.
Required. WorkflowTemplate scheduling information.
Optional. A selector that chooses target cluster for jobs based on metadata. The selector is evaluated at the time each job is submitted.
A cluster that is managed by the workflow.
Required. The cluster configuration.
Optional. Autoscaling config for the policy associated with the cluster. Cluster does not autoscale if this field is unset.
Optional. Encryption settings for the cluster.
Optional. Port/endpoint configuration for this cluster
Optional. The shared Compute Engine config settings for all instances in a cluster.
Optional. Node Group Affinity for sole-tenant clusters.
Optional. Reservation Affinity for consuming Zonal reservation.
Required. List of allowed values for the parameter.
Optional. The URIs of service account scopes to be included in Compute Engine instances. The following base set of scopes is always included: * https://www.googleapis.com/auth/cloud.useraccounts.readonly * https://www.googleapis.com/auth/devstorage.read_write * https://www.googleapis.com/auth/logging.write If no scopes are specified, the following defaults are also provided: * https://www.googleapis.com/auth/bigquery * https://www.googleapis.com/auth/bigtable.admin.table * https://www.googleapis.com/auth/bigtable.data * https://www.googleapis.com/auth/devstorage.full_control
Optional. Shielded Instance Config for clusters using Compute Engine Shielded VMs. Structure defined below.
The Compute Engine tags to add to all instances (see (https://cloud.google.com/compute/docs/label-or-tag-resources#tags)).
Optional. Commands to execute on each node after config is completed. By default, executables are run on master and all worker nodes. You can test a node's role metadata to run an executable on a master or worker node, as shown below using curl (you can also use wget): ROLE=$(curl -H Metadata-Flavor:Google http://metadata/computeMetadata/v1/instance/attributes/dataproc-role) if ; then ... master specific actions ... else ... worker specific actions ... fi
Optional. Lifecycle setting for the cluster.
Optional. The Compute Engine config settings for additional worker instances in a cluster.
Optional. The Compute Engine accelerator configuration for these instances.
Optional. Disk option config settings.
Optional. The Compute Engine config settings for additional worker instances in a cluster.
Optional. The Compute Engine accelerator configuration for these instances.
Optional. Disk option config settings.
Optional. Security settings for the cluster.
Kerberos related configuration.
Optional. The config settings for software inside the cluster.
Optional. The Compute Engine config settings for additional worker instances in a cluster.
Optional. The Compute Engine accelerator configuration for these instances.
Optional. Disk option config settings.
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
WorkflowTemplateStatus defines the observed state of WorkflowTemplate.
No description provided.
Required. WorkflowTemplate scheduling information.
A cluster that is managed by the workflow.
Required. The cluster configuration.
Optional. Port/endpoint configuration for this cluster
Optional. Lifecycle setting for the cluster.
Optional. The Compute Engine config settings for additional worker instances in a cluster.
Output only. The list of instance names. Dataproc derives the names from cluster_name, num_instances, and the instance group.
Output only. The config for Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
Optional. The Compute Engine config settings for additional worker instances in a cluster.
Output only. The list of instance names. Dataproc derives the names from cluster_name, num_instances, and the instance group.
Output only. The config for Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
Optional. The Compute Engine config settings for additional worker instances in a cluster.
Output only. The list of instance names. Dataproc derives the names from cluster_name, num_instances, and the instance group.
Output only. The config for Compute Engine Instance Group Manager that manages this group. This is only used for preemptible instance groups.
Conditions of the resource.
template
apiVersion: dataproc.gcp.upbound.io/v1beta1
kind: WorkflowTemplate
metadata:
annotations:
meta.upbound.io/example-id: dataproc/v1beta1/workflowtemplate
labels:
testing.upbound.io/example-name: template
name: template
spec:
forProvider:
jobs:
- sparkJob:
- mainClass: SomeClass
stepId: someJob
- prerequisiteStepIds:
- someJob
prestoJob:
- queryFileUri: someuri
stepId: otherJob
location: us-central1
placement:
- managedCluster:
- clusterName: my-cluster
config:
- gceClusterConfig:
- tags:
- foo
- bar
zone: us-central1-a
masterConfig:
- diskConfig:
- bootDiskSizeGb: 15
bootDiskType: pd-ssd
machineType: n1-standard-1
numInstances: 1
secondaryWorkerConfig:
- numInstances: 2
softwareConfig:
- imageVersion: 2.0.35-debian10
workerConfig:
- diskConfig:
- bootDiskSizeGb: 10
numLocalSsds: 2
machineType: n1-standard-2
numInstances: 3
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.