Get information on a Dataplatform Node Pool.
The Dataplatform Node Pool Data Source can be used to search for and return an existing Dataplatform Node Pool under a Dataplatform Cluster. If a single match is found, it will be returned. If your search results in multiple matches, an error will be returned. When this happens, please refine your search and make sure that your resources have unique names.
cluster_id
- (Required) ID of the cluster the searched node pool is part of.
id
- (Optional) ID of the node pool you want to search for.
name
- (Optional) Name of an existing cluster that you want to search for. Search by name is case-insensitive. The whole resource name is required if partial_match
parameter is not set to true.
partial_match
- (Optional) Whether partial matching is allowed or not when using name argument. Default value is false.
Either id
or name
must be provided. If none, or both are provided, the datasource will return an error.
The following attributes are returned by the datasource:
cluster_id
- ID of the cluster the searched node pool is part of.
datacenter_id
- The UUID of the virtual data center (VDC) the cluster is provisioned.
id
- ID of your node pool.
name
- The name of your node pool
version
- The version of the Data Platform.
node_count
- The number of nodes that make up the node pool.
cpu_family
- A CPU family.
cores_count
- The number of CPU cores per node.
ram_size
- The RAM size for one node in MB.
availability_zone
- The availability zone of the virtual datacenter region where the node pool resources should be provisioned.
storage_type
- The type of hardware for the volume.
storage_size
- The size of the volume in GB.
maintenance_window
- Starting time of a weekly 4 hour-long window, during which maintenance might occur in hh:mm:ss format
time
- Time at which the maintenance should start.
day_of_the_week
labels
- Key-value pairs attached to the node pool resource as Kubernetes labels.
annotations
- Key-value pairs attached to node pool resource as Kubernetes annotations.
auto_scaling
- Whether the Node Pool should autoscale. For more details, please check the API documentation
min_node_count
- The minimum number of worker nodes the node pool can scale down to. Should be less than max_node_count
max_node_count
- The maximum number of worker nodes that the node pool can scale to. Should be greater than min_node_count