NodePoolState constructor

const NodePoolState({ Input<NodePoolAutoscaling?>? autoscaling, Input<String?>? cluster, Input<String?>? deletionPolicy, Input<bool?>? ignoreNodeCountChanges, Input<int?>? initialNodeCount, Input<List<String>?>? instanceGroupUrls, Input<String?>? location, Input<List<NodePoolMaintenancePolicy>?>? maintenancePolicies, Input<List<String>?>? managedInstanceGroupUrls, Input<NodePoolManagement?>? management, Input<int?>? maxPodsPerNode, Input<String?>? name, Input<String?>? namePrefix, Input<NodePoolNetworkConfig?>? networkConfig, Input<NodePoolNodeConfig?>? nodeConfig, Input<int?>? nodeCount, Input<List<NodePoolNodeDrainConfig>?>? nodeDrainConfigs, Input<List<String>?>? nodeLocations, Input<String?>? operation, Input<NodePoolPlacementPolicy?>? placementPolicy, Input<String?>? project, Input<NodePoolQueuedProvisioning?>? queuedProvisioning, Input<NodePoolUpgradeSettings?>? upgradeSettings, Input<String?>? version, })

Creates a new NodePoolState. autoscaling Configuration required by cluster autoscaler to adjust cluster 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. deletionPolicy Whether Terraform will be prevented from destroying the resource. Defaults to "DELETE". ignoreNodeCountChanges Whether to ignore external changes (drift) to the node count (e.g. from GKE autoscaling). Setting this to true skips querying Compute Engine Instance Group Managers (IGMs) to determine the current node count on read, which can save API quota and speed up plans on large clusters. Unlike Terraform core's lifecycle { ignoreChanges = [nodeCount] }, this allows configuration-driven scaling updates in your HCL while still ignoring runtime autoscaling drift. initialNodeCount The initial number of nodes for the pool. In instanceGroupUrls The resource URLs of the managed instance groups associated with this node pool. location The location (region or zone) of the cluster. maintenancePolicies The maintenance policy of the pool. Structure is documented below. managedInstanceGroupUrls List of instance group URLs which have been assigned to this node pool. management Node management configuration, wherein auto-repair and maxPodsPerNode The maximum number of pods per node in this node pool. name The name of the node pool. If left blank, the provider will namePrefix Creates a unique name for the node pool beginning networkConfig The network configuration of the pool. Such as nodeConfig Parameters used in creating the node pool. Structure is documented below. See gcp.container.Cluster for exact schema. nodeCount The number of nodes per instance group. This field can be used to nodeDrainConfigs The node drain configuration of the pool. Structure is documented below. nodeLocations The list of zones in which the node pool's nodes should be located. Nodes must operation Optional. placementPolicy Specifies a custom placement policy for the project The ID of the project in which to create the node pool. If blank, queuedProvisioning Specifies node pool-level settings of queued provisioning. upgradeSettings Specify node upgrade settings to change how GKE upgrades nodes. version The Kubernetes version for the nodes in this pool. Note that if this field

Implementation

const NodePoolState({
  this.autoscaling,
  this.cluster,
  this.deletionPolicy,
  this.ignoreNodeCountChanges,
  this.initialNodeCount,
  this.instanceGroupUrls,
  this.location,
  this.maintenancePolicies,
  this.managedInstanceGroupUrls,
  this.management,
  this.maxPodsPerNode,
  this.name,
  this.namePrefix,
  this.networkConfig,
  this.nodeConfig,
  this.nodeCount,
  this.nodeDrainConfigs,
  this.nodeLocations,
  this.operation,
  this.placementPolicy,
  this.project,
  this.queuedProvisioning,
  this.upgradeSettings,
  this.version,
});