WorkflowTemplatePlacementManagedClusterConfig class
Constructors
-
WorkflowTemplatePlacementManagedClusterConfig({Input<WorkflowTemplatePlacementManagedClusterConfigAutoscalingConfig?>? autoscalingConfig, Input<WorkflowTemplatePlacementManagedClusterConfigEncryptionConfig?>? encryptionConfig, Input<WorkflowTemplatePlacementManagedClusterConfigEndpointConfig?>? endpointConfig, Input<WorkflowTemplatePlacementManagedClusterConfigGceClusterConfig?>? gceClusterConfig, Input<WorkflowTemplatePlacementManagedClusterConfigGkeClusterConfig?>? gkeClusterConfig, Input<List<WorkflowTemplatePlacementManagedClusterConfigInitializationAction>?>? initializationActions, Input<WorkflowTemplatePlacementManagedClusterConfigLifecycleConfig?>? lifecycleConfig, Input<WorkflowTemplatePlacementManagedClusterConfigMasterConfig?>? masterConfig, Input<WorkflowTemplatePlacementManagedClusterConfigMetastoreConfig?>? metastoreConfig, Input<WorkflowTemplatePlacementManagedClusterConfigSecondaryWorkerConfig?>? secondaryWorkerConfig, Input<WorkflowTemplatePlacementManagedClusterConfigSecurityConfig?>? securityConfig, Input<WorkflowTemplatePlacementManagedClusterConfigSoftwareConfig?>? softwareConfig, Input<String?>? stagingBucket, Input<String?>? tempBucket, Input<WorkflowTemplatePlacementManagedClusterConfigWorkerConfig?>? workerConfig})
-
Creates a new WorkflowTemplatePlacementManagedClusterConfig.
autoscalingConfig Autoscaling config for the policy associated with the cluster. Cluster does not autoscale if this field is unset.
encryptionConfig Encryption settings for the cluster.
endpointConfig Port/endpoint configuration for this cluster
gceClusterConfig The shared Compute Engine config settings for all instances in a cluster.
gkeClusterConfig The Kubernetes Engine config for Dataproc clusters deployed to Kubernetes. Setting this is considered mutually exclusive with Compute Engine-based options such as gceClusterConfig, masterConfig, workerConfig, secondaryWorkerConfig, and autoscalingConfig.
initializationActions 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
lifecycleConfig Lifecycle setting for the cluster.
masterConfig The Compute Engine config settings for additional worker instances in a cluster.
metastoreConfig Metastore configuration.
secondaryWorkerConfig The Compute Engine config settings for additional worker instances in a cluster.
securityConfig Security settings for the cluster.
softwareConfig The config settings for software inside the cluster.
stagingBucket A Cloud Storage bucket used to stage job dependencies, config files, and job driver console output. If you do not specify a staging bucket, Cloud Dataproc will determine a Cloud Storage location (US, ASIA, or EU) for your cluster's staging bucket according to the Compute Engine zone where your cluster is deployed, and then create and manage this project-level, per-location bucket (see Dataproc staging and temp buckets).
tempBucket A Cloud Storage bucket used to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. If you do not specify a temp bucket, Dataproc will determine a Cloud Storage location (US, ASIA, or EU) for your cluster's temp bucket according to the Compute Engine zone where your cluster is deployed, and then create and manage this project-level, per-location bucket. The default bucket has a TTL of 90 days, but you can use any TTL (or none) if you specify a bucket.
workerConfig The Compute Engine config settings for additional worker instances in a cluster.
const
-
WorkflowTemplatePlacementManagedClusterConfig.fromMap(Map<String, dynamic> map)
-
factory
Properties
-
autoscalingConfig
→ Input<WorkflowTemplatePlacementManagedClusterConfigAutoscalingConfig?>?
-
Autoscaling config for the policy associated with the cluster. Cluster does not autoscale if this field is unset.
final
-
encryptionConfig
→ Input<WorkflowTemplatePlacementManagedClusterConfigEncryptionConfig?>?
-
Encryption settings for the cluster.
final
-
endpointConfig
→ Input<WorkflowTemplatePlacementManagedClusterConfigEndpointConfig?>?
-
Port/endpoint configuration for this cluster
final
-
gceClusterConfig
→ Input<WorkflowTemplatePlacementManagedClusterConfigGceClusterConfig?>?
-
The shared Compute Engine config settings for all instances in a cluster.
final
-
gkeClusterConfig
→ Input<WorkflowTemplatePlacementManagedClusterConfigGkeClusterConfig?>?
-
The Kubernetes Engine config for Dataproc clusters deployed to Kubernetes. Setting this is considered mutually exclusive with Compute Engine-based options such as
gceClusterConfig, masterConfig, workerConfig, secondaryWorkerConfig, and autoscalingConfig.
final
-
hashCode
→ int
-
The hash code for this object.
no setterinherited
-
initializationActions
→ Input<List<WorkflowTemplatePlacementManagedClusterConfigInitializationAction>?>?
-
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
final
-
lifecycleConfig
→ Input<WorkflowTemplatePlacementManagedClusterConfigLifecycleConfig?>?
-
Lifecycle setting for the cluster.
final
-
masterConfig
→ Input<WorkflowTemplatePlacementManagedClusterConfigMasterConfig?>?
-
The Compute Engine config settings for additional worker instances in a cluster.
final
-
metastoreConfig
→ Input<WorkflowTemplatePlacementManagedClusterConfigMetastoreConfig?>?
-
Metastore configuration.
final
-
runtimeType
→ Type
-
A representation of the runtime type of the object.
no setterinherited
-
secondaryWorkerConfig
→ Input<WorkflowTemplatePlacementManagedClusterConfigSecondaryWorkerConfig?>?
-
The Compute Engine config settings for additional worker instances in a cluster.
final
-
securityConfig
→ Input<WorkflowTemplatePlacementManagedClusterConfigSecurityConfig?>?
-
Security settings for the cluster.
final
-
softwareConfig
→ Input<WorkflowTemplatePlacementManagedClusterConfigSoftwareConfig?>?
-
The config settings for software inside the cluster.
final
-
stagingBucket
→ Input<String?>?
-
A Cloud Storage bucket used to stage job dependencies, config files, and job driver console output. If you do not specify a staging bucket, Cloud Dataproc will determine a Cloud Storage location (US, ASIA, or EU) for your cluster's staging bucket according to the Compute Engine zone where your cluster is deployed, and then create and manage this project-level, per-location bucket (see Dataproc staging and temp buckets).
final
-
tempBucket
→ Input<String?>?
-
A Cloud Storage bucket used to store ephemeral cluster and jobs data, such as Spark and MapReduce history files. If you do not specify a temp bucket, Dataproc will determine a Cloud Storage location (US, ASIA, or EU) for your cluster's temp bucket according to the Compute Engine zone where your cluster is deployed, and then create and manage this project-level, per-location bucket. The default bucket has a TTL of 90 days, but you can use any TTL (or none) if you specify a bucket.
final
-
workerConfig
→ Input<WorkflowTemplatePlacementManagedClusterConfigWorkerConfig?>?
-
The Compute Engine config settings for additional worker instances in a cluster.
final
