pulumi-gcp-kotlin/com.pulumi.gcp.container.kotlin/NodePool

NodePool

Import

Node pools can be imported using the project, location, cluster and name. If the project is omitted, the project value in the provider configuration will be used. Examples

$ pulumi import gcp:container/nodePool:NodePool mainpool my-gcp-project/us-east1-a/my-cluster/main-pool

$ pulumi import gcp:container/nodePool:NodePool mainpool us-east1/my-cluster/main-pool

Properties

autoscaling

val autoscaling: Output<NodePoolAutoscaling>?

Configuration required by cluster autoscaler to adjust the size of the node pool to the current cluster usage. Structure is documented below.

cluster

val cluster: Output<String>

The cluster to create the node pool for. Cluster must be present in location provided for clusters. May be specified in the format projects/{{project}}/locations/{{location}}/clusters/{{cluster}} or as just the name of the cluster.

val id: Output<String>

initialNodeCount

val initialNodeCount: Output<Int>

The initial number of nodes for the pool. In regional or multi-zonal clusters, this is the number of nodes per zone. Changing this will force recreation of the resource.

instanceGroupUrls

val instanceGroupUrls: Output<List<String>>

The resource URLs of the managed instance groups associated with this node pool.

location

val location: Output<String>

The location (region or zone) of the cluster.

managedInstanceGroupUrls

val managedInstanceGroupUrls: Output<List<String>>

List of instance group URLs which have been assigned to this node pool.

management

val management: Output<NodePoolManagement>

Node management configuration, wherein auto-repair and auto-upgrade is configured. Structure is documented below.

maxPodsPerNode

val maxPodsPerNode: Output<Int>

The maximum number of pods per node in this node pool. Note that this does not work on node pools which are "route-based" - that is, node pools belonging to clusters that do not have IP Aliasing enabled. See the official documentation for more information.

name

val name: Output<String>

The name of the node pool. If left blank, Terraform will auto-generate a unique name.

namePrefix

val namePrefix: Output<String>

Creates a unique name for the node pool beginning with the specified prefix. Conflicts with name.

networkConfig

val networkConfig: Output<NodePoolNetworkConfig>

The network configuration of the pool. Such as configuration for Adding Pod IP address ranges) to the node pool. Or enabling private nodes. Structure is documented below

nodeConfig

val nodeConfig: Output<NodePoolNodeConfig>

Parameters used in creating the node pool. See gcp.container.Cluster for schema.

nodeCount

val nodeCount: Output<Int>

The number of nodes per instance group. This field can be used to update the number of nodes per instance group but should not be used alongside autoscaling.

nodeLocations

val nodeLocations: Output<List<String>>

The list of zones in which the node pool's nodes should be located. Nodes must be in the region of their regional cluster or in the same region as their cluster's zone for zonal clusters. If unspecified, the cluster-level node_locations will be used.

operation

val operation: Output<String>

placementPolicy

val placementPolicy: Output<NodePoolPlacementPolicy>?

Specifies a custom placement policy for the nodes.

project

val project: Output<String>

The ID of the project in which to create the node pool. If blank, the provider-configured project will be used.

pulumiChildResources

val pulumiChildResources: Set<KotlinResource>

pulumiResourceName

val pulumiResourceName: String

pulumiResourceType

val pulumiResourceType: String

upgradeSettings

val upgradeSettings: Output<NodePoolUpgradeSettings>

Specify node upgrade settings to change how GKE upgrades nodes. The maximum number of nodes upgraded simultaneously is limited to 20. Structure is documented below.

urn

val urn: Output<String>

version

val version: Output<String>

The Kubernetes version for the nodes in this pool. Note that if this field and auto_upgrade are both specified, they will fight each other for what the node version should be, so setting both is highly discouraged. While a fuzzy version can be specified, it's recommended that you specify explicit versions as Terraform will see spurious diffs when fuzzy versions are used. See the google_container_engine_versions data source's version_prefix field to approximate fuzzy versions in a Terraform-compatible way.