--- title: "POST /v1/{+parent}/clusters" method: POST path: "/v1/{+parent}/clusters" tags: ["projects"] --- # POST /v1/{+parent}/clusters `POST /v1/{+parent}/clusters` Creates a cluster, consisting of the specified number and type of Google Compute Engine instances. By default, the cluster is created in the project's [default network](https://cloud.google.com/compute/docs/networks-and-firewalls#networks). One firewall is added for the cluster. After cluster creation, the kubelet creates routes for each node to allow the containers on that node to communicate with all other instances in the cluster. Finally, an entry is added to the project's global metadata indicating which CIDR range the cluster is using. ## Path parameters - `parent` string, required ## Request body - CreateClusterRequest — CreateClusterRequest creates a cluster. - `projectId` string — Deprecated. The Google Developers Console [project ID or project number](https://cloud.google.com/resource-manager/docs/creating-managing-projects). This field has been deprecated and replaced by the parent field. - `zone` string — Deprecated. The name of the Google Compute Engine [zone](https://cloud.google.com/compute/docs/zones#available) in which the cluster resides. This field has been deprecated and replaced by the parent field. - `cluster` Cluster — A Google Kubernetes Engine cluster. - `currentNodeVersion` string — Output only. Deprecated, use [NodePools.version](https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters.nodePools) instead. The current version of the node software components. If they are currently at multiple versions because they're in the process of being upgraded, this reflects the minimum version of all nodes. - `verticalPodAutoscaling` VerticalPodAutoscaling — VerticalPodAutoscaling contains global, per-cluster information required by Vertical Pod Autoscaler to automatically adjust the resources of pods controlled by it. - `enabled` boolean — Enables vertical pod autoscaling. - `identityServiceConfig` IdentityServiceConfig — IdentityServiceConfig is configuration for Identity Service which allows customers to use external identity providers with the K8S API - `enabled` boolean — Whether to enable the Identity Service component - `subnetwork` string — The name of the Google Compute Engine [subnetwork](https://cloud.google.com/compute/docs/subnetworks) to which the cluster is connected. - `id` string — Output only. Unique id for the cluster. - `satisfiesPzs` boolean — Output only. Reserved for future use. - `enterpriseConfig` EnterpriseConfig — EnterpriseConfig is the cluster enterprise configuration. Deprecated: GKE Enterprise features are now available without an Enterprise tier. - `clusterTier` 'CLUSTER_TIER_UNSPECIFIED' | 'STANDARD' | 'ENTERPRISE' — Output only. cluster_tier indicates the effective tier of the cluster. - `desiredTier` 'CLUSTER_TIER_UNSPECIFIED' | 'STANDARD' | 'ENTERPRISE' — desired_tier specifies the desired tier of the cluster. - `description` string — An optional description of this cluster. - `enableTpu` boolean — Enable the ability to use Cloud TPUs in this cluster. This field is deprecated due to the deprecation of 2VM TPU. The end of life date for 2VM TPU is 2025-04-25. - `resourceLabels` object — The resource labels for the cluster to use to annotate any related Google Compute Engine resources. - `costManagementConfig` CostManagementConfig — Configuration for fine-grained cost management feature. - `enabled` boolean — Whether the feature is enabled or not. - `gkeAutoUpgradeConfig` GkeAutoUpgradeConfig — GkeAutoUpgradeConfig is the configuration for GKE auto upgrades. - `patchMode` 'PATCH_MODE_UNSPECIFIED' | 'ACCELERATED' — PatchMode specifies how auto upgrade patch builds should be selected. - `fleet` Fleet — Fleet is the fleet configuration for the cluster. - `preRegistered` boolean — Output only. Whether the cluster has been registered through the fleet API. - `membership` string — Output only. The full resource name of the registered fleet membership of the cluster, in the format `//gkehub.googleapis.com/projects/*/locations/*/memberships/*`. - `membershipType` 'MEMBERSHIP_TYPE_UNSPECIFIED' | 'LIGHTWEIGHT' — The type of the cluster's fleet membership. - `project` string — The Fleet host project(project ID or project number) where this cluster will be registered to. This field cannot be changed after the cluster has been registered. - `rbacBindingConfig` RBACBindingConfig — RBACBindingConfig allows user to restrict ClusterRoleBindings an RoleBindings that can be created. - `enableInsecureBindingSystemAuthenticated` boolean — Setting this to true will allow any ClusterRoleBinding and RoleBinding with subjects system:authenticated. - `enableInsecureBindingSystemUnauthenticated` boolean — Setting this to true will allow any ClusterRoleBinding and RoleBinding with subjets system:anonymous or system:unauthenticated. - `secretSyncConfig` SecretSyncConfig — Configuration for sync Secret Manager secrets as k8s secrets. - `rotationConfig` SyncRotationConfig — SyncRotationConfig is config for secret manager auto rotation. - `rotationInterval` string, google-duration — The interval between two consecutive rotations. Default rotation interval is 2 minutes. - `enabled` boolean — Whether the rotation is enabled. - `enabled` boolean — Enable/Disable Secret Sync Config. - `parentProductConfig` ParentProductConfig — ParentProductConfig is the configuration of the parent product of the cluster. This field is used by Google internal products that are built on top of a GKE cluster and take the ownership of the cluster. - `productName` string — Name of the parent product associated with the cluster. - `labels` object — Labels contain the configuration of the parent product. - `shieldedNodes` ShieldedNodes — Configuration of Shielded Nodes feature. - `enabled` boolean — Whether Shielded Nodes features are enabled on all nodes in this cluster. - `currentEmulatedVersion` string — Output only. The current emulated version of the master endpoint. The version is in minor version format, e.g. 1.30. No value or empty string means the cluster has no emulated version. - `status` 'STATUS_UNSPECIFIED' | 'PROVISIONING' | 'RUNNING' | 'RECONCILING' | 'STOPPING' | 'ERROR' | 'DEGRADED' — Output only. The current status of this cluster. - `locations` string[] — The list of Google Compute Engine [zones](https://cloud.google.com/compute/docs/zones#available) in which the cluster's nodes should be located. This field provides a default value if [NodePool.Locations](https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters.nodePools#NodePool.FIELDS.locations) are not specified during node pool creation. Warning: changing cluster locations will update the [NodePool.Locations](https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters.nodePools#NodePool.FIELDS.locations) of all node pools and will result in nodes being added and/or removed. - `enableKubernetesAlpha` boolean — Kubernetes alpha features are enabled on this cluster. This includes alpha API groups (e.g. v1alpha1) and features that may not be production ready in the kubernetes version of the master and nodes. The cluster has no SLA for uptime and master/node upgrades are disabled. Alpha enabled clusters are automatically deleted thirty days after creation. - `location` string — Output only. The name of the Google Compute Engine [zone](https://cloud.google.com/compute/docs/regions-zones/regions-zones#available) or [region](https://cloud.google.com/compute/docs/regions-zones/regions-zones#available) in which the cluster resides. - `etag` string — This checksum is computed by the server based on the value of cluster fields, and may be sent on update requests to ensure the client has an up-to-date value before proceeding. - `managedMachineLearningDiagnosticsConfig` ManagedMachineLearningDiagnosticsConfig — ManagedMachineLearningDiagnosticsConfig is the configuration for the GKE Managed Machine Learning Diagnostics pipeline. - `enabled` boolean — Enable/Disable Managed Machine Learning Diagnostics. - `alphaClusterFeatureGates` string[] — The list of user specified Kubernetes feature gates. Each string represents the activation status of a feature gate (e.g. "featureX=true" or "featureX=false") - `autoscaling` ClusterAutoscaling — ClusterAutoscaling contains global, per-cluster information required by Cluster Autoscaler to automatically adjust the size of the cluster and create/delete node pools based on the current needs. - `autoprovisioningNodePoolDefaults` AutoprovisioningNodePoolDefaults — AutoprovisioningNodePoolDefaults contains defaults for a node pool created by NAP. - `diskSizeGb` integer — Size of the disk attached to each node, specified in GB. The smallest allowed disk size is 10GB. If unspecified, the default disk size is 100GB. - `management` NodeManagement — NodeManagement defines the set of node management services turned on for the node pool. - `autoRepair` boolean — A flag that specifies whether the node auto-repair is enabled for the node pool. If enabled, the nodes in this node pool will be monitored and, if they fail health checks too many times, an automatic repair action will be triggered. - `upgradeOptions` AutoUpgradeOptions — AutoUpgradeOptions defines the set of options for the user to control how the Auto Upgrades will proceed. - `autoUpgradeStartTime` string — Output only. This field is set when upgrades are about to commence with the approximate start time for the upgrades, in [RFC3339](https://www.ietf.org/rfc/rfc3339.txt) text format. - `description` string — Output only. This field is set when upgrades are about to commence with the description of the upgrade. - `autoUpgrade` boolean — A flag that specifies whether node auto-upgrade is enabled for the node pool. If enabled, node auto-upgrade helps keep the nodes in your node pool up to date with the latest release version of Kubernetes. - `upgradeSettings` UpgradeSettings — These upgrade settings control the level of parallelism and the level of disruption caused by an upgrade. maxUnavailable controls the number of nodes that can be simultaneously unavailable. maxSurge controls the number of additional nodes that can be added to the node pool temporarily for the time of the upgrade to increase the number of available nodes. (maxUnavailable + maxSurge) determines the level of parallelism (how many nodes are being upgraded at the same time). Note: upgrades inevitably introduce some disruption since workloads need to be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, this holds true. (Disruption stays within the limits of PodDisruptionBudget, if it is configured.) Consider a hypothetical node pool with 5 nodes having maxSurge=2, maxUnavailable=1. This means the upgrade process upgrades 3 nodes simultaneously. It creates 2 additional (upgraded) nodes, then it brings down 3 old (not yet upgraded) nodes at the same time. This ensures that there are always at least 4 nodes available. These upgrade settings configure the upgrade strategy for the node pool. Use strategy to switch between the strategies applied to the node pool. If the strategy is ROLLING, use max_surge and max_unavailable to control the level of parallelism and the level of disruption caused by upgrade. 1. maxSurge controls the number of additional nodes that can be added to the node pool temporarily for the time of the upgrade to increase the number of available nodes. 2. maxUnavailable controls the number of nodes that can be simultaneously unavailable. 3. (maxUnavailable + maxSurge) determines the level of parallelism (how many nodes are being upgraded at the same time). If the strategy is BLUE_GREEN, use blue_green_settings to configure the blue-green upgrade related settings. 1. standard_rollout_policy is the default policy. The policy is used to control the way blue pool gets drained. The draining is executed in the batch mode. The batch size could be specified as either percentage of the node pool size or the number of nodes. batch_soak_duration is the soak time after each batch gets drained. 2. node_pool_soak_duration is the soak time after all blue nodes are drained. After this period, the blue pool nodes will be deleted. - `maxUnavailable` integer — The maximum number of nodes that can be simultaneously unavailable during the upgrade process. A node is considered available if its status is Ready. - `maxSurge` integer — The maximum number of nodes that can be created beyond the current size of the node pool during the upgrade process. - `blueGreenSettings` BlueGreenSettings — Settings for blue-green upgrade. - `standardRolloutPolicy` StandardRolloutPolicy — Standard rollout policy is the default policy for blue-green. - … - `autoscaledRolloutPolicy` AutoscaledRolloutPolicy — Autoscaled rollout policy utilizes the cluster autoscaler during blue-green upgrade to scale both the blue and green pools. - … - `nodePoolSoakDuration` string, google-duration — Time needed after draining entire blue pool. After this period, blue pool will be cleaned up. - `strategy` 'NODE_POOL_UPDATE_STRATEGY_UNSPECIFIED' | 'BLUE_GREEN' | 'SURGE' | 'SHORT_LIVED' — Update strategy of the node pool. - `serviceAccount` string — The Google Cloud Platform Service Account to be used by the node VMs. - `shieldedInstanceConfig` ShieldedInstanceConfig — A set of Shielded Instance options. - `enableIntegrityMonitoring` boolean — Defines whether the instance has integrity monitoring enabled. Enables monitoring and attestation of the boot integrity of the instance. The attestation is performed against the integrity policy baseline. This baseline is initially derived from the implicitly trusted boot image when the instance is created. - `enableSecureBoot` boolean — Defines whether the instance has Secure Boot enabled. Secure Boot helps ensure that the system only runs authentic software by verifying the digital signature of all boot components, and halting the boot process if signature verification fails. - `diskType` string — Type of the disk attached to each node (e.g. 'pd-standard', 'pd-ssd' or 'pd-balanced') If unspecified, the default disk type is 'pd-standard' - `imageType` string — The image type to use for NAP created node. Please see https://cloud.google.com/kubernetes-engine/docs/concepts/node-images for available image types. - `insecureKubeletReadonlyPortEnabled` boolean — DEPRECATED. Use NodePoolAutoConfig.NodeKubeletConfig instead. - `bootDiskKmsKey` string — The Customer Managed Encryption Key used to encrypt the boot disk attached to each node in the node pool. This should be of the form projects/[KEY_PROJECT_ID]/locations/[LOCATION]/keyRings/[RING_NAME]/cryptoKeys/[KEY_NAME]. For more information about protecting resources with Cloud KMS Keys please see: https://cloud.google.com/compute/docs/disks/customer-managed-encryption - `minCpuPlatform` string — Deprecated. Minimum CPU platform to be used for NAP created node pools. The instance may be scheduled on the specified or newer CPU platform. Applicable values are the friendly names of CPU platforms, such as minCpuPlatform: Intel Haswell or minCpuPlatform: Intel Sandy Bridge. For more information, read [how to specify min CPU platform](https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform). This field is deprecated, min_cpu_platform should be specified using `cloud.google.com/requested-min-cpu-platform` label selector on the pod. To unset the min cpu platform field pass "automatic" as field value. - `oauthScopes` string[] — Scopes that are used by NAP when creating node pools. - `defaultComputeClassConfig` DefaultComputeClassConfig — DefaultComputeClassConfig defines default compute class configuration. - `enabled` boolean — Enables default compute class. - `resourceLimits` ResourceLimit[] — Contains global constraints regarding minimum and maximum amount of resources in the cluster. - `resourceType` string — Resource name "cpu", "memory" or gpu-specific string. - `minimum` string, int64 — Minimum amount of the resource in the cluster. - `maximum` string, int64 — Maximum amount of the resource in the cluster. - `autoscalingProfile` 'PROFILE_UNSPECIFIED' | 'OPTIMIZE_UTILIZATION' | 'BALANCED' — Defines autoscaling behaviour. - `autoprovisioningLocations` string[] — The list of Google Compute Engine [zones](https://cloud.google.com/compute/docs/zones#available) in which the NodePool's nodes can be created by NAP. - `enableNodeAutoprovisioning` boolean — Enables automatic node pool creation and deletion. - `autopilotGeneralProfile` 'AUTOPILOT_GENERAL_PROFILE_UNSPECIFIED' | 'NO_PERFORMANCE' | 'NONE' — Autopilot general profile for the cluster, which defines the configuration for the cluster. - `confidentialNodes` ConfidentialNodes — ConfidentialNodes is configuration for the confidential nodes feature, which makes nodes run on confidential VMs. - `confidentialInstanceType` 'CONFIDENTIAL_INSTANCE_TYPE_UNSPECIFIED' | 'SEV' | 'SEV_SNP' | 'TDX' — Defines the type of technology used by the confidential node. - `enabled` boolean — Whether Confidential Nodes feature is enabled. - `selfLink` string — Output only. Server-defined URL for the resource. - `ipAllocationPolicy` IPAllocationPolicy — Configuration for controlling how IPs are allocated in the cluster. - `useIpAliases` boolean — Whether alias IPs will be used for pod IPs in the cluster. This is used in conjunction with use_routes. It cannot be true if use_routes is true. If both use_ip_aliases and use_routes are false, then the server picks the default IP allocation mode - `clusterIpv4Cidr` string — This field is deprecated, use cluster_ipv4_cidr_block. - `useRoutes` boolean — Whether routes will be used for pod IPs in the cluster. This is used in conjunction with use_ip_aliases. It cannot be true if use_ip_aliases is true. If both use_ip_aliases and use_routes are false, then the server picks the default IP allocation mode - `servicesIpv4Cidr` string — This field is deprecated, use services_ipv4_cidr_block. - `createSubnetwork` boolean — Whether a new subnetwork will be created automatically for the cluster. This field is only applicable when `use_ip_aliases` is true. - `servicesIpv4CidrBlock` string — The IP address range of the services IPs in this cluster. If blank, a range will be automatically chosen with the default size. This field is only applicable when `use_ip_aliases` is true. Set to blank to have a range chosen with the default size. Set to /netmask (e.g. `/14`) to have a range chosen with a specific netmask. Set to a [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) notation (e.g. `10.96.0.0/14`) from the RFC-1918 private networks (e.g. `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`) to pick a specific range to use. - `clusterIpv4CidrBlock` string — The IP address range for the cluster pod IPs. If this field is set, then `cluster.cluster_ipv4_cidr` must be left blank. This field is only applicable when `use_ip_aliases` is true. Set to blank to have a range chosen with the default size. Set to /netmask (e.g. `/14`) to have a range chosen with a specific netmask. Set to a [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) notation (e.g. `10.96.0.0/14`) from the RFC-1918 private networks (e.g. `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`) to pick a specific range to use. - `tpuIpv4CidrBlock` string — The IP address range of the Cloud TPUs in this cluster. If unspecified, a range will be automatically chosen with the default size. This field is only applicable when `use_ip_aliases` is true. If unspecified, the range will use the default size. Set to /netmask (e.g. `/14`) to have a range chosen with a specific netmask. Set to a [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) notation (e.g. `10.96.0.0/14`) from the RFC-1918 private networks (e.g. `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`) to pick a specific range to use. This field is deprecated due to the deprecation of 2VM TPU. The end of life date for 2VM TPU is 2025-04-25. - `subnetIpv6CidrBlock` string — Output only. The subnet's IPv6 CIDR block used by nodes and pods. - `ipv6AccessType` 'IPV6_ACCESS_TYPE_UNSPECIFIED' | 'INTERNAL' | 'EXTERNAL' — The ipv6 access type (internal or external) when create_subnetwork is true - `networkTierConfig` NetworkTierConfig — NetworkTierConfig contains network tier information. - `networkTier` 'NETWORK_TIER_UNSPECIFIED' | 'NETWORK_TIER_DEFAULT' | 'NETWORK_TIER_PREMIUM' | 'NETWORK_TIER_STANDARD' — Network tier configuration. - `additionalIpRangesConfigs` AdditionalIPRangesConfig[] — Output only. The additional IP ranges that are added to the cluster. These IP ranges can be used by new node pools to allocate node and pod IPs automatically. Each AdditionalIPRangesConfig corresponds to a single subnetwork. Once a range is removed it will not show up in IPAllocationPolicy. - `subnetwork` string — Name of the subnetwork. This can be the full path of the subnetwork or just the name. Example1: my-subnet Example2: projects/gke-project/regions/us-central1/subnetworks/my-subnet - `podIpv4RangeNames` string[] — List of secondary ranges names within this subnetwork that can be used for pod IPs. Example1: gke-pod-range1 Example2: gke-pod-range1,gke-pod-range2 - `status` 'STATUS_UNSPECIFIED' | 'ACTIVE' | 'DRAINING' — Draining status of the additional subnet. - `servicesIpv6CidrBlock` string — Output only. The services IPv6 CIDR block for the cluster. - `servicesSecondaryRangeName` string — The name of the secondary range to be used as for the services CIDR block. The secondary range will be used for service ClusterIPs. This must be an existing secondary range associated with the cluster subnetwork. This field is only applicable with use_ip_aliases is true and create_subnetwork is false. - `nodeIpv4CidrBlock` string — The IP address range of the instance IPs in this cluster. This is applicable only if `create_subnetwork` is true. Set to blank to have a range chosen with the default size. Set to /netmask (e.g. `/14`) to have a range chosen with a specific netmask. Set to a [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) notation (e.g. `10.96.0.0/14`) from the RFC-1918 private networks (e.g. `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`) to pick a specific range to use. - `clusterSecondaryRangeName` string — The name of the secondary range to be used for the cluster CIDR block. The secondary range will be used for pod IP addresses. This must be an existing secondary range associated with the cluster subnetwork. This field is only applicable with use_ip_aliases is true and create_subnetwork is false. - `defaultPodIpv4RangeUtilization` number, double — Output only. The utilization of the cluster default IPv4 range for the pod. The ratio is Usage/[Total number of IPs in the secondary range], Usage=numNodes*numZones*podIPsPerNode. - `nodeIpv4Cidr` string — This field is deprecated, use node_ipv4_cidr_block. - `subnetworkName` string — A custom subnetwork name to be used if `create_subnetwork` is true. If this field is empty, then an automatic name will be chosen for the new subnetwork. - `podCidrOverprovisionConfig` PodCIDROverprovisionConfig — [PRIVATE FIELD] Config for pod CIDR size overprovisioning. - `disable` boolean — Whether Pod CIDR overprovisioning is disabled. Note: Pod CIDR overprovisioning is enabled by default. - `autoIpamConfig` AutoIpamConfig — AutoIpamConfig contains all information related to Auto IPAM - `enabled` boolean — The flag that enables Auto IPAM on this cluster - `additionalPodRangesConfig` AdditionalPodRangesConfig — AdditionalPodRangesConfig is the configuration for additional pod secondary ranges supporting the ClusterUpdate message. - `podRangeNames` string[] — Name for pod secondary ipv4 range which has the actual range defined ahead. - `podRangeInfo` RangeInfo[] — Output only. Information for additional pod range. - `rangeName` string — Output only. Name of a range. - `utilization` number, double — Output only. The utilization of the range. - `stackType` 'STACK_TYPE_UNSPECIFIED' | 'IPV4' | 'IPV4_IPV6' — The IP stack type of the cluster - `compliancePostureConfig` CompliancePostureConfig — Deprecated: Compliance Posture is no longer supported. For more details, see https://cloud.google.com/kubernetes-engine/docs/deprecations/posture-management-deprecation. CompliancePostureConfig defines the settings needed to enable/disable features for the Compliance Posture. - `complianceStandards` ComplianceStandard[] — List of enabled compliance standards. - `standard` string — Name of the compliance standard. - `mode` 'MODE_UNSPECIFIED' | 'DISABLED' | 'ENABLED' — Defines the enablement mode for Compliance Posture. - `addonsConfig` AddonsConfig — Configuration for the addons that can be automatically spun up in the cluster, enabling additional functionality. - `configConnectorConfig` ConfigConnectorConfig — Configuration options for the Config Connector add-on. - `enabled` boolean — Whether Cloud Connector is enabled for this cluster. - `gcpFilestoreCsiDriverConfig` GcpFilestoreCsiDriverConfig — Configuration for the Filestore CSI driver. - `enabled` boolean — Whether the Filestore CSI driver is enabled for this cluster. - `kubernetesDashboard` KubernetesDashboard — Configuration for the Kubernetes Dashboard. - `disabled` boolean — Whether the Kubernetes Dashboard is enabled for this cluster. - `statefulHaConfig` StatefulHAConfig — Configuration for the Stateful HA add-on. - `enabled` boolean — Whether the Stateful HA add-on is enabled for this cluster. - `slurmOperatorConfig` SlurmOperatorConfig — Configuration for the Slurm Operator. - `enabled` boolean — When enabled, it runs a Slurm Operator that manages the set of compute pods for Slurm Cluster. - `nodeReadinessConfig` NodeReadinessConfig — Configuration for the GKE Node Readiness Controller. - `enabled` boolean — Optional. Whether the GKE Node Readiness Controller is enabled for this cluster. - `agentSandboxConfig` AgentSandboxConfig — Configuration for the AgentSandbox addon. - `enabled` boolean — Optional. Whether AgentSandbox is enabled for this cluster. - `horizontalPodAutoscaling` HorizontalPodAutoscaling — Configuration options for the horizontal pod autoscaling feature, which increases or decreases the number of replica pods a replication controller has based on the resource usage of the existing pods. - `disabled` boolean — Whether the Horizontal Pod Autoscaling feature is enabled in the cluster. When enabled, it ensures that metrics are collected into Stackdriver Monitoring. - `gkeBackupAgentConfig` GkeBackupAgentConfig — Configuration for the Backup for GKE Agent. - `enabled` boolean — Whether the Backup for GKE agent is enabled for this cluster. - `networkPolicyConfig` NetworkPolicyConfig — Configuration for NetworkPolicy. This only tracks whether the addon is enabled or not on the Master, it does not track whether network policy is enabled for the nodes. - `disabled` boolean — Whether NetworkPolicy is enabled for this cluster. - `lustreCsiDriverConfig` LustreCsiDriverConfig — Configuration for the Lustre CSI driver. - `enabled` boolean — Whether the Lustre CSI driver is enabled for this cluster. - `enableLegacyLustrePort` boolean — If set to true, the Lustre CSI driver will install Lustre kernel modules using port 6988. This serves as a workaround for a port conflict with the gke-metadata-server. This field is required ONLY under the following conditions: 1. The GKE node version is older than 1.33.2-gke.4655000. 2. You're connecting to a Lustre instance that has the 'gke-support-enabled' flag. Deprecated: This flag is no longer required as of GKE node version 1.33.2-gke.4655000, unless you are connecting to a Lustre instance that has the `gke-support-enabled` flag. - `disableMultiNic` boolean — When set to true, this disables multi-NIC support for the Lustre CSI driver. By default, GKE enables multi-NIC support, which allows the Lustre CSI driver to automatically detect and configure all suitable network interfaces on a node to maximize I/O performance for demanding workloads. - `cloudRunConfig` CloudRunConfig — Configuration options for the Cloud Run feature. - `disabled` boolean — Whether Cloud Run addon is enabled for this cluster. - `loadBalancerType` 'LOAD_BALANCER_TYPE_UNSPECIFIED' | 'LOAD_BALANCER_TYPE_EXTERNAL' | 'LOAD_BALANCER_TYPE_INTERNAL' — Which load balancer type is installed for Cloud Run. - `gcePersistentDiskCsiDriverConfig` GcePersistentDiskCsiDriverConfig — Configuration for the Compute Engine PD CSI driver. - `enabled` boolean — Whether the Compute Engine PD CSI driver is enabled for this cluster. - `httpLoadBalancing` HttpLoadBalancing — Configuration options for the HTTP (L7) load balancing controller addon, which makes it easy to set up HTTP load balancers for services in a cluster. - `disabled` boolean — Whether the HTTP Load Balancing controller is enabled in the cluster. When enabled, it runs a small pod in the cluster that manages the load balancers. - `parallelstoreCsiDriverConfig` ParallelstoreCsiDriverConfig — Configuration for the Cloud Storage Parallelstore CSI driver. - `enabled` boolean — Whether the Cloud Storage Parallelstore CSI driver is enabled for this cluster. - `rayOperatorConfig` RayOperatorConfig — Configuration options for the Ray Operator add-on. - `enabled` boolean — Whether the Ray Operator addon is enabled for this cluster. - `rayClusterMonitoringConfig` RayClusterMonitoringConfig — RayClusterMonitoringConfig specifies monitoring configuration for Ray clusters. - `enabled` boolean — Enable metrics collection for Ray clusters. - `rayClusterLoggingConfig` RayClusterLoggingConfig — RayClusterLoggingConfig specifies configuration of Ray logging. - `enabled` boolean — Enable log collection for Ray clusters. - `sliceControllerConfig` SliceControllerConfig — Configuration for the Slice Controller. - `enabled` boolean — Optional. Indicates whether Slice Controller is enabled in the cluster. - `highScaleCheckpointingConfig` HighScaleCheckpointingConfig — Configuration for the High Scale Checkpointing. - `enabled` boolean — Whether the High Scale Checkpointing is enabled for this cluster. - `dnsCacheConfig` DnsCacheConfig — Configuration for NodeLocal DNSCache - `enabled` boolean — Whether NodeLocal DNSCache is enabled for this cluster. - `gcsFuseCsiDriverConfig` GcsFuseCsiDriverConfig — Configuration for the Cloud Storage Fuse CSI driver. - `enabled` boolean — Whether the Cloud Storage Fuse CSI driver is enabled for this cluster. - `podSnapshotConfig` PodSnapshotConfig — PodSnapshotConfig is the configuration for GKE Pod Snapshots feature. - `enabled` boolean — Whether or not the Pod Snapshots feature is enabled. - `expireTime` string — Output only. The time the cluster will be automatically deleted in [RFC3339](https://www.ietf.org/rfc/rfc3339.txt) text format. - `databaseEncryption` DatabaseEncryption — Configuration of etcd encryption. - `state` 'UNKNOWN' | 'ENCRYPTED' | 'DECRYPTED' | 'ALL_OBJECTS_ENCRYPTION_ENABLED' — The desired state of etcd encryption. - `keyName` string — Name of CloudKMS key to use for the encryption of secrets in etcd. Ex. projects/my-project/locations/global/keyRings/my-ring/cryptoKeys/my-key - `currentState` 'CURRENT_STATE_UNSPECIFIED' | 'CURRENT_STATE_ENCRYPTED' | 'CURRENT_STATE_DECRYPTED' | 'CURRENT_STATE_ENCRYPTION_PENDING' | 'CURRENT_STATE_ENCRYPTION_ERROR' | 'CURRENT_STATE_DECRYPTION_PENDING' | 'CURRENT_STATE_DECRYPTION_ERROR' | 'CURRENT_STATE_ALL_OBJECTS_ENCRYPTION_ENABLED' | 'CURRENT_STATE_ALL_OBJECTS_ENCRYPTION_PENDING' | 'CURRENT_STATE_ALL_OBJECTS_ENCRYPTION_ERROR' — Output only. The current state of etcd encryption. - `decryptionKeys` string[] — Output only. Keys in use by the cluster for decrypting existing objects, in addition to the key in `key_name`. Each item is a CloudKMS key resource. - `lastOperationErrors` OperationError[] — Output only. Records errors seen during DatabaseEncryption update operations. - `keyName` string — CloudKMS key resource that had the error. - `errorMessage` string — Description of the error seen during the operation. - `timestamp` string, google-datetime — Time when the CloudKMS error was seen. - `rollbackSafeUpgrade` RollbackSafeUpgrade — RollbackSafeUpgrade is the configuration for the rollback safe upgrade. - `controlPlaneSoakDuration` string, google-duration — Optional. A user-defined period for the cluster remains in the rollbackable state. ex: {seconds: 21600}. - `resourceUsageExportConfig` ResourceUsageExportConfig — Configuration for exporting cluster resource usages. - `enableNetworkEgressMetering` boolean — Whether to enable network egress metering for this cluster. If enabled, a daemonset will be created in the cluster to meter network egress traffic. - `bigqueryDestination` BigQueryDestination — Parameters for using BigQuery as the destination of resource usage export. - `datasetId` string — The ID of a BigQuery Dataset. - `consumptionMeteringConfig` ConsumptionMeteringConfig — Parameters for controlling consumption metering. - `enabled` boolean — Whether to enable consumption metering for this cluster. If enabled, a second BigQuery table will be created to hold resource consumption records. - `zone` string — Output only. The name of the Google Compute Engine [zone](https://cloud.google.com/compute/docs/zones#available) in which the cluster resides. This field is deprecated, use location instead. - `nodeIpv4CidrSize` integer — Output only. The size of the address space on each node for hosting containers. This is provisioned from within the `container_ipv4_cidr` range. This field will only be set when cluster is in route-based network mode. - `authenticatorGroupsConfig` AuthenticatorGroupsConfig — Configuration for returning group information from authenticators. - `securityGroup` string — The name of the security group-of-groups to be used. Only relevant if enabled = true. - `enabled` boolean — Whether this cluster should return group membership lookups during authentication using a group of security groups. - `currentMasterVersion` string — Output only. The current software version of the master endpoint. - `conditions` StatusCondition[] — Which conditions caused the current cluster state. - `code` 'UNKNOWN' | 'GCE_STOCKOUT' | 'GKE_SERVICE_ACCOUNT_DELETED' | 'GCE_QUOTA_EXCEEDED' | 'SET_BY_OPERATOR' | 'CLOUD_KMS_KEY_ERROR' | 'CA_EXPIRING' | 'NODE_SERVICE_ACCOUNT_MISSING_PERMISSIONS' | 'CLOUD_KMS_KEY_DESTROYED' — Machine-friendly representation of the condition Deprecated. Use canonical_code instead. - `message` string — Human-friendly representation of the condition - `canonicalCode` 'OK' | 'CANCELLED' | 'UNKNOWN' | 'INVALID_ARGUMENT' | 'DEADLINE_EXCEEDED' | 'NOT_FOUND' | 'ALREADY_EXISTS' | 'PERMISSION_DENIED' | 'UNAUTHENTICATED' | 'RESOURCE_EXHAUSTED' | 'FAILED_PRECONDITION' | 'ABORTED' | 'OUT_OF_RANGE' | 'UNIMPLEMENTED' | 'INTERNAL' | 'UNAVAILABLE' | 'DATA_LOSS' — Canonical code of the condition. - `endpoint` string — Output only. The IP address of this cluster's master endpoint. The endpoint can be accessed from the internet at `https://username:password@endpoint/`. See the `masterAuth` property of this resource for username and password information. - `currentNodeCount` integer — Output only. The number of nodes currently in the cluster. Deprecated. Call Kubernetes API directly to retrieve node information. - `podAutoscaling` PodAutoscaling — PodAutoscaling is used for configuration of parameters for workload autoscaling. - `hpaProfile` 'HPA_PROFILE_UNSPECIFIED' | 'NONE' | 'PERFORMANCE' — Selected Horizontal Pod Autoscaling profile. - `scheduleUpgradeConfig` ScheduleUpgradeConfig — Configuration for scheduled upgrades on the cluster. - `enabled` boolean — Optional. Whether or not scheduled upgrades are enabled. - `initialNodeCount` integer — The number of nodes to create in this cluster. You must ensure that your Compute Engine [resource quota](https://cloud.google.com/compute/quotas) is sufficient for this number of instances. You must also have available firewall and routes quota. For requests, this field should only be used in lieu of a "node_pool" object, since this configuration (along with the "node_config") will be used to create a "NodePool" object with an auto-generated name. Do not use this and a node_pool at the same time. This field is deprecated, use node_pool.initial_node_count instead. - `initialClusterVersion` string — The initial Kubernetes version for this cluster. Valid versions are those found in validMasterVersions returned by getServerConfig. The version can be upgraded over time; such upgrades are reflected in currentMasterVersion and currentNodeVersion. Users may specify either explicit versions offered by Kubernetes Engine or version aliases, which have the following behavior: - "latest": picks the highest valid Kubernetes version - "1.X": picks the highest valid patch+gke.N patch in the 1.X version - "1.X.Y": picks the highest valid gke.N patch in the 1.X.Y version - "1.X.Y-gke.N": picks an explicit Kubernetes version - "","-": picks the default Kubernetes version - `nodePoolAutoConfig` NodePoolAutoConfig — Node pool configs that apply to all auto-provisioned node pools in autopilot clusters and node auto-provisioning enabled clusters. - `linuxNodeConfig` LinuxNodeConfig — Parameters that can be configured on Linux nodes. - `hugepages` HugepagesConfig — Hugepages amount in both 2m and 1g size - `hugepageSize2m` integer — Optional. Amount of 2M hugepages - `hugepageSize1g` integer — Optional. Amount of 1G hugepages - `nodeKernelModuleLoading` NodeKernelModuleLoading — Configuration for kernel module loading on nodes. - `policy` 'POLICY_UNSPECIFIED' | 'ENFORCE_SIGNED_MODULES' | 'DO_NOT_ENFORCE_SIGNED_MODULES' — Set the node module loading policy for nodes in the node pool. - `accurateTimeConfig` AccurateTimeConfig — AccurateTimeConfig contains configuration for the accurate time synchronization feature. - `enablePtpKvmTimeSync` boolean — Enables enhanced time synchronization using PTP-KVM. - `transparentHugepageDefrag` 'TRANSPARENT_HUGEPAGE_DEFRAG_UNSPECIFIED' | 'TRANSPARENT_HUGEPAGE_DEFRAG_ALWAYS' | 'TRANSPARENT_HUGEPAGE_DEFRAG_DEFER' | 'TRANSPARENT_HUGEPAGE_DEFRAG_DEFER_WITH_MADVISE' | 'TRANSPARENT_HUGEPAGE_DEFRAG_MADVISE' | 'TRANSPARENT_HUGEPAGE_DEFRAG_NEVER' — Optional. Defines the transparent hugepage defrag configuration on the node. VM hugepage allocation can be managed by either limiting defragmentation for delayed allocation or skipping it entirely for immediate allocation only. See https://docs.kernel.org/admin-guide/mm/transhuge.html for more details. - `swapConfig` SwapConfig — Configuration for swap memory on a node pool. - `encryptionConfig` EncryptionConfig — Defines encryption settings for the swap space. - `disabled` boolean — Optional. If true, swap space will not be encrypted. Defaults to false (encrypted). - `ephemeralLocalSsdProfile` EphemeralLocalSsdProfile — Swap on the local SSD shared with pod ephemeral storage. - `swapSizeGib` string, int64 — Specifies the size of the swap space in gibibytes (GiB). - `swapSizePercent` integer — Specifies the size of the swap space as a percentage of the ephemeral local SSD capacity. - `enabled` boolean — Optional. Enables or disables swap for the node pool. - `bootDiskProfile` BootDiskProfile — Swap on the node's boot disk. - `swapSizeGib` string, int64 — Specifies the size of the swap space in gibibytes (GiB). - `swapSizePercent` integer — Specifies the size of the swap space as a percentage of the boot disk size. - `dedicatedLocalSsdProfile` DedicatedLocalSsdProfile — Provisions a new, separate local NVMe SSD exclusively for swap. - `diskCount` string, int64 — The number of physical local NVMe SSD disks to attach. - `customNodeInit` CustomNodeInit — Support for running custom init code while bootstrapping nodes. - `initScript` InitScript — InitScript provide a simply bash script to be executed on the node. - `gcsUri` string — The Cloud Storage URI for storing the init script. Format: gs://BUCKET_NAME/OBJECT_NAME The service account on the node pool must have read access to the object. User can't configure both gcs_uri and gcp_secret_manager_secret_uri. - `args` string[] — Optional. The optional arguments line to be passed to the init script. - `gcsGeneration` string, int64 — The generation of the init script stored in Gloud Storage. This is the required field to identify the version of the init script. User can get the genetaion from `gcloud storage objects describe gs://BUCKET_NAME/OBJECT_NAME --format="value(generation)"` or from the "Version history" tab of the object in the Cloud Console UI. - `gcpSecretManagerSecretUri` string — The resource name of the secret manager secret hosting the init script. Both global and regional secrets are supported with format below: Global secret: projects/{project}/secrets/{secret}/versions/{version} Regional secret: projects/{project}/locations/{location}/secrets/{secret}/versions/{version} Example: projects/1234567890/secrets/script_1/versions/1. Accept version number only, not support version alias. User can't configure both gcp_secret_manager_secret_uri and gcs_uri. - `diskIoScheduler` DiskIoScheduler — DiskIoScheduler contains the configuration for the disk IO scheduler. - `nodeSystemIoScheduler` string — Optional. Configures the IO scheduler for the boot disk or ephemeral lssd that runs node system workloads. Supported values are `mq-deadline`, `bfq`, `kyber`, `none`. - `nodeAttachedDiskIoScheduler` string — Optional. Configures the IO scheduler for the attached disks. Supported values are `mq-deadline`, `bfq`, `kyber`, `none`. - `transparentHugepageEnabled` 'TRANSPARENT_HUGEPAGE_ENABLED_UNSPECIFIED' | 'TRANSPARENT_HUGEPAGE_ENABLED_ALWAYS' | 'TRANSPARENT_HUGEPAGE_ENABLED_MADVISE' | 'TRANSPARENT_HUGEPAGE_ENABLED_NEVER' — Optional. Transparent hugepage support for anonymous memory can be entirely disabled (mostly for debugging purposes) or only enabled inside MADV_HUGEPAGE regions (to avoid the risk of consuming more memory resources) or enabled system wide. See https://docs.kernel.org/admin-guide/mm/transhuge.html for more details. - `nodeVfioConfig` NodeVfioConfig — Configuration settings for VFIO (Virtual Function I/O) on a node. VFIO allows safe, unprivileged, userspace drivers to access I/O devices. - `dmaEntryLimit` integer — Optional. Specifies the maximum number of DMA entries (pages) that can be mapped by the VFIO IOMMU type 1 driver for a container. This limit affects the total amount of host memory that can be pinned for direct device access, which is often critical for high-performance devices like TPUs and GPUs. This setting corresponds to the kernel parameter at: `/sys/module/vfio_iommu_type1/parameters/dma_entry_limit`. The default value in the kernel is `65535`. Higher values may be needed for workloads mapping large memory regions. Supported values are integers between `65535` and `4194304`. - `sysctls` object — The Linux kernel parameters to be applied to the nodes and all pods running on the nodes. The following parameters are supported. net.core.busy_poll net.core.busy_read net.core.netdev_max_backlog net.core.rmem_max net.core.rmem_default net.core.wmem_default net.core.wmem_max net.core.optmem_max net.core.somaxconn net.ipv4.neigh.default.gc_thresh1 net.ipv4.neigh.default.gc_thresh2 net.ipv4.neigh.default.gc_thresh3 net.ipv4.tcp_rmem net.ipv4.tcp_wmem net.ipv4.tcp_tw_reuse net.ipv4.tcp_mtu_probing net.ipv4.tcp_max_orphans net.ipv4.tcp_max_tw_buckets net.ipv4.tcp_syn_retries net.ipv4.tcp_ecn net.ipv4.tcp_congestion_control net.netfilter.nf_conntrack_max net.netfilter.nf_conntrack_buckets net.netfilter.nf_conntrack_tcp_timeout_close_wait net.netfilter.nf_conntrack_tcp_timeout_time_wait net.netfilter.nf_conntrack_tcp_timeout_established net.netfilter.nf_conntrack_acct kernel.keys.maxkeys kernel.keys.maxbytes kernel.shmmni kernel.shmmax kernel.shmall kernel.core_pattern kernel.perf_event_paranoid kernel.sched_rt_runtime_us kernel.softlockup_panic kernel.yama.ptrace_scope kernel.kptr_restrict kernel.dmesg_restrict kernel.sysrq fs.aio-max-nr fs.file-max fs.inotify.max_user_instances fs.inotify.max_user_watches fs.nr_open vm.dirty_background_ratio vm.dirty_background_bytes vm.dirty_expire_centisecs vm.dirty_ratio vm.dirty_bytes vm.dirty_writeback_centisecs vm.max_map_count vm.overcommit_memory vm.overcommit_ratio vm.vfs_cache_pressure vm.swappiness vm.watermark_scale_factor vm.min_free_kbytes - `cgroupMode` 'CGROUP_MODE_UNSPECIFIED' | 'CGROUP_MODE_V1' | 'CGROUP_MODE_V2' — cgroup_mode specifies the cgroup mode to be used on the node. - `networkTags` NetworkTags — Collection of Compute Engine network tags that can be applied to a node's underlying VM instance. - `tags` string[] — List of network tags. - `resourceManagerTags` ResourceManagerTags — A map of resource manager tag keys and values to be attached to the nodes for managing Compute Engine firewalls using Network Firewall Policies. Tags must be according to specifications in https://cloud.google.com/vpc/docs/tags-firewalls-overview#specifications. A maximum of 5 tag key-value pairs can be specified. Existing tags will be replaced with new values. - `tags` object — TagKeyValue must be in one of the following formats ([KEY]=[VALUE]) 1. `tagKeys/{tag_key_id}=tagValues/{tag_value_id}` 2. `{org_id}/{tag_key_name}={tag_value_name}` 3. `{project_id}/{tag_key_name}={tag_value_name}` - `nodeKubeletConfig` NodeKubeletConfig — Node kubelet configs. - `insecureKubeletReadonlyPortEnabled` boolean — Enable or disable Kubelet read only port. - `crashLoopBackOff` CrashLoopBackOffConfig — Contains config to modify node-level parameters for container restart behavior. - `maxContainerRestartPeriod` string — Optional. The maximum duration the backoff delay can accrue to for container restarts, minimum 1 second, maximum 300 seconds. If not set, defaults to the internal crashloopbackoff maximum. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". See https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#configurable-container-restart-delay for more details. - `imageGcLowThresholdPercent` integer — Optional. Defines the percent of disk usage before which image garbage collection is never run. Lowest disk usage to garbage collect to. The percent is calculated as this field value out of 100. The value must be between 10 and 85, inclusive and smaller than image_gc_high_threshold_percent. The default value is 80 if unspecified. - `imageMaximumGcAge` string — Optional. Defines the maximum age an image can be unused before it is garbage collected. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300s", "1.5h", and "2h45m". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". The value must be a positive duration greater than image_minimum_gc_age or "0s". The default value is "0s" if unspecified, which disables this field, meaning images won't be garbage collected based on being unused for too long. - `cpuManagerPolicy` string — Control the CPU management policy on the node. See https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/ The following values are allowed. * "none": the default, which represents the existing scheduling behavior. * "static": allows pods with certain resource characteristics to be granted increased CPU affinity and exclusivity on the node. The default value is 'none' if unspecified. - `cpuCfsQuota` boolean — Enable CPU CFS quota enforcement for containers that specify CPU limits. This option is enabled by default which makes kubelet use CFS quota (https://www.kernel.org/doc/Documentation/scheduler/sched-bwc.txt) to enforce container CPU limits. Otherwise, CPU limits will not be enforced at all. Disable this option to mitigate CPU throttling problems while still having your pods to be in Guaranteed QoS class by specifying the CPU limits. The default value is 'true' if unspecified. - `evictionMinimumReclaim` EvictionMinimumReclaim — Eviction minimum reclaims are the resource amounts of minimum reclaims for each eviction signal. - `memoryAvailable` string — Optional. Minimum reclaim for eviction due to memory available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsInodesFree` string — Optional. Minimum reclaim for eviction due to imagefs inodes free signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsAvailable` string — Optional. Minimum reclaim for eviction due to nodefs available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsAvailable` string — Optional. Minimum reclaim for eviction due to imagefs available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `pidAvailable` string — Optional. Minimum reclaim for eviction due to pid available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsInodesFree` string — Optional. Minimum reclaim for eviction due to nodefs inodes free signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `allowedUnsafeSysctls` string[] — Optional. Defines a comma-separated allowlist of unsafe sysctls or sysctl patterns (ending in `*`). The unsafe namespaced sysctl groups are `kernel.shm*`, `kernel.msg*`, `kernel.sem`, `fs.mqueue.*`, and `net.*`. Leaving this allowlist empty means they cannot be set on Pods. To allow certain sysctls or sysctl patterns to be set on Pods, list them separated by commas. For example: `kernel.msg*,net.ipv4.route.min_pmtu`. See https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/ for more details. - `evictionSoft` EvictionSignals — Eviction signals are the current state of a particular resource at a specific point in time. The kubelet uses eviction signals to make eviction decisions by comparing the signals to eviction thresholds, which are the minimum amount of the resource that should be available on the node. - `memoryAvailable` string — Optional. Memory available (i.e. capacity - workingSet), in bytes. Defines the amount of "memory.available" signal in kubelet. Default is unset, if not specified in the kubelet config. Format: positive number + unit, e.g. 100Ki, 10Mi, 5Gi. Valid units are Ki, Mi, Gi. Must be >= 100Mi and <= 50% of the node's memory. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsInodesFree` string — Optional. Amount of inodes available on filesystem that container runtime uses for storing images layers. Defines the amount of "imagefs.inodesFree" signal in kubelet. Default is unset, if not specified in the kubelet config. Linux only. It takses percentage value for now. Sample format: "30%". Must be >= 5% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsAvailable` string — Optional. Amount of storage available on filesystem that kubelet uses for volumes, daemon logs, etc. Defines the amount of "nodefs.available" signal in kubelet. Default is unset, if not specified in the kubelet config. It takses percentage value for now. Sample format: "30%". Must be >= 10% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsAvailable` string — Optional. Amount of storage available on filesystem that container runtime uses for storing images layers. If the container filesystem and image filesystem are not separate, then imagefs can store both image layers and writeable layers. Defines the amount of "imagefs.available" signal in kubelet. Default is unset, if not specified in the kubelet config. It takses percentage value for now. Sample format: "30%". Must be >= 15% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `pidAvailable` string — Optional. Amount of PID available for pod allocation. Defines the amount of "pid.available" signal in kubelet. Default is unset, if not specified in the kubelet config. It takses percentage value for now. Sample format: "30%". Must be >= 10% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsInodesFree` string — Optional. Amount of inodes available on filesystem that kubelet uses for volumes, daemon logs, etc. Defines the amount of "nodefs.inodesFree" signal in kubelet. Default is unset, if not specified in the kubelet config. Linux only. It takses percentage value for now. Sample format: "30%". Must be >= 5% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `podPidsLimit` string, int64 — Set the Pod PID limits. See https://kubernetes.io/docs/concepts/policy/pid-limiting/#pod-pid-limits Controls the maximum number of processes allowed to run in a pod. The value must be greater than or equal to 1024 and less than 4194304. - `imageGcHighThresholdPercent` integer — Optional. Defines the percent of disk usage after which image garbage collection is always run. The percent is calculated as this field value out of 100. The value must be between 10 and 85, inclusive and greater than image_gc_low_threshold_percent. The default value is 85 if unspecified. - `shutdownGracePeriodCriticalPodsSeconds` integer — Optional. shutdown_grace_period_critical_pods_seconds is the maximum allowed grace period (in seconds) used to terminate critical pods during a node shutdown. This value should be <= shutdown_grace_period_seconds, and is only valid if shutdown_grace_period_seconds is set. https://kubernetes.io/docs/concepts/cluster-administration/node-shutdown/ Range: [0, 120]. - `imageMinimumGcAge` string — Optional. Defines the minimum age for an unused image before it is garbage collected. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300s", "1.5h", and "2h45m". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". The value must be a positive duration less than or equal to 2 minutes. The default value is "2m0s" if unspecified. - `singleProcessOomKill` boolean — Optional. Defines whether to enable single process OOM killer. If true, will prevent the memory.oom.group flag from being set for container cgroups in cgroups v2. This causes processes in the container to be OOM killed individually instead of as a group. - `evictionMaxPodGracePeriodSeconds` integer — Optional. eviction_max_pod_grace_period_seconds is the maximum allowed grace period (in seconds) to use when terminating pods in response to a soft eviction threshold being met. This value effectively caps the Pod's terminationGracePeriodSeconds value during soft evictions. Default: 0. Range: [0, 300]. - `evictionSoftGracePeriod` EvictionGracePeriod — Eviction grace periods are grace periods for each eviction signal. - `nodefsAvailable` string — Optional. Grace period for eviction due to nodefs available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsAvailable` string — Optional. Grace period for eviction due to imagefs available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `pidAvailable` string — Optional. Grace period for eviction due to pid available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsInodesFree` string — Optional. Grace period for eviction due to nodefs inodes free signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `memoryAvailable` string — Optional. Grace period for eviction due to memory available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsInodesFree` string — Optional. Grace period for eviction due to imagefs inodes free signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `maxParallelImagePulls` integer — Optional. Defines the maximum number of image pulls in parallel. The range is 2 to 5, inclusive. The default value is 2 or 3 depending on the disk type. See https://kubernetes.io/docs/concepts/containers/images/#maximum-parallel-image-pulls for more details. - `containerLogMaxSize` string — Optional. Defines the maximum size of the container log file before it is rotated. See https://kubernetes.io/docs/concepts/cluster-administration/logging/#log-rotation Valid format is positive number + unit, e.g. 100Ki, 10Mi. Valid units are Ki, Mi, Gi. The value must be between 10Mi and 500Mi, inclusive. Note that the total container log size (container_log_max_size * container_log_max_files) cannot exceed 1% of the total storage of the node, to avoid disk pressure caused by log files. The default value is 10Mi if unspecified. - `shutdownGracePeriodSeconds` integer — Optional. shutdown_grace_period_seconds is the maximum allowed grace period (in seconds) the total duration that the node should delay the shutdown during a graceful shutdown. This is the total grace period for pod termination for both regular and critical pods. https://kubernetes.io/docs/concepts/cluster-administration/node-shutdown/ If set to 0, node will not enable the graceful node shutdown functionality. This field is only valid for Spot VMs. Allowed values: 0, 30, 120. - `memoryManager` MemoryManager — The option enables the Kubernetes NUMA-aware Memory Manager feature. Detailed description about the feature can be found [here](https://kubernetes.io/docs/tasks/administer-cluster/memory-manager/). - `policy` string — Controls the memory management policy on the Node. See https://kubernetes.io/docs/tasks/administer-cluster/memory-manager/#policies The following values are allowed. * "none" * "static" The default value is 'none' if unspecified. - `topologyManager` TopologyManager — TopologyManager defines the configuration options for the [`kubelet` Topology Manager component](https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/). For more information about the supported machine types and versions for the Topology Manager in GKE, see [Customizing node system configuration](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/node-system-config#kubelet-resource-managers). - `scope` string — The Topology Manager aligns resources in following scopes: * container * pod The default scope is 'container' if unspecified. See https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/#topology-manager-scopes - `policy` string — Configures the strategy for resource alignment. Allowed values are: * none: the default policy, and does not perform any topology alignment. * restricted: the topology manager stores the preferred NUMA node affinity for the container, and will reject the pod if the affinity if not preferred. * best-effort: the topology manager stores the preferred NUMA node affinity for the container. If the affinity is not preferred, the topology manager will admit the pod to the node anyway. * single-numa-node: the topology manager determines if the single NUMA node affinity is possible. If it is, Topology Manager will store this and the Hint Providers can then use this information when making the resource allocation decision. If, however, this is not possible then the Topology Manager will reject the pod from the node. This will result in a pod in a Terminated state with a pod admission failure. The default policy value is 'none' if unspecified. Details about each strategy can be found [here](https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/#topology-manager-policies). - `cpuCfsQuotaPeriod` string — Set the CPU CFS quota period value 'cpu.cfs_period_us'. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". The value must be a positive duration between 1ms and 1 second, inclusive. - `containerLogMaxFiles` integer — Optional. Defines the maximum number of container log files that can be present for a container. See https://kubernetes.io/docs/concepts/cluster-administration/logging/#log-rotation The value must be an integer between 2 and 10, inclusive. The default value is 5 if unspecified. - `notificationConfig` NotificationConfig — NotificationConfig is the configuration of notifications. - `pubsub` PubSub — Pub/Sub specific notification config. - `enabled` boolean — Enable notifications for Pub/Sub. - `filter` Filter — Allows filtering to one or more specific event types. If event types are present, those and only those event types will be transmitted to the cluster. Other types will be skipped. If no filter is specified, or no event types are present, all event types will be sent - `eventType` string[] — Event types to allowlist. - `topic` string — The desired Pub/Sub topic to which notifications will be sent by GKE. Format is `projects/{project}/topics/{topic}`. - `maintenancePolicy` MaintenancePolicy — MaintenancePolicy defines the maintenance policy to be used for the cluster. - `window` MaintenanceWindow — MaintenanceWindow defines the maintenance window to be used for the cluster. - `dailyMaintenanceWindow` DailyMaintenanceWindow — Time window specified for daily maintenance operations. - `startTime` string — Time within the maintenance window to start the maintenance operations. Time format should be in [RFC3339](https://www.ietf.org/rfc/rfc3339.txt) format "HH:MM", where HH : [00-23] and MM : [00-59] GMT. - `duration` string — Output only. Duration of the time window, automatically chosen to be smallest possible in the given scenario. Duration will be in [RFC3339](https://www.ietf.org/rfc/rfc3339.txt) format "PTnHnMnS". - `recurringMaintenanceWindow` RecurringMaintenanceWindow — Represents an arbitrary window of time that recurs. Will replace RecurringTimeWindow. - `recurrence` string — Required. An RRULE (https://tools.ietf.org/html/rfc5545#section-3.8.5.3) for how this window recurs. For example, to have something repeat every weekday, you'd use: `FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR` To repeat some window daily (equivalent to the DailyMaintenanceWindow): `FREQ=DAILY` For the first weekend of every month: `FREQ=MONTHLY;BYSETPOS=1;BYDAY=SA,SU` The FREQ values of HOURLY, MINUTELY, and SECONDLY are not supported. - `delayUntil` Date — Represents a whole or partial calendar date, such as a birthday. The time of day and time zone are either specified elsewhere or are insignificant. The date is relative to the Gregorian Calendar. This can represent one of the following: * A full date, with non-zero year, month, and day values. * A month and day, with a zero year (for example, an anniversary). * A year on its own, with a zero month and a zero day. * A year and month, with a zero day (for example, a credit card expiration date). Related types: * google.type.TimeOfDay * google.type.DateTime * google.protobuf.Timestamp - `year` integer — Year of the date. Must be from 1 to 9999, or 0 to specify a date without a year. - `month` integer — Month of a year. Must be from 1 to 12, or 0 to specify a year without a month and day. - `day` integer — Day of a month. Must be from 1 to 31 and valid for the year and month, or 0 to specify a year by itself or a year and month where the day isn't significant. - `windowDuration` string, google-duration — Required. Duration of the window. - `windowStartTime` TimeOfDay — Represents a time of day. The date and time zone are either not significant or are specified elsewhere. An API may choose to allow leap seconds. Related types are google.type.Date and `google.protobuf.Timestamp`. - `hours` integer — Hours of a day in 24 hour format. Must be greater than or equal to 0 and typically must be less than or equal to 23. An API may choose to allow the value "24:00:00" for scenarios like business closing time. - `nanos` integer — Fractions of seconds, in nanoseconds. Must be greater than or equal to 0 and less than or equal to 999,999,999. - `minutes` integer — Minutes of an hour. Must be greater than or equal to 0 and less than or equal to 59. - `seconds` integer — Seconds of a minute. Must be greater than or equal to 0 and typically must be less than or equal to 59. An API may allow the value 60 if it allows leap-seconds. - `maintenanceExclusions` object — Exceptions to maintenance window. Non-emergency maintenance should not occur in these windows. - `recurringWindow` RecurringTimeWindow — Represents an arbitrary window of time that recurs. - `window` TimeWindow — Represents an arbitrary window of time. - `endTime` string, google-datetime — The time that the window ends. The end time should take place after the start time. - `maintenanceExclusionOptions` MaintenanceExclusionOptions — Represents the Maintenance exclusion option. - … - `startTime` string, google-datetime — The time that the window first starts. - `recurrence` string — An RRULE (https://tools.ietf.org/html/rfc5545#section-3.8.5.3) for how this window recurs. They go on for the span of time between the start and end time. For example, to have something repeat every weekday, you'd use: `FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR` To repeat some window daily (equivalent to the DailyMaintenanceWindow): `FREQ=DAILY` For the first weekend of every month: `FREQ=MONTHLY;BYSETPOS=1;BYDAY=SA,SU` This specifies how frequently the window starts. Eg, if you wanted to have a 9-5 UTC-4 window every weekday, you'd use something like: ``` start time = 2019-01-01T09:00:00-0400 end time = 2019-01-01T17:00:00-0400 recurrence = FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR ``` Windows can span multiple days. Eg, to make the window encompass every weekend from midnight Saturday till the last minute of Sunday UTC: ``` start time = 2019-01-05T00:00:00Z end time = 2019-01-07T23:59:00Z recurrence = FREQ=WEEKLY;BYDAY=SA ``` Note the start and end time's specific dates are largely arbitrary except to specify duration of the window and when it first starts. The FREQ values of HOURLY, MINUTELY, and SECONDLY are not supported. - `resourceVersion` string — A hash identifying the version of this policy, so that updates to fields of the policy won't accidentally undo intermediate changes (and so that users of the API unaware of some fields won't accidentally remove other fields). Make a `get()` request to the cluster to get the current resource version and include it with requests to set the policy. - `disruptionBudget` DisruptionBudget — DisruptionBudget defines the upgrade disruption budget for the cluster control plane. - `lastDisruptionTime` string, google-datetime — Output only. The last time a disruption was performed on the control plane. - `minorVersionDisruptionInterval` string, google-duration — Optional. The minimum duration between two minor version upgrades of the control plane. - `patchVersionDisruptionInterval` string, google-duration — Optional. The minimum duration between two patch version upgrades of the control plane. - `lastMinorVersionDisruptionTime` string, google-datetime — Output only. The last time a minor version upgrade was performed on the control plane. - `meshCertificates` MeshCertificates — Configuration for issuance of mTLS keys and certificates to Kubernetes pods. - `enableCertificates` boolean — enable_certificates controls issuance of workload mTLS certificates. If set, the GKE Workload Identity Certificates controller and node agent will be deployed in the cluster, which can then be configured by creating a WorkloadCertificateConfig Custom Resource. Requires Workload Identity (workload_pool must be non-empty). - `name` string — The name of this cluster. The name must be unique within this project and location (e.g. zone or region), and can be up to 40 characters with the following restrictions: * Lowercase letters, numbers, and hyphens only. * Must start with a letter. * Must end with a number or a letter. - `networkPolicy` NetworkPolicy — Configuration options for the NetworkPolicy feature. https://kubernetes.io/docs/concepts/services-networking/networkpolicies/ - `provider` 'PROVIDER_UNSPECIFIED' | 'CALICO' — The selected network policy provider. - `enabled` boolean — Whether network policy is enabled on the cluster. - `secretManagerConfig` SecretManagerConfig — SecretManagerConfig is config for secret manager enablement. - `rotationConfig` RotationConfig — RotationConfig is config for secret manager auto rotation. - `enabled` boolean — Whether the rotation is enabled. - `rotationInterval` string, google-duration — The interval between two consecutive rotations. Default rotation interval is 2 minutes. - `enabled` boolean — Enable/Disable Secret Manager Config. - `nodeConfig` NodeConfig — Parameters that describe the nodes in a cluster. GKE Autopilot clusters do not recognize parameters in `NodeConfig`. Use AutoprovisioningNodePoolDefaults instead. - `taintConfig` TaintConfig — TaintConfig contains the configuration for the taints of the node pool. - `architectureTaintBehavior` 'ARCHITECTURE_TAINT_BEHAVIOR_UNSPECIFIED' | 'NONE' | 'ARM' — Optional. Controls architecture tainting behavior. - `nodeGroup` string — Setting this field will assign instances of this pool to run on the specified node group. This is useful for running workloads on [sole tenant nodes](https://cloud.google.com/compute/docs/nodes/sole-tenant-nodes). - `loggingConfig` NodePoolLoggingConfig — NodePoolLoggingConfig specifies logging configuration for node pools. - `variantConfig` LoggingVariantConfig — LoggingVariantConfig specifies the behaviour of the logging component. - `variant` 'VARIANT_UNSPECIFIED' | 'DEFAULT' | 'MAX_THROUGHPUT' — Logging variant deployed on nodes. - `consolidationDelay` string, google-duration — Consolidation delay defines duration after which the Cluster Autoscaler can scale down underutilized nodes. If not set, nodes are scaled down by default behavior, i.e. according to the chosen autoscaling profile. - `storagePools` string[] — List of Storage Pools where boot disks are provisioned. - `bootDiskKmsKey` string — The Customer Managed Encryption Key used to encrypt the boot disk attached to each node in the node pool. This should be of the form projects/[KEY_PROJECT_ID]/locations/[LOCATION]/keyRings/[RING_NAME]/cryptoKeys/[KEY_NAME]. For more information about protecting resources with Cloud KMS Keys please see: https://cloud.google.com/compute/docs/disks/customer-managed-encryption - `preemptible` boolean — Whether the nodes are created as preemptible VM instances. See: https://cloud.google.com/compute/docs/instances/preemptible for more information about preemptible VM instances. - `spot` boolean — Spot flag for enabling Spot VM, which is a rebrand of the existing preemptible flag. - `secondaryBootDisks` SecondaryBootDisk[] — List of secondary boot disks attached to the nodes. - `diskImage` string — Fully-qualified resource ID for an existing disk image. - `mode` 'MODE_UNSPECIFIED' | 'CONTAINER_IMAGE_CACHE' — Disk mode (container image cache, etc.) - `metadata` object — The metadata key/value pairs assigned to instances in the cluster. Keys must conform to the regexp `[a-zA-Z0-9-_]+` and be less than 128 bytes in length. These are reflected as part of a URL in the metadata server. Additionally, to avoid ambiguity, keys must not conflict with any other metadata keys for the project or be one of the reserved keys: - "cluster-location" - "cluster-name" - "cluster-uid" - "configure-sh" - "containerd-configure-sh" - "enable-os-login" - "gci-ensure-gke-docker" - "gci-metrics-enabled" - "gci-update-strategy" - "instance-template" - "kube-env" - "startup-script" - "user-data" - "disable-address-manager" - "windows-startup-script-ps1" - "common-psm1" - "k8s-node-setup-psm1" - "install-ssh-psm1" - "user-profile-psm1" Values are free-form strings, and only have meaning as interpreted by the image running in the instance. The only restriction placed on them is that each value's size must be less than or equal to 32 KB. The total size of all keys and values must be less than 512 KB. - `minCpuPlatform` string — Minimum CPU platform to be used by this instance. The instance may be scheduled on the specified or newer CPU platform. Applicable values are the friendly names of CPU platforms, such as `minCpuPlatform: "Intel Haswell"` or `minCpuPlatform: "Intel Sandy Bridge"`. For more information, read [how to specify min CPU platform](https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform) - `windowsNodeConfig` WindowsNodeConfig — Parameters that can be configured on Windows nodes. Windows Node Config that define the parameters that will be used to configure the Windows node pool settings. - `osVersion` 'OS_VERSION_UNSPECIFIED' | 'OS_VERSION_LTSC2019' | 'OS_VERSION_LTSC2022' — OSVersion specifies the Windows node config to be used on the node. - `sandboxConfig` SandboxConfig — SandboxConfig contains configurations of the sandbox to use for the node. - `type` 'UNSPECIFIED' | 'GVISOR' — Type of the sandbox to use for the node. - `localSsdEncryptionMode` 'LOCAL_SSD_ENCRYPTION_MODE_UNSPECIFIED' | 'STANDARD_ENCRYPTION' | 'EPHEMERAL_KEY_ENCRYPTION' — Specifies which method should be used for encrypting the Local SSDs attached to the node. - `labels` object — The Kubernetes labels (key/value pairs) to apply to each node. The values in this field are added to the set of default labels Kubernetes applies to nodes. This field has the following restrictions: * Labels must use a valid Kubernetes syntax and character set, as defined in https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set. * This field supports up to 1,024 total characters in a single request. Depending on the Kubernetes version, keys in this field might conflict with the keys of the default labels, which might change which of your labels are applied to the nodes. Assume that the behavior is unpredictable and avoid label key conflicts. For more information about the default labels, see: https://kubernetes.io/docs/reference/labels-annotations-taints/ - `gcfsConfig` GcfsConfig — GcfsConfig contains configurations of Google Container File System (image streaming). - `enabled` boolean — Whether to use GCFS. - `imageType` string — The image type to use for this node. Note that for a given image type, the latest version of it will be used. Please see https://cloud.google.com/kubernetes-engine/docs/concepts/node-images for available image types. - `secondaryBootDiskUpdateStrategy` SecondaryBootDiskUpdateStrategy — SecondaryBootDiskUpdateStrategy is a placeholder which will be extended in the future to define different options for updating secondary boot disks. - `flexStart` boolean — Flex Start flag for enabling Flex Start VM. - `reservationAffinity` ReservationAffinity — [ReservationAffinity](https://cloud.google.com/compute/docs/instances/reserving-zonal-resources) is the configuration of desired reservation which instances could take capacity from. - `consumeReservationType` 'UNSPECIFIED' | 'NO_RESERVATION' | 'ANY_RESERVATION' | 'SPECIFIC_RESERVATION' | 'ANY_RESERVATION_THEN_FAIL' — Corresponds to the type of reservation consumption. - `values` string[] — Corresponds to the label value(s) of reservation resource(s). - `key` string — Corresponds to the label key of a reservation resource. To target a SPECIFIC_RESERVATION by name, specify "compute.googleapis.com/reservation-name" as the key and specify the name of your reservation as its value. - `advancedMachineFeatures` AdvancedMachineFeatures — Specifies options for controlling advanced machine features. - `threadsPerCore` string, int64 — The number of threads per physical core. To disable simultaneous multithreading (SMT) set this to 1. If unset, the maximum number of threads supported per core by the underlying processor is assumed. - `performanceMonitoringUnit` 'PERFORMANCE_MONITORING_UNIT_UNSPECIFIED' | 'ARCHITECTURAL' | 'STANDARD' | 'ENHANCED' — Type of Performance Monitoring Unit (PMU) requested on node pool instances. If unset, PMU will not be available to the node. - `enableNestedVirtualization` boolean — Whether or not to enable nested virtualization (defaults to false). - `bootDisk` BootDisk — BootDisk specifies the boot disk configuration for node pools. - `diskType` string — Disk type of the boot disk. (i.e. Hyperdisk-Balanced, PD-Balanced, etc.) - `sizeGb` string, int64 — Disk size in GB. Replaces NodeConfig.disk_size_gb - `provisionedIops` string, int64 — For Hyperdisk-Balanced only, the provisioned IOPS config value. - `provisionedThroughput` string, int64 — For Hyperdisk-Balanced only, the provisioned throughput config value. - `gvnic` VirtualNIC — Configuration of gVNIC feature. - `enabled` boolean — Whether gVNIC features are enabled in the node pool. - `gpuDirectConfig` GPUDirectConfig — GPUDirectConfig specifies the GPU direct strategy on the node pool. - `gpuDirectStrategy` 'GPU_DIRECT_STRATEGY_UNSPECIFIED' | 'RDMA' — The type of GPU direct strategy to enable on the node pool. - `nodeImageConfig` CustomImageConfig — CustomImageConfig contains the information r - `image` string — The name of the image to use for this node. - `imageProject` string — The project containing the image to use for this node. - `serviceAccount` string — The Google Cloud Platform Service Account to be used by the node VMs. Specify the email address of the Service Account; otherwise, if no Service Account is specified, the "default" service account is used. - `shieldedInstanceConfig` ShieldedInstanceConfig — A set of Shielded Instance options. - `enableIntegrityMonitoring` boolean — Defines whether the instance has integrity monitoring enabled. Enables monitoring and attestation of the boot integrity of the instance. The attestation is performed against the integrity policy baseline. This baseline is initially derived from the implicitly trusted boot image when the instance is created. - `enableSecureBoot` boolean — Defines whether the instance has Secure Boot enabled. Secure Boot helps ensure that the system only runs authentic software by verifying the digital signature of all boot components, and halting the boot process if signature verification fails. - `linuxNodeConfig` LinuxNodeConfig — Parameters that can be configured on Linux nodes. - `hugepages` HugepagesConfig — Hugepages amount in both 2m and 1g size - `hugepageSize2m` integer — Optional. Amount of 2M hugepages - `hugepageSize1g` integer — Optional. Amount of 1G hugepages - `nodeKernelModuleLoading` NodeKernelModuleLoading — Configuration for kernel module loading on nodes. - `policy` 'POLICY_UNSPECIFIED' | 'ENFORCE_SIGNED_MODULES' | 'DO_NOT_ENFORCE_SIGNED_MODULES' — Set the node module loading policy for nodes in the node pool. - `accurateTimeConfig` AccurateTimeConfig — AccurateTimeConfig contains configuration for the accurate time synchronization feature. - `enablePtpKvmTimeSync` boolean — Enables enhanced time synchronization using PTP-KVM. - `transparentHugepageDefrag` 'TRANSPARENT_HUGEPAGE_DEFRAG_UNSPECIFIED' | 'TRANSPARENT_HUGEPAGE_DEFRAG_ALWAYS' | 'TRANSPARENT_HUGEPAGE_DEFRAG_DEFER' | 'TRANSPARENT_HUGEPAGE_DEFRAG_DEFER_WITH_MADVISE' | 'TRANSPARENT_HUGEPAGE_DEFRAG_MADVISE' | 'TRANSPARENT_HUGEPAGE_DEFRAG_NEVER' — Optional. Defines the transparent hugepage defrag configuration on the node. VM hugepage allocation can be managed by either limiting defragmentation for delayed allocation or skipping it entirely for immediate allocation only. See https://docs.kernel.org/admin-guide/mm/transhuge.html for more details. - `swapConfig` SwapConfig — Configuration for swap memory on a node pool. - `encryptionConfig` EncryptionConfig — Defines encryption settings for the swap space. - `disabled` boolean — Optional. If true, swap space will not be encrypted. Defaults to false (encrypted). - `ephemeralLocalSsdProfile` EphemeralLocalSsdProfile — Swap on the local SSD shared with pod ephemeral storage. - `swapSizeGib` string, int64 — Specifies the size of the swap space in gibibytes (GiB). - `swapSizePercent` integer — Specifies the size of the swap space as a percentage of the ephemeral local SSD capacity. - `enabled` boolean — Optional. Enables or disables swap for the node pool. - `bootDiskProfile` BootDiskProfile — Swap on the node's boot disk. - `swapSizeGib` string, int64 — Specifies the size of the swap space in gibibytes (GiB). - `swapSizePercent` integer — Specifies the size of the swap space as a percentage of the boot disk size. - `dedicatedLocalSsdProfile` DedicatedLocalSsdProfile — Provisions a new, separate local NVMe SSD exclusively for swap. - `diskCount` string, int64 — The number of physical local NVMe SSD disks to attach. - `customNodeInit` CustomNodeInit — Support for running custom init code while bootstrapping nodes. - `initScript` InitScript — InitScript provide a simply bash script to be executed on the node. - `gcsUri` string — The Cloud Storage URI for storing the init script. Format: gs://BUCKET_NAME/OBJECT_NAME The service account on the node pool must have read access to the object. User can't configure both gcs_uri and gcp_secret_manager_secret_uri. - `args` string[] — Optional. The optional arguments line to be passed to the init script. - `gcsGeneration` string, int64 — The generation of the init script stored in Gloud Storage. This is the required field to identify the version of the init script. User can get the genetaion from `gcloud storage objects describe gs://BUCKET_NAME/OBJECT_NAME --format="value(generation)"` or from the "Version history" tab of the object in the Cloud Console UI. - `gcpSecretManagerSecretUri` string — The resource name of the secret manager secret hosting the init script. Both global and regional secrets are supported with format below: Global secret: projects/{project}/secrets/{secret}/versions/{version} Regional secret: projects/{project}/locations/{location}/secrets/{secret}/versions/{version} Example: projects/1234567890/secrets/script_1/versions/1. Accept version number only, not support version alias. User can't configure both gcp_secret_manager_secret_uri and gcs_uri. - `diskIoScheduler` DiskIoScheduler — DiskIoScheduler contains the configuration for the disk IO scheduler. - `nodeSystemIoScheduler` string — Optional. Configures the IO scheduler for the boot disk or ephemeral lssd that runs node system workloads. Supported values are `mq-deadline`, `bfq`, `kyber`, `none`. - `nodeAttachedDiskIoScheduler` string — Optional. Configures the IO scheduler for the attached disks. Supported values are `mq-deadline`, `bfq`, `kyber`, `none`. - `transparentHugepageEnabled` 'TRANSPARENT_HUGEPAGE_ENABLED_UNSPECIFIED' | 'TRANSPARENT_HUGEPAGE_ENABLED_ALWAYS' | 'TRANSPARENT_HUGEPAGE_ENABLED_MADVISE' | 'TRANSPARENT_HUGEPAGE_ENABLED_NEVER' — Optional. Transparent hugepage support for anonymous memory can be entirely disabled (mostly for debugging purposes) or only enabled inside MADV_HUGEPAGE regions (to avoid the risk of consuming more memory resources) or enabled system wide. See https://docs.kernel.org/admin-guide/mm/transhuge.html for more details. - `nodeVfioConfig` NodeVfioConfig — Configuration settings for VFIO (Virtual Function I/O) on a node. VFIO allows safe, unprivileged, userspace drivers to access I/O devices. - `dmaEntryLimit` integer — Optional. Specifies the maximum number of DMA entries (pages) that can be mapped by the VFIO IOMMU type 1 driver for a container. This limit affects the total amount of host memory that can be pinned for direct device access, which is often critical for high-performance devices like TPUs and GPUs. This setting corresponds to the kernel parameter at: `/sys/module/vfio_iommu_type1/parameters/dma_entry_limit`. The default value in the kernel is `65535`. Higher values may be needed for workloads mapping large memory regions. Supported values are integers between `65535` and `4194304`. - `sysctls` object — The Linux kernel parameters to be applied to the nodes and all pods running on the nodes. The following parameters are supported. net.core.busy_poll net.core.busy_read net.core.netdev_max_backlog net.core.rmem_max net.core.rmem_default net.core.wmem_default net.core.wmem_max net.core.optmem_max net.core.somaxconn net.ipv4.neigh.default.gc_thresh1 net.ipv4.neigh.default.gc_thresh2 net.ipv4.neigh.default.gc_thresh3 net.ipv4.tcp_rmem net.ipv4.tcp_wmem net.ipv4.tcp_tw_reuse net.ipv4.tcp_mtu_probing net.ipv4.tcp_max_orphans net.ipv4.tcp_max_tw_buckets net.ipv4.tcp_syn_retries net.ipv4.tcp_ecn net.ipv4.tcp_congestion_control net.netfilter.nf_conntrack_max net.netfilter.nf_conntrack_buckets net.netfilter.nf_conntrack_tcp_timeout_close_wait net.netfilter.nf_conntrack_tcp_timeout_time_wait net.netfilter.nf_conntrack_tcp_timeout_established net.netfilter.nf_conntrack_acct kernel.keys.maxkeys kernel.keys.maxbytes kernel.shmmni kernel.shmmax kernel.shmall kernel.core_pattern kernel.perf_event_paranoid kernel.sched_rt_runtime_us kernel.softlockup_panic kernel.yama.ptrace_scope kernel.kptr_restrict kernel.dmesg_restrict kernel.sysrq fs.aio-max-nr fs.file-max fs.inotify.max_user_instances fs.inotify.max_user_watches fs.nr_open vm.dirty_background_ratio vm.dirty_background_bytes vm.dirty_expire_centisecs vm.dirty_ratio vm.dirty_bytes vm.dirty_writeback_centisecs vm.max_map_count vm.overcommit_memory vm.overcommit_ratio vm.vfs_cache_pressure vm.swappiness vm.watermark_scale_factor vm.min_free_kbytes - `cgroupMode` 'CGROUP_MODE_UNSPECIFIED' | 'CGROUP_MODE_V1' | 'CGROUP_MODE_V2' — cgroup_mode specifies the cgroup mode to be used on the node. - `tags` string[] — The list of instance tags applied to all nodes. Tags are used to identify valid sources or targets for network firewalls and are specified by the client during cluster or node pool creation. Each tag within the list must comply with RFC1035. - `soleTenantConfig` SoleTenantConfig — SoleTenantConfig contains the NodeAffinities to specify what shared sole tenant node groups should back the node pool. - `minNodeCpus` integer — Optional. The minimum number of virtual CPUs this instance will consume when running on a sole-tenant node. This field can only be set if the node pool is created in a shared sole-tenant node group. - `nodeAffinities` NodeAffinity[] — NodeAffinities used to match to a shared sole tenant node group. - `values` string[] — Values for NodeAffinity. - `key` string — Key for NodeAffinity. - `operator` 'OPERATOR_UNSPECIFIED' | 'IN' | 'NOT_IN' — Operator for NodeAffinity. - `resourceManagerTags` ResourceManagerTags — A map of resource manager tag keys and values to be attached to the nodes for managing Compute Engine firewalls using Network Firewall Policies. Tags must be according to specifications in https://cloud.google.com/vpc/docs/tags-firewalls-overview#specifications. A maximum of 5 tag key-value pairs can be specified. Existing tags will be replaced with new values. - `tags` object — TagKeyValue must be in one of the following formats ([KEY]=[VALUE]) 1. `tagKeys/{tag_key_id}=tagValues/{tag_value_id}` 2. `{org_id}/{tag_key_name}={tag_value_name}` 3. `{project_id}/{tag_key_name}={tag_value_name}` - `ephemeralStorageLocalSsdConfig` EphemeralStorageLocalSsdConfig — EphemeralStorageLocalSsdConfig contains configuration for the node ephemeral storage using Local SSDs. - `localSsdCount` integer — Number of local SSDs to use to back ephemeral storage. Uses NVMe interfaces. A zero (or unset) value has different meanings depending on machine type being used: 1. For pre-Gen3 machines, which support flexible numbers of local ssds, zero (or unset) means to disable using local SSDs as ephemeral storage. The limit for this value is dependent upon the maximum number of disk available on a machine per zone. See: https://cloud.google.com/compute/docs/disks/local-ssd for more information. 2. For Gen3 machines which dictate a specific number of local ssds, zero (or unset) means to use the default number of local ssds that goes with that machine type. For example, for a c3-standard-8-lssd machine, 2 local ssds would be provisioned. For c3-standard-8 (which doesn't support local ssds), 0 will be provisioned. See https://cloud.google.com/compute/docs/disks/local-ssd#choose_number_local_ssds for more info. - `dataCacheCount` integer — Number of local SSDs to use for GKE Data Cache. - `diskSizeGb` integer — Size of the disk attached to each node, specified in GB. The smallest allowed disk size is 10GB. If unspecified, the default disk size is 100GB. - `enableConfidentialStorage` boolean — Optional. Reserved for future use. - `localSsdCount` integer — The number of local SSD disks to be attached to the node. The limit for this value is dependent upon the maximum number of disks available on a machine per zone. See: https://cloud.google.com/compute/docs/disks/local-ssd for more information. - `taints` NodeTaint[] — List of kubernetes taints to be applied to each node. For more information, including usage and the valid values, see: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/ - `key` string — Key for taint. - `value` string — Value for taint. - `effect` 'EFFECT_UNSPECIFIED' | 'NO_SCHEDULE' | 'PREFER_NO_SCHEDULE' | 'NO_EXECUTE' — Effect for taint. - `diskType` string — Type of the disk attached to each node (e.g. 'pd-standard', 'pd-ssd' or 'pd-balanced') If unspecified, the default disk type is 'pd-standard' - `resourceLabels` object — The resource labels for the node pool to use to annotate any related Google Compute Engine resources. - `workloadMetadataConfig` WorkloadMetadataConfig — WorkloadMetadataConfig defines the metadata configuration to expose to workloads on the node pool. - `mode` 'MODE_UNSPECIFIED' | 'GCE_METADATA' | 'GKE_METADATA' — Mode is the configuration for how to expose metadata to workloads running on the node pool. - `oauthScopes` string[] — The set of Google API scopes to be made available on all of the node VMs under the "default" service account. The following scopes are recommended, but not required, and by default are not included: * `https://www.googleapis.com/auth/compute` is required for mounting persistent storage on your nodes. * `https://www.googleapis.com/auth/devstorage.read_only` is required for communicating with **gcr.io** (the [Artifact Registry](https://cloud.google.com/artifact-registry/)). If unspecified, no scopes are added, unless Cloud Logging or Cloud Monitoring are enabled, in which case their required scopes will be added. - `machineType` string — The name of a Google Compute Engine [machine type](https://cloud.google.com/compute/docs/machine-types) If unspecified, the default machine type is `e2-medium`. - `localNvmeSsdBlockConfig` LocalNvmeSsdBlockConfig — LocalNvmeSsdBlockConfig contains configuration for using raw-block local NVMe SSDs - `localSsdCount` integer — Number of local NVMe SSDs to use. The limit for this value is dependent upon the maximum number of disk available on a machine per zone. See: https://cloud.google.com/compute/docs/disks/local-ssd for more information. A zero (or unset) value has different meanings depending on machine type being used: 1. For pre-Gen3 machines, which support flexible numbers of local ssds, zero (or unset) means to disable using local SSDs as ephemeral storage. 2. For Gen3 machines which dictate a specific number of local ssds, zero (or unset) means to use the default number of local ssds that goes with that machine type. For example, for a c3-standard-8-lssd machine, 2 local ssds would be provisioned. For c3-standard-8 (which doesn't support local ssds), 0 will be provisioned. See https://cloud.google.com/compute/docs/disks/local-ssd#choose_number_local_ssds for more info. - `fastSocket` FastSocket — Configuration of Fast Socket feature. - `enabled` boolean — Whether Fast Socket features are enabled in the node pool. - `containerdConfig` ContainerdConfig — ContainerdConfig contains configuration to customize containerd. - `registryHosts` RegistryHostConfig[] — RegistryHostConfig configures containerd registry host configuration. Each registry_hosts represents a hosts.toml file. At most 25 registry_hosts are allowed. - `hosts` HostConfig[] — HostConfig configures a list of host-specific configurations for the server. Each server can have at most 10 host configurations. - `header` RegistryHeader[] — Header configures the registry host headers. - … - `client` CertificateConfigPair[] — Client configures the registry host client certificate and key. - … - `overridePath` boolean — OverridePath is used to indicate the host's API root endpoint is defined in the URL path rather than by the API specification. This may be used with non-compliant OCI registries which are missing the /v2 prefix. If not set, containerd sets default false. - `host` string — Host configures the registry host/mirror. It supports fully qualified domain names (FQDNs) and IP addresses. Specifying scheme, port or path is supported. Scheme can only be http or https. Wildcards are NOT supported. Examples: - `my.customdomain.com` - `https://my.customdomain.com/path` - `10.0.1.2:5000` - `capabilities` string[] — Capabilities represent the capabilities of the registry host, specifying what operations a host is capable of performing. If not set, containerd enables all capabilities by default. - `dialTimeout` string, google-duration — Specifies the maximum duration allowed for a connection attempt to complete. A shorter timeout helps reduce delays when falling back to the original registry if the mirror is unreachable. Maximum allowed value is 180s. If not set, containerd sets default 30s. The value should be a decimal number of seconds with an `s` suffix. - `ca` CertificateConfig[] — CA configures the registry host certificate. - … - `server` string — Defines the host name of the registry server, which will be used to create configuration file as /etc/containerd/hosts.d//hosts.toml. It supports fully qualified domain names (FQDN) and IP addresses: Specifying port is supported, while scheme and path are NOT supported. Wildcards are NOT supported. Examples: - `my.customdomain.com` - `10.0.1.2:5000` - `privateRegistryAccessConfig` PrivateRegistryAccessConfig — PrivateRegistryAccessConfig contains access configuration for private container registries. - `enabled` boolean — Private registry access is enabled. - `certificateAuthorityDomainConfig` CertificateAuthorityDomainConfig[] — Private registry access configuration. - `fqdns` string[] — List of fully qualified domain names (FQDN). Specifying port is supported. Wildcards are NOT supported. Examples: - `my.customdomain.com` - `10.0.1.2:5000` - `gcpSecretManagerCertificateConfig` GCPSecretManagerCertificateConfig — GCPSecretManagerCertificateConfig configures a secret from [Secret Manager](https://cloud.google.com/secret-manager). - … - `writableCgroups` WritableCgroups — Defines writable cgroups configuration. - `enabled` boolean — Optional. Whether writable cgroups is enabled. - `confidentialNodes` ConfidentialNodes — ConfidentialNodes is configuration for the confidential nodes feature, which makes nodes run on confidential VMs. - `confidentialInstanceType` 'CONFIDENTIAL_INSTANCE_TYPE_UNSPECIFIED' | 'SEV' | 'SEV_SNP' | 'TDX' — Defines the type of technology used by the confidential node. - `enabled` boolean — Whether Confidential Nodes feature is enabled. - `maxRunDuration` string, google-duration — The maximum duration for the nodes to exist. If unspecified, the nodes can exist indefinitely. - `accelerators` AcceleratorConfig[] — A list of hardware accelerators to be attached to each node. See https://cloud.google.com/compute/docs/gpus for more information about support for GPUs. - `gpuSharingConfig` GPUSharingConfig — GPUSharingConfig represents the GPU sharing configuration for Hardware Accelerators. - `maxSharedClientsPerGpu` string, int64 — The max number of containers that can share a physical GPU. - `gpuSharingStrategy` 'GPU_SHARING_STRATEGY_UNSPECIFIED' | 'TIME_SHARING' | 'MPS' — The type of GPU sharing strategy to enable on the GPU node. - `acceleratorType` string — The accelerator type resource name. List of supported accelerators [here](https://cloud.google.com/compute/docs/gpus) - `acceleratorCount` string, int64 — The number of the accelerator cards exposed to an instance. - `gpuDriverInstallationConfig` GPUDriverInstallationConfig — GPUDriverInstallationConfig specifies the version of GPU driver to be auto installed. - `gpuDriverVersion` 'GPU_DRIVER_VERSION_UNSPECIFIED' | 'INSTALLATION_DISABLED' | 'DEFAULT' | 'LATEST' — Mode for how the GPU driver is installed. - `gpuPartitionSize` string — Size of partitions to create on the GPU. Valid values are described in the NVIDIA [mig user guide](https://docs.nvidia.com/datacenter/tesla/mig-user-guide/#partitioning). - `effectiveCgroupMode` 'EFFECTIVE_CGROUP_MODE_UNSPECIFIED' | 'EFFECTIVE_CGROUP_MODE_V1' | 'EFFECTIVE_CGROUP_MODE_V2' — Output only. effective_cgroup_mode is the cgroup mode actually used by the node pool. It is determined by the cgroup mode specified in the LinuxNodeConfig or the default cgroup mode based on the cluster creation version. - `kubeletConfig` NodeKubeletConfig — Node kubelet configs. - `insecureKubeletReadonlyPortEnabled` boolean — Enable or disable Kubelet read only port. - `crashLoopBackOff` CrashLoopBackOffConfig — Contains config to modify node-level parameters for container restart behavior. - `maxContainerRestartPeriod` string — Optional. The maximum duration the backoff delay can accrue to for container restarts, minimum 1 second, maximum 300 seconds. If not set, defaults to the internal crashloopbackoff maximum. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". See https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#configurable-container-restart-delay for more details. - `imageGcLowThresholdPercent` integer — Optional. Defines the percent of disk usage before which image garbage collection is never run. Lowest disk usage to garbage collect to. The percent is calculated as this field value out of 100. The value must be between 10 and 85, inclusive and smaller than image_gc_high_threshold_percent. The default value is 80 if unspecified. - `imageMaximumGcAge` string — Optional. Defines the maximum age an image can be unused before it is garbage collected. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300s", "1.5h", and "2h45m". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". The value must be a positive duration greater than image_minimum_gc_age or "0s". The default value is "0s" if unspecified, which disables this field, meaning images won't be garbage collected based on being unused for too long. - `cpuManagerPolicy` string — Control the CPU management policy on the node. See https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/ The following values are allowed. * "none": the default, which represents the existing scheduling behavior. * "static": allows pods with certain resource characteristics to be granted increased CPU affinity and exclusivity on the node. The default value is 'none' if unspecified. - `cpuCfsQuota` boolean — Enable CPU CFS quota enforcement for containers that specify CPU limits. This option is enabled by default which makes kubelet use CFS quota (https://www.kernel.org/doc/Documentation/scheduler/sched-bwc.txt) to enforce container CPU limits. Otherwise, CPU limits will not be enforced at all. Disable this option to mitigate CPU throttling problems while still having your pods to be in Guaranteed QoS class by specifying the CPU limits. The default value is 'true' if unspecified. - `evictionMinimumReclaim` EvictionMinimumReclaim — Eviction minimum reclaims are the resource amounts of minimum reclaims for each eviction signal. - `memoryAvailable` string — Optional. Minimum reclaim for eviction due to memory available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsInodesFree` string — Optional. Minimum reclaim for eviction due to imagefs inodes free signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsAvailable` string — Optional. Minimum reclaim for eviction due to nodefs available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsAvailable` string — Optional. Minimum reclaim for eviction due to imagefs available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `pidAvailable` string — Optional. Minimum reclaim for eviction due to pid available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsInodesFree` string — Optional. Minimum reclaim for eviction due to nodefs inodes free signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `allowedUnsafeSysctls` string[] — Optional. Defines a comma-separated allowlist of unsafe sysctls or sysctl patterns (ending in `*`). The unsafe namespaced sysctl groups are `kernel.shm*`, `kernel.msg*`, `kernel.sem`, `fs.mqueue.*`, and `net.*`. Leaving this allowlist empty means they cannot be set on Pods. To allow certain sysctls or sysctl patterns to be set on Pods, list them separated by commas. For example: `kernel.msg*,net.ipv4.route.min_pmtu`. See https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/ for more details. - `evictionSoft` EvictionSignals — Eviction signals are the current state of a particular resource at a specific point in time. The kubelet uses eviction signals to make eviction decisions by comparing the signals to eviction thresholds, which are the minimum amount of the resource that should be available on the node. - `memoryAvailable` string — Optional. Memory available (i.e. capacity - workingSet), in bytes. Defines the amount of "memory.available" signal in kubelet. Default is unset, if not specified in the kubelet config. Format: positive number + unit, e.g. 100Ki, 10Mi, 5Gi. Valid units are Ki, Mi, Gi. Must be >= 100Mi and <= 50% of the node's memory. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsInodesFree` string — Optional. Amount of inodes available on filesystem that container runtime uses for storing images layers. Defines the amount of "imagefs.inodesFree" signal in kubelet. Default is unset, if not specified in the kubelet config. Linux only. It takses percentage value for now. Sample format: "30%". Must be >= 5% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsAvailable` string — Optional. Amount of storage available on filesystem that kubelet uses for volumes, daemon logs, etc. Defines the amount of "nodefs.available" signal in kubelet. Default is unset, if not specified in the kubelet config. It takses percentage value for now. Sample format: "30%". Must be >= 10% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsAvailable` string — Optional. Amount of storage available on filesystem that container runtime uses for storing images layers. If the container filesystem and image filesystem are not separate, then imagefs can store both image layers and writeable layers. Defines the amount of "imagefs.available" signal in kubelet. Default is unset, if not specified in the kubelet config. It takses percentage value for now. Sample format: "30%". Must be >= 15% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `pidAvailable` string — Optional. Amount of PID available for pod allocation. Defines the amount of "pid.available" signal in kubelet. Default is unset, if not specified in the kubelet config. It takses percentage value for now. Sample format: "30%". Must be >= 10% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsInodesFree` string — Optional. Amount of inodes available on filesystem that kubelet uses for volumes, daemon logs, etc. Defines the amount of "nodefs.inodesFree" signal in kubelet. Default is unset, if not specified in the kubelet config. Linux only. It takses percentage value for now. Sample format: "30%". Must be >= 5% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `podPidsLimit` string, int64 — Set the Pod PID limits. See https://kubernetes.io/docs/concepts/policy/pid-limiting/#pod-pid-limits Controls the maximum number of processes allowed to run in a pod. The value must be greater than or equal to 1024 and less than 4194304. - `imageGcHighThresholdPercent` integer — Optional. Defines the percent of disk usage after which image garbage collection is always run. The percent is calculated as this field value out of 100. The value must be between 10 and 85, inclusive and greater than image_gc_low_threshold_percent. The default value is 85 if unspecified. - `shutdownGracePeriodCriticalPodsSeconds` integer — Optional. shutdown_grace_period_critical_pods_seconds is the maximum allowed grace period (in seconds) used to terminate critical pods during a node shutdown. This value should be <= shutdown_grace_period_seconds, and is only valid if shutdown_grace_period_seconds is set. https://kubernetes.io/docs/concepts/cluster-administration/node-shutdown/ Range: [0, 120]. - `imageMinimumGcAge` string — Optional. Defines the minimum age for an unused image before it is garbage collected. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300s", "1.5h", and "2h45m". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". The value must be a positive duration less than or equal to 2 minutes. The default value is "2m0s" if unspecified. - `singleProcessOomKill` boolean — Optional. Defines whether to enable single process OOM killer. If true, will prevent the memory.oom.group flag from being set for container cgroups in cgroups v2. This causes processes in the container to be OOM killed individually instead of as a group. - `evictionMaxPodGracePeriodSeconds` integer — Optional. eviction_max_pod_grace_period_seconds is the maximum allowed grace period (in seconds) to use when terminating pods in response to a soft eviction threshold being met. This value effectively caps the Pod's terminationGracePeriodSeconds value during soft evictions. Default: 0. Range: [0, 300]. - `evictionSoftGracePeriod` EvictionGracePeriod — Eviction grace periods are grace periods for each eviction signal. - `nodefsAvailable` string — Optional. Grace period for eviction due to nodefs available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsAvailable` string — Optional. Grace period for eviction due to imagefs available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `pidAvailable` string — Optional. Grace period for eviction due to pid available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsInodesFree` string — Optional. Grace period for eviction due to nodefs inodes free signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `memoryAvailable` string — Optional. Grace period for eviction due to memory available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsInodesFree` string — Optional. Grace period for eviction due to imagefs inodes free signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `maxParallelImagePulls` integer — Optional. Defines the maximum number of image pulls in parallel. The range is 2 to 5, inclusive. The default value is 2 or 3 depending on the disk type. See https://kubernetes.io/docs/concepts/containers/images/#maximum-parallel-image-pulls for more details. - `containerLogMaxSize` string — Optional. Defines the maximum size of the container log file before it is rotated. See https://kubernetes.io/docs/concepts/cluster-administration/logging/#log-rotation Valid format is positive number + unit, e.g. 100Ki, 10Mi. Valid units are Ki, Mi, Gi. The value must be between 10Mi and 500Mi, inclusive. Note that the total container log size (container_log_max_size * container_log_max_files) cannot exceed 1% of the total storage of the node, to avoid disk pressure caused by log files. The default value is 10Mi if unspecified. - `shutdownGracePeriodSeconds` integer — Optional. shutdown_grace_period_seconds is the maximum allowed grace period (in seconds) the total duration that the node should delay the shutdown during a graceful shutdown. This is the total grace period for pod termination for both regular and critical pods. https://kubernetes.io/docs/concepts/cluster-administration/node-shutdown/ If set to 0, node will not enable the graceful node shutdown functionality. This field is only valid for Spot VMs. Allowed values: 0, 30, 120. - `memoryManager` MemoryManager — The option enables the Kubernetes NUMA-aware Memory Manager feature. Detailed description about the feature can be found [here](https://kubernetes.io/docs/tasks/administer-cluster/memory-manager/). - `policy` string — Controls the memory management policy on the Node. See https://kubernetes.io/docs/tasks/administer-cluster/memory-manager/#policies The following values are allowed. * "none" * "static" The default value is 'none' if unspecified. - `topologyManager` TopologyManager — TopologyManager defines the configuration options for the [`kubelet` Topology Manager component](https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/). For more information about the supported machine types and versions for the Topology Manager in GKE, see [Customizing node system configuration](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/node-system-config#kubelet-resource-managers). - `scope` string — The Topology Manager aligns resources in following scopes: * container * pod The default scope is 'container' if unspecified. See https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/#topology-manager-scopes - `policy` string — Configures the strategy for resource alignment. Allowed values are: * none: the default policy, and does not perform any topology alignment. * restricted: the topology manager stores the preferred NUMA node affinity for the container, and will reject the pod if the affinity if not preferred. * best-effort: the topology manager stores the preferred NUMA node affinity for the container. If the affinity is not preferred, the topology manager will admit the pod to the node anyway. * single-numa-node: the topology manager determines if the single NUMA node affinity is possible. If it is, Topology Manager will store this and the Hint Providers can then use this information when making the resource allocation decision. If, however, this is not possible then the Topology Manager will reject the pod from the node. This will result in a pod in a Terminated state with a pod admission failure. The default policy value is 'none' if unspecified. Details about each strategy can be found [here](https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/#topology-manager-policies). - `cpuCfsQuotaPeriod` string — Set the CPU CFS quota period value 'cpu.cfs_period_us'. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". The value must be a positive duration between 1ms and 1 second, inclusive. - `containerLogMaxFiles` integer — Optional. Defines the maximum number of container log files that can be present for a container. See https://kubernetes.io/docs/concepts/cluster-administration/logging/#log-rotation The value must be an integer between 2 and 10, inclusive. The default value is 5 if unspecified. - `satisfiesPzi` boolean — Output only. Reserved for future use. - `controlPlaneEgress` ControlPlaneEgress — ControlPlaneEgress defines the settings needed to enable control plane egress control. - `mode` 'MODE_UNSPECIFIED' | 'VIA_CONTROL_PLANE' | 'NONE' — Defines the mode of control plane egress. - `masterAuth` MasterAuth — The authentication information for accessing the master endpoint. Authentication can be done using HTTP basic auth or using client certificates. - `clientCertificate` string — Output only. Base64-encoded public certificate used by clients to authenticate to the cluster endpoint. Issued only if client_certificate_config is set. - `clientKey` string — Output only. Base64-encoded private key used by clients to authenticate to the cluster endpoint. - `clientCertificateConfig` ClientCertificateConfig — Configuration for client certificates on the cluster. - `issueClientCertificate` boolean — Issue a client certificate. - `username` string — The username to use for HTTP basic authentication to the master endpoint. For clusters v1.6.0 and later, basic authentication can be disabled by leaving username unspecified (or setting it to the empty string). Warning: basic authentication is deprecated, and will be removed in GKE control plane versions 1.19 and newer. For a list of recommended authentication methods, see: https://cloud.google.com/kubernetes-engine/docs/how-to/api-server-authentication - `clusterCaCertificate` string — Output only. Base64-encoded public certificate that is the root of trust for the cluster. - `password` string — The password to use for HTTP basic authentication to the master endpoint. Because the master endpoint is open to the Internet, you should create a strong password. If a password is provided for cluster creation, username must be non-empty. Warning: basic authentication is deprecated, and will be removed in GKE control plane versions 1.19 and newer. For a list of recommended authentication methods, see: https://cloud.google.com/kubernetes-engine/docs/how-to/api-server-authentication - `monitoringService` string — The monitoring service the cluster should use to write metrics. Currently available options: * `monitoring.googleapis.com/kubernetes` - The Cloud Monitoring service with a Kubernetes-native resource model * `monitoring.googleapis.com` - The legacy Cloud Monitoring service (no longer available as of GKE 1.15). * `none` - No metrics will be exported from the cluster. If left as an empty string,`monitoring.googleapis.com/kubernetes` will be used for GKE 1.14+ or `monitoring.googleapis.com` for earlier versions. - `masterAuthorizedNetworksConfig` MasterAuthorizedNetworksConfig — Configuration options for the master authorized networks feature. Enabled master authorized networks will disallow all external traffic to access Kubernetes master through HTTPS except traffic from the given CIDR blocks, Google Compute Engine Public IPs and Google Prod IPs. - `enabled` boolean — Whether or not master authorized networks is enabled. - `cidrBlocks` CidrBlock[] — cidr_blocks define up to 50 external networks that could access Kubernetes master through HTTPS. - `displayName` string — display_name is an optional field for users to identify CIDR blocks. - `cidrBlock` string — cidr_block must be specified in CIDR notation. - `gcpPublicCidrsAccessEnabled` boolean — Whether master is accessible via Google Compute Engine Public IP addresses. - `privateEndpointEnforcementEnabled` boolean — Whether master authorized networks is enforced on private endpoint or not. - `nodePools` NodePool[] — The node pools associated with this cluster. This field should not be set if "node_config" or "initial_node_count" are specified. - `selfLink` string — Output only. Server-defined URL for the resource. - `autopilotConfig` AutopilotConfig — AutopilotConfig contains configuration of autopilot feature for this node pool. - `enabled` boolean — Denotes that nodes belonging to this node pool are Autopilot nodes. - `placementPolicy` PlacementPolicy — PlacementPolicy defines the placement policy used by the node pool. - `type` 'TYPE_UNSPECIFIED' | 'COMPACT' — The type of placement. - `tpuTopology` string — Optional. TPU placement topology for pod slice node pool. https://cloud.google.com/tpu/docs/types-topologies#tpu_topologies - `policyName` string — If set, refers to the name of a custom resource policy supplied by the user. The resource policy must be in the same project and region as the node pool. If not found, InvalidArgument error is returned. - `updateInfo` UpdateInfo — UpdateInfo contains resource (instance groups, etc), status and other intermediate information relevant to a node pool upgrade. - `blueGreenInfo` BlueGreenInfo — Information relevant to blue-green upgrade. - `blueInstanceGroupUrls` string[] — The resource URLs of the [managed instance groups] (/compute/docs/instance-groups/creating-groups-of-managed-instances) associated with blue pool. - `greenPoolVersion` string — Version of green pool. - `phase` 'PHASE_UNSPECIFIED' | 'UPDATE_STARTED' | 'CREATING_GREEN_POOL' | 'CORDONING_BLUE_POOL' | 'DRAINING_BLUE_POOL' | 'NODE_POOL_SOAKING' | 'DELETING_BLUE_POOL' | 'ROLLBACK_STARTED' — Current blue-green upgrade phase. - `greenInstanceGroupUrls` string[] — The resource URLs of the [managed instance groups] (/compute/docs/instance-groups/creating-groups-of-managed-instances) associated with green pool. - `bluePoolDeletionStartTime` string — Time to start deleting blue pool to complete blue-green upgrade, in [RFC3339](https://www.ietf.org/rfc/rfc3339.txt) text format. - `conditions` StatusCondition[] — Output only. Which conditions caused the current node pool state. - `code` 'UNKNOWN' | 'GCE_STOCKOUT' | 'GKE_SERVICE_ACCOUNT_DELETED' | 'GCE_QUOTA_EXCEEDED' | 'SET_BY_OPERATOR' | 'CLOUD_KMS_KEY_ERROR' | 'CA_EXPIRING' | 'NODE_SERVICE_ACCOUNT_MISSING_PERMISSIONS' | 'CLOUD_KMS_KEY_DESTROYED' — Machine-friendly representation of the condition Deprecated. Use canonical_code instead. - `message` string — Human-friendly representation of the condition - `canonicalCode` 'OK' | 'CANCELLED' | 'UNKNOWN' | 'INVALID_ARGUMENT' | 'DEADLINE_EXCEEDED' | 'NOT_FOUND' | 'ALREADY_EXISTS' | 'PERMISSION_DENIED' | 'UNAUTHENTICATED' | 'RESOURCE_EXHAUSTED' | 'FAILED_PRECONDITION' | 'ABORTED' | 'OUT_OF_RANGE' | 'UNIMPLEMENTED' | 'INTERNAL' | 'UNAVAILABLE' | 'DATA_LOSS' — Canonical code of the condition. - `initialNodeCount` integer — The initial node count for the pool. You must ensure that your Compute Engine [resource quota](https://cloud.google.com/compute/quotas) is sufficient for this number of instances. You must also have available firewall and routes quota. - `instanceGroupUrls` string[] — Output only. The resource URLs of the [managed instance groups](https://cloud.google.com/compute/docs/instance-groups/creating-groups-of-managed-instances) associated with this node pool. During the node pool blue-green upgrade operation, the URLs contain both blue and green resources. - `management` NodeManagement — NodeManagement defines the set of node management services turned on for the node pool. - `autoRepair` boolean — A flag that specifies whether the node auto-repair is enabled for the node pool. If enabled, the nodes in this node pool will be monitored and, if they fail health checks too many times, an automatic repair action will be triggered. - `upgradeOptions` AutoUpgradeOptions — AutoUpgradeOptions defines the set of options for the user to control how the Auto Upgrades will proceed. - `autoUpgradeStartTime` string — Output only. This field is set when upgrades are about to commence with the approximate start time for the upgrades, in [RFC3339](https://www.ietf.org/rfc/rfc3339.txt) text format. - `description` string — Output only. This field is set when upgrades are about to commence with the description of the upgrade. - `autoUpgrade` boolean — A flag that specifies whether node auto-upgrade is enabled for the node pool. If enabled, node auto-upgrade helps keep the nodes in your node pool up to date with the latest release version of Kubernetes. - `podIpv4CidrSize` integer — Output only. The pod CIDR block size per node in this node pool. - `maintenancePolicy` NodePoolMaintenancePolicy — Defines the maintenance policy for the node pool. - `exclusionUntilEndOfSupport` ExclusionUntilEndOfSupport — Defines the maintenance exclusion for the node pool. - `endTime` string, google-datetime — Output only. The end time of the maintenance exclusion. It is output only. It is the cluster control plane version's end of support time, or end of extended support time when the cluster is on extended support channel. - `enabled` boolean — Optional. Indicates whether the exclusion is enabled. - `startTime` string, google-datetime — Output only. The start time of the maintenance exclusion. It is output only. It is the exclusion creation time. - `networkConfig` NodeNetworkConfig — Parameters for node pool-level network config. - `podIpv4CidrBlock` string — The IP address range for pod IPs in this node pool. Only applicable if `create_pod_range` is true. Set to blank to have a range chosen with the default size. Set to /netmask (e.g. `/14`) to have a range chosen with a specific netmask. Set to a [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) notation (e.g. `10.96.0.0/14`) to pick a specific range to use. Only applicable if `ip_allocation_policy.use_ip_aliases` is true. This field cannot be changed after the node pool has been created. - `acceleratorNetworkProfile` string — Immutable. The accelerator network profile for the node pool. For now the only valid value is "auto". If specified, the network configuration of the nodes in this node pool will be managed by this profile for the supported machine types, zone, etc. - `networkPerformanceConfig` NetworkPerformanceConfig — Configuration of all network bandwidth tiers - `totalEgressBandwidthTier` 'TIER_UNSPECIFIED' | 'TIER_1' — Specifies the total network bandwidth tier for the NodePool. - `additionalPodNetworkConfigs` AdditionalPodNetworkConfig[] — We specify the additional pod networks for this node pool using this list. Each pod network corresponds to an additional alias IP range for the node - `networkAttachment` string — The name of the network attachment for pods to communicate to; cannot be specified along with subnetwork or secondary_pod_range. - `subnetwork` string — Name of the subnetwork where the additional pod network belongs. - `secondaryPodRange` string — The name of the secondary range on the subnet which provides IP address for this pod range. - `maxPodsPerNode` MaxPodsConstraint — Constraints applied to pods. - `maxPodsPerNode` string, int64 — Constraint enforced on the max num of pods per node. - `additionalNodeNetworkConfigs` AdditionalNodeNetworkConfig[] — We specify the additional node networks for this node pool using this list. Each node network corresponds to an additional interface - `network` string — Name of the VPC where the additional interface belongs - `subnetwork` string — Name of the subnetwork where the additional interface belongs - `networkTierConfig` NetworkTierConfig — NetworkTierConfig contains network tier information. - `networkTier` 'NETWORK_TIER_UNSPECIFIED' | 'NETWORK_TIER_DEFAULT' | 'NETWORK_TIER_PREMIUM' | 'NETWORK_TIER_STANDARD' — Network tier configuration. - `enablePrivateNodes` boolean — Whether nodes have internal IP addresses only. If enable_private_nodes is not specified, then the value is derived from Cluster.NetworkConfig.default_enable_private_nodes - `network` string — Optional. Immutable. The VPC network for the node pool. - `podRange` string — The ID of the secondary range for pod IPs. If `create_pod_range` is true, this ID is used for the new range. If `create_pod_range` is false, uses an existing secondary range with this ID. Only applicable if `ip_allocation_policy.use_ip_aliases` is true. This field cannot be changed after the node pool has been created. - `podCidrOverprovisionConfig` PodCIDROverprovisionConfig — [PRIVATE FIELD] Config for pod CIDR size overprovisioning. - `disable` boolean — Whether Pod CIDR overprovisioning is disabled. Note: Pod CIDR overprovisioning is enabled by default. - `subnetwork` string — Optional. The subnetwork name/path for the node pool. Format: projects/{project}/regions/{region}/subnetworks/{subnetwork} If the cluster is associated with multiple subnetworks, the subnetwork can be either: - A user supplied subnetwork name during node pool creation (e.g., `my-subnet`). The name must be between 1 and 63 characters long, start with a letter, contain only letters, numbers, and hyphens, and end with a letter or a number. - A full subnetwork path during node pool creation, such as `projects/gke-project/regions/us-central1/subnetworks/my-subnet` - A subnetwork path picked based on the IP utilization during node pool creation and is immutable. - `createPodRange` boolean — Input only. Whether to create a new range for pod IPs in this node pool. Defaults are provided for `pod_range` and `pod_ipv4_cidr_block` if they are not specified. If neither `create_pod_range` or `pod_range` are specified, the cluster-level default (`ip_allocation_policy.cluster_ipv4_cidr_block`) is used. Only applicable if `ip_allocation_policy.use_ip_aliases` is true. This field cannot be changed after the node pool has been created. - `podIpv4RangeUtilization` number, double — Output only. The utilization of the IPv4 range for the pod. The ratio is Usage/[Total number of IPs in the secondary range], Usage=numNodes*numZones*podIPsPerNode. - `statusMessage` string — Output only. Deprecated. Use conditions instead. Additional information about the current status of this node pool instance, if available. - `name` string — The name of the node pool. - `version` string — The version of Kubernetes running on this NodePool's nodes. If unspecified, it defaults as described [here](https://cloud.google.com/kubernetes-engine/versioning#specifying_node_version). - `nodeDrainConfig` NodeDrainConfig — NodeDrainConfig contains the node drain related configurations for this node pool. - `pdbTimeoutDuration` string, google-duration — The duration of the PDB timeout period for node drain. - `respectPdbDuringNodePoolDeletion` boolean — Whether to respect PDB during node pool deletion. - `graceTerminationDuration` string, google-duration — The duration of the grace termination period for node drain. - `queuedProvisioning` QueuedProvisioning — QueuedProvisioning defines the queued provisioning used by the node pool. - `enabled` boolean — Denotes that this node pool is QRM specific, meaning nodes can be only obtained through queuing via the Cluster Autoscaler ProvisioningRequest API. - `kubeletCertInfo` KubeletCertInfo — Contains expiry information about the kubelet certificate. - `tpmBootstrapCertExpireTime` string, google-datetime — Output only. - `nonTpmBootstrapCertExpireTime` string, google-datetime — Output only. - `bestEffortProvisioning` BestEffortProvisioning — Best effort provisioning. - `minProvisionNodes` integer — Minimum number of nodes to be provisioned to be considered as succeeded, and the rest of nodes will be provisioned gradually and eventually when stockout issue has been resolved. - `enabled` boolean — When this is enabled, cluster/node pool creations will ignore non-fatal errors like stockout to best provision as many nodes as possible right now and eventually bring up all target number of nodes - `maxPodsConstraint` MaxPodsConstraint — Constraints applied to pods. - `maxPodsPerNode` string, int64 — Constraint enforced on the max num of pods per node. - `upgradeSettings` UpgradeSettings — These upgrade settings control the level of parallelism and the level of disruption caused by an upgrade. maxUnavailable controls the number of nodes that can be simultaneously unavailable. maxSurge controls the number of additional nodes that can be added to the node pool temporarily for the time of the upgrade to increase the number of available nodes. (maxUnavailable + maxSurge) determines the level of parallelism (how many nodes are being upgraded at the same time). Note: upgrades inevitably introduce some disruption since workloads need to be moved from old nodes to new, upgraded ones. Even if maxUnavailable=0, this holds true. (Disruption stays within the limits of PodDisruptionBudget, if it is configured.) Consider a hypothetical node pool with 5 nodes having maxSurge=2, maxUnavailable=1. This means the upgrade process upgrades 3 nodes simultaneously. It creates 2 additional (upgraded) nodes, then it brings down 3 old (not yet upgraded) nodes at the same time. This ensures that there are always at least 4 nodes available. These upgrade settings configure the upgrade strategy for the node pool. Use strategy to switch between the strategies applied to the node pool. If the strategy is ROLLING, use max_surge and max_unavailable to control the level of parallelism and the level of disruption caused by upgrade. 1. maxSurge controls the number of additional nodes that can be added to the node pool temporarily for the time of the upgrade to increase the number of available nodes. 2. maxUnavailable controls the number of nodes that can be simultaneously unavailable. 3. (maxUnavailable + maxSurge) determines the level of parallelism (how many nodes are being upgraded at the same time). If the strategy is BLUE_GREEN, use blue_green_settings to configure the blue-green upgrade related settings. 1. standard_rollout_policy is the default policy. The policy is used to control the way blue pool gets drained. The draining is executed in the batch mode. The batch size could be specified as either percentage of the node pool size or the number of nodes. batch_soak_duration is the soak time after each batch gets drained. 2. node_pool_soak_duration is the soak time after all blue nodes are drained. After this period, the blue pool nodes will be deleted. - `maxUnavailable` integer — The maximum number of nodes that can be simultaneously unavailable during the upgrade process. A node is considered available if its status is Ready. - `maxSurge` integer — The maximum number of nodes that can be created beyond the current size of the node pool during the upgrade process. - `blueGreenSettings` BlueGreenSettings — Settings for blue-green upgrade. - `standardRolloutPolicy` StandardRolloutPolicy — Standard rollout policy is the default policy for blue-green. - `batchNodeCount` integer — Number of blue nodes to drain in a batch. - `batchSoakDuration` string, google-duration — Soak time after each batch gets drained. Default to zero. - `batchPercentage` number, float — Percentage of the blue pool nodes to drain in a batch. The range of this field should be (0.0, 1.0]. - `autoscaledRolloutPolicy` AutoscaledRolloutPolicy — Autoscaled rollout policy utilizes the cluster autoscaler during blue-green upgrade to scale both the blue and green pools. - `waitForDrainDuration` string, google-duration — Optional. Time to wait after cordoning the blue pool before draining the nodes. Defaults to 3 days. The value can be set between 0 and 7 days, inclusive. - `nodePoolSoakDuration` string, google-duration — Time needed after draining entire blue pool. After this period, blue pool will be cleaned up. - `strategy` 'NODE_POOL_UPDATE_STRATEGY_UNSPECIFIED' | 'BLUE_GREEN' | 'SURGE' | 'SHORT_LIVED' — Update strategy of the node pool. - `status` 'STATUS_UNSPECIFIED' | 'PROVISIONING' | 'RUNNING' | 'RUNNING_WITH_ERROR' | 'RECONCILING' | 'STOPPING' | 'ERROR' — Output only. The status of the nodes in this pool instance. - `locations` string[] — The list of Google Compute Engine [zones](https://cloud.google.com/compute/docs/zones#available) in which the NodePool's nodes should be located. If this value is unspecified during node pool creation, the [Cluster.Locations](https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters#Cluster.FIELDS.locations) value will be used, instead. Warning: changing node pool locations will result in nodes being added and/or removed. - `etag` string — Output only. This checksum is computed by the server based on the value of node pool fields, and may be sent on update requests to ensure the client has an up-to-date value before proceeding. - `config` NodeConfig — Parameters that describe the nodes in a cluster. GKE Autopilot clusters do not recognize parameters in `NodeConfig`. Use AutoprovisioningNodePoolDefaults instead. - `taintConfig` TaintConfig — TaintConfig contains the configuration for the taints of the node pool. - `architectureTaintBehavior` 'ARCHITECTURE_TAINT_BEHAVIOR_UNSPECIFIED' | 'NONE' | 'ARM' — Optional. Controls architecture tainting behavior. - `nodeGroup` string — Setting this field will assign instances of this pool to run on the specified node group. This is useful for running workloads on [sole tenant nodes](https://cloud.google.com/compute/docs/nodes/sole-tenant-nodes). - `loggingConfig` NodePoolLoggingConfig — NodePoolLoggingConfig specifies logging configuration for node pools. - `variantConfig` LoggingVariantConfig — LoggingVariantConfig specifies the behaviour of the logging component. - `variant` 'VARIANT_UNSPECIFIED' | 'DEFAULT' | 'MAX_THROUGHPUT' — Logging variant deployed on nodes. - `consolidationDelay` string, google-duration — Consolidation delay defines duration after which the Cluster Autoscaler can scale down underutilized nodes. If not set, nodes are scaled down by default behavior, i.e. according to the chosen autoscaling profile. - `storagePools` string[] — List of Storage Pools where boot disks are provisioned. - `bootDiskKmsKey` string — The Customer Managed Encryption Key used to encrypt the boot disk attached to each node in the node pool. This should be of the form projects/[KEY_PROJECT_ID]/locations/[LOCATION]/keyRings/[RING_NAME]/cryptoKeys/[KEY_NAME]. For more information about protecting resources with Cloud KMS Keys please see: https://cloud.google.com/compute/docs/disks/customer-managed-encryption - `preemptible` boolean — Whether the nodes are created as preemptible VM instances. See: https://cloud.google.com/compute/docs/instances/preemptible for more information about preemptible VM instances. - `spot` boolean — Spot flag for enabling Spot VM, which is a rebrand of the existing preemptible flag. - `secondaryBootDisks` SecondaryBootDisk[] — List of secondary boot disks attached to the nodes. - `diskImage` string — Fully-qualified resource ID for an existing disk image. - `mode` 'MODE_UNSPECIFIED' | 'CONTAINER_IMAGE_CACHE' — Disk mode (container image cache, etc.) - `metadata` object — The metadata key/value pairs assigned to instances in the cluster. Keys must conform to the regexp `[a-zA-Z0-9-_]+` and be less than 128 bytes in length. These are reflected as part of a URL in the metadata server. Additionally, to avoid ambiguity, keys must not conflict with any other metadata keys for the project or be one of the reserved keys: - "cluster-location" - "cluster-name" - "cluster-uid" - "configure-sh" - "containerd-configure-sh" - "enable-os-login" - "gci-ensure-gke-docker" - "gci-metrics-enabled" - "gci-update-strategy" - "instance-template" - "kube-env" - "startup-script" - "user-data" - "disable-address-manager" - "windows-startup-script-ps1" - "common-psm1" - "k8s-node-setup-psm1" - "install-ssh-psm1" - "user-profile-psm1" Values are free-form strings, and only have meaning as interpreted by the image running in the instance. The only restriction placed on them is that each value's size must be less than or equal to 32 KB. The total size of all keys and values must be less than 512 KB. - `minCpuPlatform` string — Minimum CPU platform to be used by this instance. The instance may be scheduled on the specified or newer CPU platform. Applicable values are the friendly names of CPU platforms, such as `minCpuPlatform: "Intel Haswell"` or `minCpuPlatform: "Intel Sandy Bridge"`. For more information, read [how to specify min CPU platform](https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform) - `windowsNodeConfig` WindowsNodeConfig — Parameters that can be configured on Windows nodes. Windows Node Config that define the parameters that will be used to configure the Windows node pool settings. - `osVersion` 'OS_VERSION_UNSPECIFIED' | 'OS_VERSION_LTSC2019' | 'OS_VERSION_LTSC2022' — OSVersion specifies the Windows node config to be used on the node. - `sandboxConfig` SandboxConfig — SandboxConfig contains configurations of the sandbox to use for the node. - `type` 'UNSPECIFIED' | 'GVISOR' — Type of the sandbox to use for the node. - `localSsdEncryptionMode` 'LOCAL_SSD_ENCRYPTION_MODE_UNSPECIFIED' | 'STANDARD_ENCRYPTION' | 'EPHEMERAL_KEY_ENCRYPTION' — Specifies which method should be used for encrypting the Local SSDs attached to the node. - `labels` object — The Kubernetes labels (key/value pairs) to apply to each node. The values in this field are added to the set of default labels Kubernetes applies to nodes. This field has the following restrictions: * Labels must use a valid Kubernetes syntax and character set, as defined in https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set. * This field supports up to 1,024 total characters in a single request. Depending on the Kubernetes version, keys in this field might conflict with the keys of the default labels, which might change which of your labels are applied to the nodes. Assume that the behavior is unpredictable and avoid label key conflicts. For more information about the default labels, see: https://kubernetes.io/docs/reference/labels-annotations-taints/ - `gcfsConfig` GcfsConfig — GcfsConfig contains configurations of Google Container File System (image streaming). - `enabled` boolean — Whether to use GCFS. - `imageType` string — The image type to use for this node. Note that for a given image type, the latest version of it will be used. Please see https://cloud.google.com/kubernetes-engine/docs/concepts/node-images for available image types. - `secondaryBootDiskUpdateStrategy` SecondaryBootDiskUpdateStrategy — SecondaryBootDiskUpdateStrategy is a placeholder which will be extended in the future to define different options for updating secondary boot disks. - `flexStart` boolean — Flex Start flag for enabling Flex Start VM. - `reservationAffinity` ReservationAffinity — [ReservationAffinity](https://cloud.google.com/compute/docs/instances/reserving-zonal-resources) is the configuration of desired reservation which instances could take capacity from. - `consumeReservationType` 'UNSPECIFIED' | 'NO_RESERVATION' | 'ANY_RESERVATION' | 'SPECIFIC_RESERVATION' | 'ANY_RESERVATION_THEN_FAIL' — Corresponds to the type of reservation consumption. - `values` string[] — Corresponds to the label value(s) of reservation resource(s). - `key` string — Corresponds to the label key of a reservation resource. To target a SPECIFIC_RESERVATION by name, specify "compute.googleapis.com/reservation-name" as the key and specify the name of your reservation as its value. - `advancedMachineFeatures` AdvancedMachineFeatures — Specifies options for controlling advanced machine features. - `threadsPerCore` string, int64 — The number of threads per physical core. To disable simultaneous multithreading (SMT) set this to 1. If unset, the maximum number of threads supported per core by the underlying processor is assumed. - `performanceMonitoringUnit` 'PERFORMANCE_MONITORING_UNIT_UNSPECIFIED' | 'ARCHITECTURAL' | 'STANDARD' | 'ENHANCED' — Type of Performance Monitoring Unit (PMU) requested on node pool instances. If unset, PMU will not be available to the node. - `enableNestedVirtualization` boolean — Whether or not to enable nested virtualization (defaults to false). - `bootDisk` BootDisk — BootDisk specifies the boot disk configuration for node pools. - `diskType` string — Disk type of the boot disk. (i.e. Hyperdisk-Balanced, PD-Balanced, etc.) - `sizeGb` string, int64 — Disk size in GB. Replaces NodeConfig.disk_size_gb - `provisionedIops` string, int64 — For Hyperdisk-Balanced only, the provisioned IOPS config value. - `provisionedThroughput` string, int64 — For Hyperdisk-Balanced only, the provisioned throughput config value. - `gvnic` VirtualNIC — Configuration of gVNIC feature. - `enabled` boolean — Whether gVNIC features are enabled in the node pool. - `gpuDirectConfig` GPUDirectConfig — GPUDirectConfig specifies the GPU direct strategy on the node pool. - `gpuDirectStrategy` 'GPU_DIRECT_STRATEGY_UNSPECIFIED' | 'RDMA' — The type of GPU direct strategy to enable on the node pool. - `nodeImageConfig` CustomImageConfig — CustomImageConfig contains the information r - `image` string — The name of the image to use for this node. - `imageProject` string — The project containing the image to use for this node. - `serviceAccount` string — The Google Cloud Platform Service Account to be used by the node VMs. Specify the email address of the Service Account; otherwise, if no Service Account is specified, the "default" service account is used. - `shieldedInstanceConfig` ShieldedInstanceConfig — A set of Shielded Instance options. - `enableIntegrityMonitoring` boolean — Defines whether the instance has integrity monitoring enabled. Enables monitoring and attestation of the boot integrity of the instance. The attestation is performed against the integrity policy baseline. This baseline is initially derived from the implicitly trusted boot image when the instance is created. - `enableSecureBoot` boolean — Defines whether the instance has Secure Boot enabled. Secure Boot helps ensure that the system only runs authentic software by verifying the digital signature of all boot components, and halting the boot process if signature verification fails. - `linuxNodeConfig` LinuxNodeConfig — Parameters that can be configured on Linux nodes. - `hugepages` HugepagesConfig — Hugepages amount in both 2m and 1g size - `hugepageSize2m` integer — Optional. Amount of 2M hugepages - `hugepageSize1g` integer — Optional. Amount of 1G hugepages - `nodeKernelModuleLoading` NodeKernelModuleLoading — Configuration for kernel module loading on nodes. - `policy` 'POLICY_UNSPECIFIED' | 'ENFORCE_SIGNED_MODULES' | 'DO_NOT_ENFORCE_SIGNED_MODULES' — Set the node module loading policy for nodes in the node pool. - `accurateTimeConfig` AccurateTimeConfig — AccurateTimeConfig contains configuration for the accurate time synchronization feature. - `enablePtpKvmTimeSync` boolean — Enables enhanced time synchronization using PTP-KVM. - `transparentHugepageDefrag` 'TRANSPARENT_HUGEPAGE_DEFRAG_UNSPECIFIED' | 'TRANSPARENT_HUGEPAGE_DEFRAG_ALWAYS' | 'TRANSPARENT_HUGEPAGE_DEFRAG_DEFER' | 'TRANSPARENT_HUGEPAGE_DEFRAG_DEFER_WITH_MADVISE' | 'TRANSPARENT_HUGEPAGE_DEFRAG_MADVISE' | 'TRANSPARENT_HUGEPAGE_DEFRAG_NEVER' — Optional. Defines the transparent hugepage defrag configuration on the node. VM hugepage allocation can be managed by either limiting defragmentation for delayed allocation or skipping it entirely for immediate allocation only. See https://docs.kernel.org/admin-guide/mm/transhuge.html for more details. - `swapConfig` SwapConfig — Configuration for swap memory on a node pool. - `encryptionConfig` EncryptionConfig — Defines encryption settings for the swap space. - … - `ephemeralLocalSsdProfile` EphemeralLocalSsdProfile — Swap on the local SSD shared with pod ephemeral storage. - … - `enabled` boolean — Optional. Enables or disables swap for the node pool. - `bootDiskProfile` BootDiskProfile — Swap on the node's boot disk. - … - `dedicatedLocalSsdProfile` DedicatedLocalSsdProfile — Provisions a new, separate local NVMe SSD exclusively for swap. - … - `customNodeInit` CustomNodeInit — Support for running custom init code while bootstrapping nodes. - `initScript` InitScript — InitScript provide a simply bash script to be executed on the node. - … - `diskIoScheduler` DiskIoScheduler — DiskIoScheduler contains the configuration for the disk IO scheduler. - `nodeSystemIoScheduler` string — Optional. Configures the IO scheduler for the boot disk or ephemeral lssd that runs node system workloads. Supported values are `mq-deadline`, `bfq`, `kyber`, `none`. - `nodeAttachedDiskIoScheduler` string — Optional. Configures the IO scheduler for the attached disks. Supported values are `mq-deadline`, `bfq`, `kyber`, `none`. - `transparentHugepageEnabled` 'TRANSPARENT_HUGEPAGE_ENABLED_UNSPECIFIED' | 'TRANSPARENT_HUGEPAGE_ENABLED_ALWAYS' | 'TRANSPARENT_HUGEPAGE_ENABLED_MADVISE' | 'TRANSPARENT_HUGEPAGE_ENABLED_NEVER' — Optional. Transparent hugepage support for anonymous memory can be entirely disabled (mostly for debugging purposes) or only enabled inside MADV_HUGEPAGE regions (to avoid the risk of consuming more memory resources) or enabled system wide. See https://docs.kernel.org/admin-guide/mm/transhuge.html for more details. - `nodeVfioConfig` NodeVfioConfig — Configuration settings for VFIO (Virtual Function I/O) on a node. VFIO allows safe, unprivileged, userspace drivers to access I/O devices. - `dmaEntryLimit` integer — Optional. Specifies the maximum number of DMA entries (pages) that can be mapped by the VFIO IOMMU type 1 driver for a container. This limit affects the total amount of host memory that can be pinned for direct device access, which is often critical for high-performance devices like TPUs and GPUs. This setting corresponds to the kernel parameter at: `/sys/module/vfio_iommu_type1/parameters/dma_entry_limit`. The default value in the kernel is `65535`. Higher values may be needed for workloads mapping large memory regions. Supported values are integers between `65535` and `4194304`. - `sysctls` object — The Linux kernel parameters to be applied to the nodes and all pods running on the nodes. The following parameters are supported. net.core.busy_poll net.core.busy_read net.core.netdev_max_backlog net.core.rmem_max net.core.rmem_default net.core.wmem_default net.core.wmem_max net.core.optmem_max net.core.somaxconn net.ipv4.neigh.default.gc_thresh1 net.ipv4.neigh.default.gc_thresh2 net.ipv4.neigh.default.gc_thresh3 net.ipv4.tcp_rmem net.ipv4.tcp_wmem net.ipv4.tcp_tw_reuse net.ipv4.tcp_mtu_probing net.ipv4.tcp_max_orphans net.ipv4.tcp_max_tw_buckets net.ipv4.tcp_syn_retries net.ipv4.tcp_ecn net.ipv4.tcp_congestion_control net.netfilter.nf_conntrack_max net.netfilter.nf_conntrack_buckets net.netfilter.nf_conntrack_tcp_timeout_close_wait net.netfilter.nf_conntrack_tcp_timeout_time_wait net.netfilter.nf_conntrack_tcp_timeout_established net.netfilter.nf_conntrack_acct kernel.keys.maxkeys kernel.keys.maxbytes kernel.shmmni kernel.shmmax kernel.shmall kernel.core_pattern kernel.perf_event_paranoid kernel.sched_rt_runtime_us kernel.softlockup_panic kernel.yama.ptrace_scope kernel.kptr_restrict kernel.dmesg_restrict kernel.sysrq fs.aio-max-nr fs.file-max fs.inotify.max_user_instances fs.inotify.max_user_watches fs.nr_open vm.dirty_background_ratio vm.dirty_background_bytes vm.dirty_expire_centisecs vm.dirty_ratio vm.dirty_bytes vm.dirty_writeback_centisecs vm.max_map_count vm.overcommit_memory vm.overcommit_ratio vm.vfs_cache_pressure vm.swappiness vm.watermark_scale_factor vm.min_free_kbytes - `cgroupMode` 'CGROUP_MODE_UNSPECIFIED' | 'CGROUP_MODE_V1' | 'CGROUP_MODE_V2' — cgroup_mode specifies the cgroup mode to be used on the node. - `tags` string[] — The list of instance tags applied to all nodes. Tags are used to identify valid sources or targets for network firewalls and are specified by the client during cluster or node pool creation. Each tag within the list must comply with RFC1035. - `soleTenantConfig` SoleTenantConfig — SoleTenantConfig contains the NodeAffinities to specify what shared sole tenant node groups should back the node pool. - `minNodeCpus` integer — Optional. The minimum number of virtual CPUs this instance will consume when running on a sole-tenant node. This field can only be set if the node pool is created in a shared sole-tenant node group. - `nodeAffinities` NodeAffinity[] — NodeAffinities used to match to a shared sole tenant node group. - `values` string[] — Values for NodeAffinity. - `key` string — Key for NodeAffinity. - `operator` 'OPERATOR_UNSPECIFIED' | 'IN' | 'NOT_IN' — Operator for NodeAffinity. - `resourceManagerTags` ResourceManagerTags — A map of resource manager tag keys and values to be attached to the nodes for managing Compute Engine firewalls using Network Firewall Policies. Tags must be according to specifications in https://cloud.google.com/vpc/docs/tags-firewalls-overview#specifications. A maximum of 5 tag key-value pairs can be specified. Existing tags will be replaced with new values. - `tags` object — TagKeyValue must be in one of the following formats ([KEY]=[VALUE]) 1. `tagKeys/{tag_key_id}=tagValues/{tag_value_id}` 2. `{org_id}/{tag_key_name}={tag_value_name}` 3. `{project_id}/{tag_key_name}={tag_value_name}` - `ephemeralStorageLocalSsdConfig` EphemeralStorageLocalSsdConfig — EphemeralStorageLocalSsdConfig contains configuration for the node ephemeral storage using Local SSDs. - `localSsdCount` integer — Number of local SSDs to use to back ephemeral storage. Uses NVMe interfaces. A zero (or unset) value has different meanings depending on machine type being used: 1. For pre-Gen3 machines, which support flexible numbers of local ssds, zero (or unset) means to disable using local SSDs as ephemeral storage. The limit for this value is dependent upon the maximum number of disk available on a machine per zone. See: https://cloud.google.com/compute/docs/disks/local-ssd for more information. 2. For Gen3 machines which dictate a specific number of local ssds, zero (or unset) means to use the default number of local ssds that goes with that machine type. For example, for a c3-standard-8-lssd machine, 2 local ssds would be provisioned. For c3-standard-8 (which doesn't support local ssds), 0 will be provisioned. See https://cloud.google.com/compute/docs/disks/local-ssd#choose_number_local_ssds for more info. - `dataCacheCount` integer — Number of local SSDs to use for GKE Data Cache. - `diskSizeGb` integer — Size of the disk attached to each node, specified in GB. The smallest allowed disk size is 10GB. If unspecified, the default disk size is 100GB. - `enableConfidentialStorage` boolean — Optional. Reserved for future use. - `localSsdCount` integer — The number of local SSD disks to be attached to the node. The limit for this value is dependent upon the maximum number of disks available on a machine per zone. See: https://cloud.google.com/compute/docs/disks/local-ssd for more information. - `taints` NodeTaint[] — List of kubernetes taints to be applied to each node. For more information, including usage and the valid values, see: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/ - `key` string — Key for taint. - `value` string — Value for taint. - `effect` 'EFFECT_UNSPECIFIED' | 'NO_SCHEDULE' | 'PREFER_NO_SCHEDULE' | 'NO_EXECUTE' — Effect for taint. - `diskType` string — Type of the disk attached to each node (e.g. 'pd-standard', 'pd-ssd' or 'pd-balanced') If unspecified, the default disk type is 'pd-standard' - `resourceLabels` object — The resource labels for the node pool to use to annotate any related Google Compute Engine resources. - `workloadMetadataConfig` WorkloadMetadataConfig — WorkloadMetadataConfig defines the metadata configuration to expose to workloads on the node pool. - `mode` 'MODE_UNSPECIFIED' | 'GCE_METADATA' | 'GKE_METADATA' — Mode is the configuration for how to expose metadata to workloads running on the node pool. - `oauthScopes` string[] — The set of Google API scopes to be made available on all of the node VMs under the "default" service account. The following scopes are recommended, but not required, and by default are not included: * `https://www.googleapis.com/auth/compute` is required for mounting persistent storage on your nodes. * `https://www.googleapis.com/auth/devstorage.read_only` is required for communicating with **gcr.io** (the [Artifact Registry](https://cloud.google.com/artifact-registry/)). If unspecified, no scopes are added, unless Cloud Logging or Cloud Monitoring are enabled, in which case their required scopes will be added. - `machineType` string — The name of a Google Compute Engine [machine type](https://cloud.google.com/compute/docs/machine-types) If unspecified, the default machine type is `e2-medium`. - `localNvmeSsdBlockConfig` LocalNvmeSsdBlockConfig — LocalNvmeSsdBlockConfig contains configuration for using raw-block local NVMe SSDs - `localSsdCount` integer — Number of local NVMe SSDs to use. The limit for this value is dependent upon the maximum number of disk available on a machine per zone. See: https://cloud.google.com/compute/docs/disks/local-ssd for more information. A zero (or unset) value has different meanings depending on machine type being used: 1. For pre-Gen3 machines, which support flexible numbers of local ssds, zero (or unset) means to disable using local SSDs as ephemeral storage. 2. For Gen3 machines which dictate a specific number of local ssds, zero (or unset) means to use the default number of local ssds that goes with that machine type. For example, for a c3-standard-8-lssd machine, 2 local ssds would be provisioned. For c3-standard-8 (which doesn't support local ssds), 0 will be provisioned. See https://cloud.google.com/compute/docs/disks/local-ssd#choose_number_local_ssds for more info. - `fastSocket` FastSocket — Configuration of Fast Socket feature. - `enabled` boolean — Whether Fast Socket features are enabled in the node pool. - `containerdConfig` ContainerdConfig — ContainerdConfig contains configuration to customize containerd. - `registryHosts` RegistryHostConfig[] — RegistryHostConfig configures containerd registry host configuration. Each registry_hosts represents a hosts.toml file. At most 25 registry_hosts are allowed. - `hosts` HostConfig[] — HostConfig configures a list of host-specific configurations for the server. Each server can have at most 10 host configurations. - … - `server` string — Defines the host name of the registry server, which will be used to create configuration file as /etc/containerd/hosts.d//hosts.toml. It supports fully qualified domain names (FQDN) and IP addresses: Specifying port is supported, while scheme and path are NOT supported. Wildcards are NOT supported. Examples: - `my.customdomain.com` - `10.0.1.2:5000` - `privateRegistryAccessConfig` PrivateRegistryAccessConfig — PrivateRegistryAccessConfig contains access configuration for private container registries. - `enabled` boolean — Private registry access is enabled. - `certificateAuthorityDomainConfig` CertificateAuthorityDomainConfig[] — Private registry access configuration. - … - `writableCgroups` WritableCgroups — Defines writable cgroups configuration. - `enabled` boolean — Optional. Whether writable cgroups is enabled. - `confidentialNodes` ConfidentialNodes — ConfidentialNodes is configuration for the confidential nodes feature, which makes nodes run on confidential VMs. - `confidentialInstanceType` 'CONFIDENTIAL_INSTANCE_TYPE_UNSPECIFIED' | 'SEV' | 'SEV_SNP' | 'TDX' — Defines the type of technology used by the confidential node. - `enabled` boolean — Whether Confidential Nodes feature is enabled. - `maxRunDuration` string, google-duration — The maximum duration for the nodes to exist. If unspecified, the nodes can exist indefinitely. - `accelerators` AcceleratorConfig[] — A list of hardware accelerators to be attached to each node. See https://cloud.google.com/compute/docs/gpus for more information about support for GPUs. - `gpuSharingConfig` GPUSharingConfig — GPUSharingConfig represents the GPU sharing configuration for Hardware Accelerators. - `maxSharedClientsPerGpu` string, int64 — The max number of containers that can share a physical GPU. - `gpuSharingStrategy` 'GPU_SHARING_STRATEGY_UNSPECIFIED' | 'TIME_SHARING' | 'MPS' — The type of GPU sharing strategy to enable on the GPU node. - `acceleratorType` string — The accelerator type resource name. List of supported accelerators [here](https://cloud.google.com/compute/docs/gpus) - `acceleratorCount` string, int64 — The number of the accelerator cards exposed to an instance. - `gpuDriverInstallationConfig` GPUDriverInstallationConfig — GPUDriverInstallationConfig specifies the version of GPU driver to be auto installed. - `gpuDriverVersion` 'GPU_DRIVER_VERSION_UNSPECIFIED' | 'INSTALLATION_DISABLED' | 'DEFAULT' | 'LATEST' — Mode for how the GPU driver is installed. - `gpuPartitionSize` string — Size of partitions to create on the GPU. Valid values are described in the NVIDIA [mig user guide](https://docs.nvidia.com/datacenter/tesla/mig-user-guide/#partitioning). - `effectiveCgroupMode` 'EFFECTIVE_CGROUP_MODE_UNSPECIFIED' | 'EFFECTIVE_CGROUP_MODE_V1' | 'EFFECTIVE_CGROUP_MODE_V2' — Output only. effective_cgroup_mode is the cgroup mode actually used by the node pool. It is determined by the cgroup mode specified in the LinuxNodeConfig or the default cgroup mode based on the cluster creation version. - `kubeletConfig` NodeKubeletConfig — Node kubelet configs. - `insecureKubeletReadonlyPortEnabled` boolean — Enable or disable Kubelet read only port. - `crashLoopBackOff` CrashLoopBackOffConfig — Contains config to modify node-level parameters for container restart behavior. - `maxContainerRestartPeriod` string — Optional. The maximum duration the backoff delay can accrue to for container restarts, minimum 1 second, maximum 300 seconds. If not set, defaults to the internal crashloopbackoff maximum. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". See https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#configurable-container-restart-delay for more details. - `imageGcLowThresholdPercent` integer — Optional. Defines the percent of disk usage before which image garbage collection is never run. Lowest disk usage to garbage collect to. The percent is calculated as this field value out of 100. The value must be between 10 and 85, inclusive and smaller than image_gc_high_threshold_percent. The default value is 80 if unspecified. - `imageMaximumGcAge` string — Optional. Defines the maximum age an image can be unused before it is garbage collected. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300s", "1.5h", and "2h45m". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". The value must be a positive duration greater than image_minimum_gc_age or "0s". The default value is "0s" if unspecified, which disables this field, meaning images won't be garbage collected based on being unused for too long. - `cpuManagerPolicy` string — Control the CPU management policy on the node. See https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/ The following values are allowed. * "none": the default, which represents the existing scheduling behavior. * "static": allows pods with certain resource characteristics to be granted increased CPU affinity and exclusivity on the node. The default value is 'none' if unspecified. - `cpuCfsQuota` boolean — Enable CPU CFS quota enforcement for containers that specify CPU limits. This option is enabled by default which makes kubelet use CFS quota (https://www.kernel.org/doc/Documentation/scheduler/sched-bwc.txt) to enforce container CPU limits. Otherwise, CPU limits will not be enforced at all. Disable this option to mitigate CPU throttling problems while still having your pods to be in Guaranteed QoS class by specifying the CPU limits. The default value is 'true' if unspecified. - `evictionMinimumReclaim` EvictionMinimumReclaim — Eviction minimum reclaims are the resource amounts of minimum reclaims for each eviction signal. - `memoryAvailable` string — Optional. Minimum reclaim for eviction due to memory available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsInodesFree` string — Optional. Minimum reclaim for eviction due to imagefs inodes free signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsAvailable` string — Optional. Minimum reclaim for eviction due to nodefs available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsAvailable` string — Optional. Minimum reclaim for eviction due to imagefs available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `pidAvailable` string — Optional. Minimum reclaim for eviction due to pid available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsInodesFree` string — Optional. Minimum reclaim for eviction due to nodefs inodes free signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `allowedUnsafeSysctls` string[] — Optional. Defines a comma-separated allowlist of unsafe sysctls or sysctl patterns (ending in `*`). The unsafe namespaced sysctl groups are `kernel.shm*`, `kernel.msg*`, `kernel.sem`, `fs.mqueue.*`, and `net.*`. Leaving this allowlist empty means they cannot be set on Pods. To allow certain sysctls or sysctl patterns to be set on Pods, list them separated by commas. For example: `kernel.msg*,net.ipv4.route.min_pmtu`. See https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/ for more details. - `evictionSoft` EvictionSignals — Eviction signals are the current state of a particular resource at a specific point in time. The kubelet uses eviction signals to make eviction decisions by comparing the signals to eviction thresholds, which are the minimum amount of the resource that should be available on the node. - `memoryAvailable` string — Optional. Memory available (i.e. capacity - workingSet), in bytes. Defines the amount of "memory.available" signal in kubelet. Default is unset, if not specified in the kubelet config. Format: positive number + unit, e.g. 100Ki, 10Mi, 5Gi. Valid units are Ki, Mi, Gi. Must be >= 100Mi and <= 50% of the node's memory. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsInodesFree` string — Optional. Amount of inodes available on filesystem that container runtime uses for storing images layers. Defines the amount of "imagefs.inodesFree" signal in kubelet. Default is unset, if not specified in the kubelet config. Linux only. It takses percentage value for now. Sample format: "30%". Must be >= 5% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsAvailable` string — Optional. Amount of storage available on filesystem that kubelet uses for volumes, daemon logs, etc. Defines the amount of "nodefs.available" signal in kubelet. Default is unset, if not specified in the kubelet config. It takses percentage value for now. Sample format: "30%". Must be >= 10% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsAvailable` string — Optional. Amount of storage available on filesystem that container runtime uses for storing images layers. If the container filesystem and image filesystem are not separate, then imagefs can store both image layers and writeable layers. Defines the amount of "imagefs.available" signal in kubelet. Default is unset, if not specified in the kubelet config. It takses percentage value for now. Sample format: "30%". Must be >= 15% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `pidAvailable` string — Optional. Amount of PID available for pod allocation. Defines the amount of "pid.available" signal in kubelet. Default is unset, if not specified in the kubelet config. It takses percentage value for now. Sample format: "30%". Must be >= 10% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsInodesFree` string — Optional. Amount of inodes available on filesystem that kubelet uses for volumes, daemon logs, etc. Defines the amount of "nodefs.inodesFree" signal in kubelet. Default is unset, if not specified in the kubelet config. Linux only. It takses percentage value for now. Sample format: "30%". Must be >= 5% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `podPidsLimit` string, int64 — Set the Pod PID limits. See https://kubernetes.io/docs/concepts/policy/pid-limiting/#pod-pid-limits Controls the maximum number of processes allowed to run in a pod. The value must be greater than or equal to 1024 and less than 4194304. - `imageGcHighThresholdPercent` integer — Optional. Defines the percent of disk usage after which image garbage collection is always run. The percent is calculated as this field value out of 100. The value must be between 10 and 85, inclusive and greater than image_gc_low_threshold_percent. The default value is 85 if unspecified. - `shutdownGracePeriodCriticalPodsSeconds` integer — Optional. shutdown_grace_period_critical_pods_seconds is the maximum allowed grace period (in seconds) used to terminate critical pods during a node shutdown. This value should be <= shutdown_grace_period_seconds, and is only valid if shutdown_grace_period_seconds is set. https://kubernetes.io/docs/concepts/cluster-administration/node-shutdown/ Range: [0, 120]. - `imageMinimumGcAge` string — Optional. Defines the minimum age for an unused image before it is garbage collected. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300s", "1.5h", and "2h45m". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". The value must be a positive duration less than or equal to 2 minutes. The default value is "2m0s" if unspecified. - `singleProcessOomKill` boolean — Optional. Defines whether to enable single process OOM killer. If true, will prevent the memory.oom.group flag from being set for container cgroups in cgroups v2. This causes processes in the container to be OOM killed individually instead of as a group. - `evictionMaxPodGracePeriodSeconds` integer — Optional. eviction_max_pod_grace_period_seconds is the maximum allowed grace period (in seconds) to use when terminating pods in response to a soft eviction threshold being met. This value effectively caps the Pod's terminationGracePeriodSeconds value during soft evictions. Default: 0. Range: [0, 300]. - `evictionSoftGracePeriod` EvictionGracePeriod — Eviction grace periods are grace periods for each eviction signal. - `nodefsAvailable` string — Optional. Grace period for eviction due to nodefs available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsAvailable` string — Optional. Grace period for eviction due to imagefs available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `pidAvailable` string — Optional. Grace period for eviction due to pid available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsInodesFree` string — Optional. Grace period for eviction due to nodefs inodes free signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `memoryAvailable` string — Optional. Grace period for eviction due to memory available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsInodesFree` string — Optional. Grace period for eviction due to imagefs inodes free signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `maxParallelImagePulls` integer — Optional. Defines the maximum number of image pulls in parallel. The range is 2 to 5, inclusive. The default value is 2 or 3 depending on the disk type. See https://kubernetes.io/docs/concepts/containers/images/#maximum-parallel-image-pulls for more details. - `containerLogMaxSize` string — Optional. Defines the maximum size of the container log file before it is rotated. See https://kubernetes.io/docs/concepts/cluster-administration/logging/#log-rotation Valid format is positive number + unit, e.g. 100Ki, 10Mi. Valid units are Ki, Mi, Gi. The value must be between 10Mi and 500Mi, inclusive. Note that the total container log size (container_log_max_size * container_log_max_files) cannot exceed 1% of the total storage of the node, to avoid disk pressure caused by log files. The default value is 10Mi if unspecified. - `shutdownGracePeriodSeconds` integer — Optional. shutdown_grace_period_seconds is the maximum allowed grace period (in seconds) the total duration that the node should delay the shutdown during a graceful shutdown. This is the total grace period for pod termination for both regular and critical pods. https://kubernetes.io/docs/concepts/cluster-administration/node-shutdown/ If set to 0, node will not enable the graceful node shutdown functionality. This field is only valid for Spot VMs. Allowed values: 0, 30, 120. - `memoryManager` MemoryManager — The option enables the Kubernetes NUMA-aware Memory Manager feature. Detailed description about the feature can be found [here](https://kubernetes.io/docs/tasks/administer-cluster/memory-manager/). - `policy` string — Controls the memory management policy on the Node. See https://kubernetes.io/docs/tasks/administer-cluster/memory-manager/#policies The following values are allowed. * "none" * "static" The default value is 'none' if unspecified. - `topologyManager` TopologyManager — TopologyManager defines the configuration options for the [`kubelet` Topology Manager component](https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/). For more information about the supported machine types and versions for the Topology Manager in GKE, see [Customizing node system configuration](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/node-system-config#kubelet-resource-managers). - `scope` string — The Topology Manager aligns resources in following scopes: * container * pod The default scope is 'container' if unspecified. See https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/#topology-manager-scopes - `policy` string — Configures the strategy for resource alignment. Allowed values are: * none: the default policy, and does not perform any topology alignment. * restricted: the topology manager stores the preferred NUMA node affinity for the container, and will reject the pod if the affinity if not preferred. * best-effort: the topology manager stores the preferred NUMA node affinity for the container. If the affinity is not preferred, the topology manager will admit the pod to the node anyway. * single-numa-node: the topology manager determines if the single NUMA node affinity is possible. If it is, Topology Manager will store this and the Hint Providers can then use this information when making the resource allocation decision. If, however, this is not possible then the Topology Manager will reject the pod from the node. This will result in a pod in a Terminated state with a pod admission failure. The default policy value is 'none' if unspecified. Details about each strategy can be found [here](https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/#topology-manager-policies). - `cpuCfsQuotaPeriod` string — Set the CPU CFS quota period value 'cpu.cfs_period_us'. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". The value must be a positive duration between 1ms and 1 second, inclusive. - `containerLogMaxFiles` integer — Optional. Defines the maximum number of container log files that can be present for a container. See https://kubernetes.io/docs/concepts/cluster-administration/logging/#log-rotation The value must be an integer between 2 and 10, inclusive. The default value is 5 if unspecified. - `autoscaling` NodePoolAutoscaling — NodePoolAutoscaling contains information required by cluster autoscaler to adjust the size of the node pool to the current cluster usage. - `locationPolicy` 'LOCATION_POLICY_UNSPECIFIED' | 'BALANCED' | 'ANY' — Location policy used when scaling up a node pool. - `enabled` boolean — Is autoscaling enabled for this node pool. - `totalMinNodeCount` integer — Minimum number of nodes in the node pool. Must be greater than or equal to 0 and less than or equal to total_max_node_count. The total_*_node_count fields are mutually exclusive with the *_node_count fields. - `minNodeCount` integer — Minimum number of nodes for one location in the node pool. Must be greater than or equal to 0 and less than or equal to max_node_count. - `totalMaxNodeCount` integer — Maximum number of nodes in the node pool. Must be greater than or equal to total_min_node_count. There has to be enough quota to scale up the cluster. The total_*_node_count fields are mutually exclusive with the *_node_count fields. - `autoprovisioned` boolean — Can this node pool be deleted automatically. - `maxNodeCount` integer — Maximum number of nodes for one location in the node pool. Must be >= min_node_count. There has to be enough quota to scale up the cluster. - `managedOpentelemetryConfig` ManagedOpenTelemetryConfig — ManagedOpenTelemetryConfig is the configuration for the GKE Managed OpenTelemetry pipeline. - `scope` 'SCOPE_UNSPECIFIED' | 'NONE' | 'COLLECTION_AND_INSTRUMENTATION_COMPONENTS' — Scope of the Managed OpenTelemetry pipeline. - `autopilot` Autopilot — Autopilot is the configuration for Autopilot settings on the cluster. - `privilegedAdmissionConfig` PrivilegedAdmissionConfig — PrivilegedAdmissionConfig stores the list of authorized allowlist paths for the cluster. - `allowlistPaths` string[] — The customer allowlist Cloud Storage paths for the cluster. These paths are used with the `--autopilot-privileged-admission` flag to authorize privileged workloads in Autopilot clusters. Paths can be GKE-owned, in the format `gke:////`, or customer-owned, in the format `gs:///`. Wildcards (`*`) are supported to authorize all allowlists under specific paths or directories. Example: `gs://my-bucket/*` will authorize all allowlists under the `my-bucket` bucket. - `enabled` boolean — Enable Autopilot - `workloadPolicyConfig` WorkloadPolicyConfig — WorkloadPolicyConfig is the configuration related to GCW workload policy - `allowNetAdmin` boolean — If true, workloads can use NET_ADMIN capability. - `autopilotCompatibilityAuditingEnabled` boolean — If true, enables the GCW Auditor that audits workloads on standard clusters. - `clusterPolicyConfig` ClusterPolicyConfig — ClusterPolicyConfig stores the configuration for cluster wide policies. - `noSystemMutation` boolean — Denotes that preventing creation and mutation of resources in GKE managed namespaces and cluster-scoped GKE managed resources . - `noSystemImpersonation` boolean — Denotes preventing impersonation and CSRs for GKE System users. - `noUnsafeWebhooks` boolean — Denotes preventing unsafe webhooks. - `noStandardNodePools` boolean — Denotes preventing standard node pools and requiring only autopilot node pools. - `workloadIdentityConfig` WorkloadIdentityConfig — Configuration for the use of Kubernetes Service Accounts in IAM policies. - `workloadPool` string — The workload pool to attach all Kubernetes service accounts to. - `monitoringConfig` MonitoringConfig — MonitoringConfig is cluster monitoring configuration. - `managedPrometheusConfig` ManagedPrometheusConfig — ManagedPrometheusConfig defines the configuration for Google Cloud Managed Service for Prometheus. - `enabled` boolean — Enable Managed Collection. - `autoMonitoringConfig` AutoMonitoringConfig — AutoMonitoringConfig defines the configuration for GKE Workload Auto-Monitoring. - `scope` 'SCOPE_UNSPECIFIED' | 'ALL' | 'NONE' — Scope for GKE Workload Auto-Monitoring. - `advancedDatapathObservabilityConfig` AdvancedDatapathObservabilityConfig — AdvancedDatapathObservabilityConfig specifies configuration of observability features of advanced datapath. - `enableMetrics` boolean — Expose flow metrics on nodes - `enableRelay` boolean — Enable Relay component - `relayMode` 'RELAY_MODE_UNSPECIFIED' | 'DISABLED' | 'INTERNAL_VPC_LB' | 'EXTERNAL_LB' — Method used to make Relay available - `componentConfig` MonitoringComponentConfig — MonitoringComponentConfig is cluster monitoring component configuration. - `enableComponents` string[] — Select components to collect metrics. An empty set would disable all monitoring. - `tpuIpv4CidrBlock` string — Output only. The IP address range of the Cloud TPUs in this cluster, in [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) notation (e.g. `1.2.3.4/29`). This field is deprecated due to the deprecation of 2VM TPU. The end of life date for 2VM TPU is 2025-04-25. - `labelFingerprint` string — The fingerprint of the set of labels for this cluster. - `releaseChannel` ReleaseChannel — ReleaseChannel indicates which release channel a cluster is subscribed to. Release channels are arranged in order of risk. When a cluster is subscribed to a release channel, Google maintains both the master version and the node version. Node auto-upgrade defaults to true and cannot be disabled. - `channel` 'UNSPECIFIED' | 'RAPID' | 'REGULAR' | 'STABLE' | 'EXTENDED' — channel specifies which release channel the cluster is subscribed to. - `userManagedKeysConfig` UserManagedKeysConfig — UserManagedKeysConfig holds the resource address to Keys which are used for signing certs and token that are used for communication within cluster. - `clusterCa` string — The Certificate Authority Service caPool to use for the cluster CA in this cluster. - `etcdPeerCa` string — Resource path of the Certificate Authority Service caPool to use for the etcd peer CA in this cluster. - `serviceAccountSigningKeys` string[] — The Cloud KMS cryptoKeyVersions to use for signing service account JWTs issued by this cluster. Format: `projects/{project}/locations/{location}/keyRings/{keyring}/cryptoKeys/{cryptoKey}/cryptoKeyVersions/{cryptoKeyVersion}` - `gkeopsEtcdBackupEncryptionKey` string — Resource path of the Cloud KMS cryptoKey to use for encryption of internal etcd backups. - `serviceAccountVerificationKeys` string[] — The Cloud KMS cryptoKeyVersions to use for verifying service account JWTs issued by this cluster. Format: `projects/{project}/locations/{location}/keyRings/{keyring}/cryptoKeys/{cryptoKey}/cryptoKeyVersions/{cryptoKeyVersion}` - `controlPlaneDiskEncryptionKey` string — The Cloud KMS cryptoKey to use for Confidential Hyperdisk on the control plane nodes. - `etcdApiCa` string — Resource path of the Certificate Authority Service caPool to use for the etcd API CA in this cluster. - `controlPlaneDiskEncryptionKeyVersions` string[] — Output only. All of the versions of the Cloud KMS cryptoKey that are used by Confidential Hyperdisks on the control plane nodes. - `aggregationCa` string — The Certificate Authority Service caPool to use for the aggregation CA in this cluster. - `binaryAuthorization` BinaryAuthorization — Configuration for Binary Authorization. - `enabled` boolean — This field is deprecated. Leave this unset and instead configure BinaryAuthorization using evaluation_mode. If evaluation_mode is set to anything other than EVALUATION_MODE_UNSPECIFIED, this field is ignored. - `evaluationMode` 'EVALUATION_MODE_UNSPECIFIED' | 'DISABLED' | 'PROJECT_SINGLETON_POLICY_ENFORCE' — Mode of operation for binauthz policy evaluation. If unspecified, defaults to DISABLED. - `nodePoolDefaults` NodePoolDefaults — Subset of Nodepool message that has defaults. - `nodeConfigDefaults` NodeConfigDefaults — Subset of NodeConfig message that has defaults. - `loggingConfig` NodePoolLoggingConfig — NodePoolLoggingConfig specifies logging configuration for node pools. - `variantConfig` LoggingVariantConfig — LoggingVariantConfig specifies the behaviour of the logging component. - `variant` 'VARIANT_UNSPECIFIED' | 'DEFAULT' | 'MAX_THROUGHPUT' — Logging variant deployed on nodes. - `containerdConfig` ContainerdConfig — ContainerdConfig contains configuration to customize containerd. - `registryHosts` RegistryHostConfig[] — RegistryHostConfig configures containerd registry host configuration. Each registry_hosts represents a hosts.toml file. At most 25 registry_hosts are allowed. - `hosts` HostConfig[] — HostConfig configures a list of host-specific configurations for the server. Each server can have at most 10 host configurations. - … - `server` string — Defines the host name of the registry server, which will be used to create configuration file as /etc/containerd/hosts.d//hosts.toml. It supports fully qualified domain names (FQDN) and IP addresses: Specifying port is supported, while scheme and path are NOT supported. Wildcards are NOT supported. Examples: - `my.customdomain.com` - `10.0.1.2:5000` - `privateRegistryAccessConfig` PrivateRegistryAccessConfig — PrivateRegistryAccessConfig contains access configuration for private container registries. - `enabled` boolean — Private registry access is enabled. - `certificateAuthorityDomainConfig` CertificateAuthorityDomainConfig[] — Private registry access configuration. - … - `writableCgroups` WritableCgroups — Defines writable cgroups configuration. - `enabled` boolean — Optional. Whether writable cgroups is enabled. - `gcfsConfig` GcfsConfig — GcfsConfig contains configurations of Google Container File System (image streaming). - `enabled` boolean — Whether to use GCFS. - `nodeKubeletConfig` NodeKubeletConfig — Node kubelet configs. - `insecureKubeletReadonlyPortEnabled` boolean — Enable or disable Kubelet read only port. - `crashLoopBackOff` CrashLoopBackOffConfig — Contains config to modify node-level parameters for container restart behavior. - `maxContainerRestartPeriod` string — Optional. The maximum duration the backoff delay can accrue to for container restarts, minimum 1 second, maximum 300 seconds. If not set, defaults to the internal crashloopbackoff maximum. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". See https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#configurable-container-restart-delay for more details. - `imageGcLowThresholdPercent` integer — Optional. Defines the percent of disk usage before which image garbage collection is never run. Lowest disk usage to garbage collect to. The percent is calculated as this field value out of 100. The value must be between 10 and 85, inclusive and smaller than image_gc_high_threshold_percent. The default value is 80 if unspecified. - `imageMaximumGcAge` string — Optional. Defines the maximum age an image can be unused before it is garbage collected. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300s", "1.5h", and "2h45m". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". The value must be a positive duration greater than image_minimum_gc_age or "0s". The default value is "0s" if unspecified, which disables this field, meaning images won't be garbage collected based on being unused for too long. - `cpuManagerPolicy` string — Control the CPU management policy on the node. See https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/ The following values are allowed. * "none": the default, which represents the existing scheduling behavior. * "static": allows pods with certain resource characteristics to be granted increased CPU affinity and exclusivity on the node. The default value is 'none' if unspecified. - `cpuCfsQuota` boolean — Enable CPU CFS quota enforcement for containers that specify CPU limits. This option is enabled by default which makes kubelet use CFS quota (https://www.kernel.org/doc/Documentation/scheduler/sched-bwc.txt) to enforce container CPU limits. Otherwise, CPU limits will not be enforced at all. Disable this option to mitigate CPU throttling problems while still having your pods to be in Guaranteed QoS class by specifying the CPU limits. The default value is 'true' if unspecified. - `evictionMinimumReclaim` EvictionMinimumReclaim — Eviction minimum reclaims are the resource amounts of minimum reclaims for each eviction signal. - `memoryAvailable` string — Optional. Minimum reclaim for eviction due to memory available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsInodesFree` string — Optional. Minimum reclaim for eviction due to imagefs inodes free signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsAvailable` string — Optional. Minimum reclaim for eviction due to nodefs available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsAvailable` string — Optional. Minimum reclaim for eviction due to imagefs available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `pidAvailable` string — Optional. Minimum reclaim for eviction due to pid available signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsInodesFree` string — Optional. Minimum reclaim for eviction due to nodefs inodes free signal. Only take percentage value for now. Sample format: "10%". Must be <=10%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `allowedUnsafeSysctls` string[] — Optional. Defines a comma-separated allowlist of unsafe sysctls or sysctl patterns (ending in `*`). The unsafe namespaced sysctl groups are `kernel.shm*`, `kernel.msg*`, `kernel.sem`, `fs.mqueue.*`, and `net.*`. Leaving this allowlist empty means they cannot be set on Pods. To allow certain sysctls or sysctl patterns to be set on Pods, list them separated by commas. For example: `kernel.msg*,net.ipv4.route.min_pmtu`. See https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/ for more details. - `evictionSoft` EvictionSignals — Eviction signals are the current state of a particular resource at a specific point in time. The kubelet uses eviction signals to make eviction decisions by comparing the signals to eviction thresholds, which are the minimum amount of the resource that should be available on the node. - `memoryAvailable` string — Optional. Memory available (i.e. capacity - workingSet), in bytes. Defines the amount of "memory.available" signal in kubelet. Default is unset, if not specified in the kubelet config. Format: positive number + unit, e.g. 100Ki, 10Mi, 5Gi. Valid units are Ki, Mi, Gi. Must be >= 100Mi and <= 50% of the node's memory. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsInodesFree` string — Optional. Amount of inodes available on filesystem that container runtime uses for storing images layers. Defines the amount of "imagefs.inodesFree" signal in kubelet. Default is unset, if not specified in the kubelet config. Linux only. It takses percentage value for now. Sample format: "30%". Must be >= 5% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsAvailable` string — Optional. Amount of storage available on filesystem that kubelet uses for volumes, daemon logs, etc. Defines the amount of "nodefs.available" signal in kubelet. Default is unset, if not specified in the kubelet config. It takses percentage value for now. Sample format: "30%". Must be >= 10% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsAvailable` string — Optional. Amount of storage available on filesystem that container runtime uses for storing images layers. If the container filesystem and image filesystem are not separate, then imagefs can store both image layers and writeable layers. Defines the amount of "imagefs.available" signal in kubelet. Default is unset, if not specified in the kubelet config. It takses percentage value for now. Sample format: "30%". Must be >= 15% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `pidAvailable` string — Optional. Amount of PID available for pod allocation. Defines the amount of "pid.available" signal in kubelet. Default is unset, if not specified in the kubelet config. It takses percentage value for now. Sample format: "30%". Must be >= 10% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsInodesFree` string — Optional. Amount of inodes available on filesystem that kubelet uses for volumes, daemon logs, etc. Defines the amount of "nodefs.inodesFree" signal in kubelet. Default is unset, if not specified in the kubelet config. Linux only. It takses percentage value for now. Sample format: "30%". Must be >= 5% and <= 50%. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `podPidsLimit` string, int64 — Set the Pod PID limits. See https://kubernetes.io/docs/concepts/policy/pid-limiting/#pod-pid-limits Controls the maximum number of processes allowed to run in a pod. The value must be greater than or equal to 1024 and less than 4194304. - `imageGcHighThresholdPercent` integer — Optional. Defines the percent of disk usage after which image garbage collection is always run. The percent is calculated as this field value out of 100. The value must be between 10 and 85, inclusive and greater than image_gc_low_threshold_percent. The default value is 85 if unspecified. - `shutdownGracePeriodCriticalPodsSeconds` integer — Optional. shutdown_grace_period_critical_pods_seconds is the maximum allowed grace period (in seconds) used to terminate critical pods during a node shutdown. This value should be <= shutdown_grace_period_seconds, and is only valid if shutdown_grace_period_seconds is set. https://kubernetes.io/docs/concepts/cluster-administration/node-shutdown/ Range: [0, 120]. - `imageMinimumGcAge` string — Optional. Defines the minimum age for an unused image before it is garbage collected. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300s", "1.5h", and "2h45m". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". The value must be a positive duration less than or equal to 2 minutes. The default value is "2m0s" if unspecified. - `singleProcessOomKill` boolean — Optional. Defines whether to enable single process OOM killer. If true, will prevent the memory.oom.group flag from being set for container cgroups in cgroups v2. This causes processes in the container to be OOM killed individually instead of as a group. - `evictionMaxPodGracePeriodSeconds` integer — Optional. eviction_max_pod_grace_period_seconds is the maximum allowed grace period (in seconds) to use when terminating pods in response to a soft eviction threshold being met. This value effectively caps the Pod's terminationGracePeriodSeconds value during soft evictions. Default: 0. Range: [0, 300]. - `evictionSoftGracePeriod` EvictionGracePeriod — Eviction grace periods are grace periods for each eviction signal. - `nodefsAvailable` string — Optional. Grace period for eviction due to nodefs available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsAvailable` string — Optional. Grace period for eviction due to imagefs available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `pidAvailable` string — Optional. Grace period for eviction due to pid available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `nodefsInodesFree` string — Optional. Grace period for eviction due to nodefs inodes free signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `memoryAvailable` string — Optional. Grace period for eviction due to memory available signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `imagefsInodesFree` string — Optional. Grace period for eviction due to imagefs inodes free signal. Sample format: "10s". Must be >= 0. See https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/#eviction-signals - `maxParallelImagePulls` integer — Optional. Defines the maximum number of image pulls in parallel. The range is 2 to 5, inclusive. The default value is 2 or 3 depending on the disk type. See https://kubernetes.io/docs/concepts/containers/images/#maximum-parallel-image-pulls for more details. - `containerLogMaxSize` string — Optional. Defines the maximum size of the container log file before it is rotated. See https://kubernetes.io/docs/concepts/cluster-administration/logging/#log-rotation Valid format is positive number + unit, e.g. 100Ki, 10Mi. Valid units are Ki, Mi, Gi. The value must be between 10Mi and 500Mi, inclusive. Note that the total container log size (container_log_max_size * container_log_max_files) cannot exceed 1% of the total storage of the node, to avoid disk pressure caused by log files. The default value is 10Mi if unspecified. - `shutdownGracePeriodSeconds` integer — Optional. shutdown_grace_period_seconds is the maximum allowed grace period (in seconds) the total duration that the node should delay the shutdown during a graceful shutdown. This is the total grace period for pod termination for both regular and critical pods. https://kubernetes.io/docs/concepts/cluster-administration/node-shutdown/ If set to 0, node will not enable the graceful node shutdown functionality. This field is only valid for Spot VMs. Allowed values: 0, 30, 120. - `memoryManager` MemoryManager — The option enables the Kubernetes NUMA-aware Memory Manager feature. Detailed description about the feature can be found [here](https://kubernetes.io/docs/tasks/administer-cluster/memory-manager/). - `policy` string — Controls the memory management policy on the Node. See https://kubernetes.io/docs/tasks/administer-cluster/memory-manager/#policies The following values are allowed. * "none" * "static" The default value is 'none' if unspecified. - `topologyManager` TopologyManager — TopologyManager defines the configuration options for the [`kubelet` Topology Manager component](https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/). For more information about the supported machine types and versions for the Topology Manager in GKE, see [Customizing node system configuration](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/node-system-config#kubelet-resource-managers). - `scope` string — The Topology Manager aligns resources in following scopes: * container * pod The default scope is 'container' if unspecified. See https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/#topology-manager-scopes - `policy` string — Configures the strategy for resource alignment. Allowed values are: * none: the default policy, and does not perform any topology alignment. * restricted: the topology manager stores the preferred NUMA node affinity for the container, and will reject the pod if the affinity if not preferred. * best-effort: the topology manager stores the preferred NUMA node affinity for the container. If the affinity is not preferred, the topology manager will admit the pod to the node anyway. * single-numa-node: the topology manager determines if the single NUMA node affinity is possible. If it is, Topology Manager will store this and the Hint Providers can then use this information when making the resource allocation decision. If, however, this is not possible then the Topology Manager will reject the pod from the node. This will result in a pod in a Terminated state with a pod admission failure. The default policy value is 'none' if unspecified. Details about each strategy can be found [here](https://kubernetes.io/docs/tasks/administer-cluster/topology-manager/#topology-manager-policies). - `cpuCfsQuotaPeriod` string — Set the CPU CFS quota period value 'cpu.cfs_period_us'. The string must be a sequence of decimal numbers, each with optional fraction and a unit suffix, such as "300ms". Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h". The value must be a positive duration between 1ms and 1 second, inclusive. - `containerLogMaxFiles` integer — Optional. Defines the maximum number of container log files that can be present for a container. See https://kubernetes.io/docs/concepts/cluster-administration/logging/#log-rotation The value must be an integer between 2 and 10, inclusive. The default value is 5 if unspecified. - `createTime` string — Output only. The time the cluster was created, in [RFC3339](https://www.ietf.org/rfc/rfc3339.txt) text format. - `loggingService` string — The logging service the cluster should use to write logs. Currently available options: * `logging.googleapis.com/kubernetes` - The Cloud Logging service with a Kubernetes-native resource model * `logging.googleapis.com` - The legacy Cloud Logging service (no longer available as of GKE 1.15). * `none` - no logs will be exported from the cluster. If left as an empty string,`logging.googleapis.com/kubernetes` will be used for GKE 1.14+ or `logging.googleapis.com` for earlier versions. - `legacyAbac` LegacyAbac — Configuration for the legacy Attribute Based Access Control authorization mode. - `enabled` boolean — Whether the ABAC authorizer is enabled for this cluster. When enabled, identities in the system, including service accounts, nodes, and controllers, will have statically granted permissions beyond those provided by the RBAC configuration or IAM. - `loggingConfig` LoggingConfig — LoggingConfig is cluster logging configuration. - `componentConfig` LoggingComponentConfig — LoggingComponentConfig is cluster logging component configuration. - `enableComponents` string[] — Select components to collect logs. An empty set would disable all logging. - `nodeCreationConfig` NodeCreationConfig — NodeCreationConfig defines the settings of node creation mode. - `nodeCreationMode` 'MODE_UNSPECIFIED' | 'VIA_KUBELET' | 'VIA_CONTROL_PLANE' — The mode of node creation. - `defaultMaxPodsConstraint` MaxPodsConstraint — Constraints applied to pods. - `maxPodsPerNode` string, int64 — Constraint enforced on the max num of pods per node. - `network` string — The name of the Google Compute Engine [network](https://cloud.google.com/compute/docs/networks-and-firewalls#networks) to which the cluster is connected. If left unspecified, the `default` network will be used. - `instanceGroupUrls` string[] — Output only. Deprecated. Use node_pools.instance_group_urls. - `privateClusterConfig` PrivateClusterConfig — Configuration options for private clusters. - `privateEndpoint` string — Output only. The internal IP address of this cluster's master endpoint. Deprecated: Use ControlPlaneEndpointsConfig.IPEndpointsConfig.private_endpoint instead. - `enablePrivateEndpoint` boolean — Whether the master's internal IP address is used as the cluster endpoint. Deprecated: Use ControlPlaneEndpointsConfig.IPEndpointsConfig.enable_public_endpoint instead. Note that the value of enable_public_endpoint is reversed: if enable_private_endpoint is false, then enable_public_endpoint will be true. - `masterIpv4CidrBlock` string — The IP range in CIDR notation to use for the hosted master network. This range will be used for assigning internal IP addresses to the master or set of masters, as well as the ILB VIP. This range must not overlap with any other ranges in use within the cluster's network. - `privateEndpointSubnetwork` string — Subnet to provision the master's private endpoint during cluster creation. Specified in projects/*/regions/*/subnetworks/* format. Deprecated: Use ControlPlaneEndpointsConfig.IPEndpointsConfig.private_endpoint_subnetwork instead. - `publicEndpoint` string — Output only. The external IP address of this cluster's master endpoint. Deprecated:Use ControlPlaneEndpointsConfig.IPEndpointsConfig.public_endpoint instead. - `peeringName` string — Output only. The peering name in the customer VPC used by this cluster. - `masterGlobalAccessConfig` PrivateClusterMasterGlobalAccessConfig — Configuration for controlling master global access settings. - `enabled` boolean — Whenever master is accessible globally or not. - `enablePrivateNodes` boolean — Whether nodes have internal IP addresses only. If enabled, all nodes are given only RFC 1918 private addresses and communicate with the master via private networking. Deprecated: Use NetworkConfig.default_enable_private_nodes instead. - `controlPlaneEndpointsConfig` ControlPlaneEndpointsConfig — Configuration for all of the cluster's control plane endpoints. - `dnsEndpointConfig` DNSEndpointConfig — Describes the configuration of a DNS endpoint. - `enableK8sCertsViaDns` boolean — Controls whether the k8s certs auth is allowed via DNS. - `endpoint` string — Output only. The cluster's DNS endpoint configuration. A DNS format address. This is accessible from the public internet. Ex: uid.us-central1.gke.goog. Always present, but the behavior may change according to the value of DNSEndpointConfig.allow_external_traffic. - `allowExternalTraffic` boolean — Controls whether user traffic is allowed over this endpoint. Note that Google-managed services may still use the endpoint even if this is false. - `enableK8sTokensViaDns` boolean — Controls whether the k8s token auth is allowed via DNS. - `ipEndpointsConfig` IPEndpointsConfig — IP endpoints configuration. - `enabled` boolean — Controls whether to allow direct IP access. - `globalAccess` boolean — Controls whether the control plane's private endpoint is accessible from sources in other regions. It is invalid to specify both PrivateClusterMasterGlobalAccessConfig.enabled and this field at the same time. - `authorizedNetworksConfig` MasterAuthorizedNetworksConfig — Configuration options for the master authorized networks feature. Enabled master authorized networks will disallow all external traffic to access Kubernetes master through HTTPS except traffic from the given CIDR blocks, Google Compute Engine Public IPs and Google Prod IPs. - `enabled` boolean — Whether or not master authorized networks is enabled. - `cidrBlocks` CidrBlock[] — cidr_blocks define up to 50 external networks that could access Kubernetes master through HTTPS. - `displayName` string — display_name is an optional field for users to identify CIDR blocks. - `cidrBlock` string — cidr_block must be specified in CIDR notation. - `gcpPublicCidrsAccessEnabled` boolean — Whether master is accessible via Google Compute Engine Public IP addresses. - `privateEndpointEnforcementEnabled` boolean — Whether master authorized networks is enforced on private endpoint or not. - `publicEndpoint` string — Output only. The external IP address of this cluster's control plane. Only populated if enabled. - `enablePublicEndpoint` boolean — Controls whether the control plane allows access through a public IP. It is invalid to specify both PrivateClusterConfig.enablePrivateEndpoint and this field at the same time. - `privateEndpointSubnetwork` string — Subnet to provision the master's private endpoint during cluster creation. Specified in projects/*/regions/*/subnetworks/* format. It is invalid to specify both PrivateClusterConfig.privateEndpointSubnetwork and this field at the same time. - `privateEndpoint` string — Output only. The internal IP address of this cluster's control plane. Only populated if enabled. - `securityPostureConfig` SecurityPostureConfig — SecurityPostureConfig defines the flags needed to enable/disable features for the Security Posture API. - `mode` 'MODE_UNSPECIFIED' | 'DISABLED' | 'BASIC' | 'ENTERPRISE' — Sets which mode to use for Security Posture features. - `vulnerabilityMode` 'VULNERABILITY_MODE_UNSPECIFIED' | 'VULNERABILITY_DISABLED' | 'VULNERABILITY_BASIC' | 'VULNERABILITY_ENTERPRISE' — Sets which mode to use for vulnerability scanning. - `networkConfig` NetworkConfig — NetworkConfig reports the relative names of network & subnetwork. - `serviceExternalIpsConfig` ServiceExternalIPsConfig — Config to block services with externalIPs field. - `enabled` boolean — Whether Services with ExternalIPs field are allowed or not. - `datapathProvider` 'DATAPATH_PROVIDER_UNSPECIFIED' | 'LEGACY_DATAPATH' | 'ADVANCED_DATAPATH' — The desired datapath provider for this cluster. By default, uses the IPTables-based kube-proxy implementation. - `networkPerformanceConfig` ClusterNetworkPerformanceConfig — Configuration of network bandwidth tiers - `totalEgressBandwidthTier` 'TIER_UNSPECIFIED' | 'TIER_1' — Specifies the total network bandwidth tier for NodePools in the cluster. - `gatewayApiConfig` GatewayAPIConfig — GatewayAPIConfig contains the desired config of Gateway API on this cluster. - `channel` 'CHANNEL_UNSPECIFIED' | 'CHANNEL_DISABLED' | 'CHANNEL_EXPERIMENTAL' | 'CHANNEL_STANDARD' — The Gateway API release channel to use for Gateway API. - `defaultSnatStatus` DefaultSnatStatus — DefaultSnatStatus contains the desired state of whether default sNAT should be disabled on the cluster. - `disabled` boolean — Disables cluster default sNAT rules. - `dnsConfig` DNSConfig — DNSConfig contains the desired set of options for configuring clusterDNS. - `clusterDnsScope` 'DNS_SCOPE_UNSPECIFIED' | 'CLUSTER_SCOPE' | 'VPC_SCOPE' — cluster_dns_scope indicates the scope of access to cluster DNS records. - `additiveVpcScopeDnsDomain` string — Optional. The domain used in Additive VPC scope. - `clusterDns` 'PROVIDER_UNSPECIFIED' | 'PLATFORM_DEFAULT' | 'CLOUD_DNS' | 'KUBE_DNS' — cluster_dns indicates which in-cluster DNS provider should be used. - `clusterDnsDomain` string — cluster_dns_domain is the suffix used for all cluster service records. - `inTransitEncryptionConfig` 'IN_TRANSIT_ENCRYPTION_CONFIG_UNSPECIFIED' | 'IN_TRANSIT_ENCRYPTION_DISABLED' | 'IN_TRANSIT_ENCRYPTION_INTER_NODE_TRANSPARENT' — Specify the details of in-transit encryption. Now named inter-node transparent encryption. - `defaultEnablePrivateNodes` boolean — Controls whether by default nodes have private IP addresses only. It is invalid to specify both PrivateClusterConfig.enablePrivateNodes and this field at the same time. To update the default setting, use ClusterUpdate.desired_default_enable_private_nodes - `enableFqdnNetworkPolicy` boolean — Whether FQDN Network Policy is enabled on this cluster. - `enableCiliumClusterwideNetworkPolicy` boolean — Whether CiliumClusterwideNetworkPolicy is enabled on this cluster. - `network` string — Output only. The relative name of the Google Compute Engine [network](https://cloud.google.com/compute/docs/networks-and-firewalls#networks) to which the cluster is connected. Example: projects/my-project/global/networks/my-network - `enableIntraNodeVisibility` boolean — Whether Intra-node visibility is enabled for this cluster. This makes same node pod to pod traffic visible for VPC network. - `enableL4ilbSubsetting` boolean — Whether L4ILB Subsetting is enabled for this cluster. - `enableMultiNetworking` boolean — Whether multi-networking is enabled for this cluster. - `disableL4LbFirewallReconciliation` boolean — Disable L4 load balancer VPC firewalls to enable firewall policies. - `subnetwork` string — Output only. The relative name of the Google Compute Engine [subnetwork](https://cloud.google.com/compute/docs/vpc) to which the cluster is connected. Example: projects/my-project/regions/us-central1/subnetworks/my-subnet - `privateIpv6GoogleAccess` 'PRIVATE_IPV6_GOOGLE_ACCESS_UNSPECIFIED' | 'PRIVATE_IPV6_GOOGLE_ACCESS_DISABLED' | 'PRIVATE_IPV6_GOOGLE_ACCESS_TO_GOOGLE' | 'PRIVATE_IPV6_GOOGLE_ACCESS_BIDIRECTIONAL' — The desired state of IPv6 connectivity to Google Services. By default, no private IPv6 access to or from Google Services (all access will be via IPv4) - `dataplaneV2Config` DataplaneV2Config — DataplaneV2Config is the configuration for DPv2. - `scalabilityMode` 'SCALABILITY_MODE_UNSPECIFIED' | 'DISABLED' | 'SCALE_OPTIMIZED' — Optional. Scalability mode for the cluster. - `statusMessage` string — Output only. Deprecated. Use conditions instead. Additional information about the current status of this cluster, if available. - `servicesIpv4Cidr` string — Output only. The IP address range of the Kubernetes services in this cluster, in [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) notation (e.g. `1.2.3.4/29`). Service addresses are typically put in the last `/16` from the container CIDR. - `enableK8sBetaApis` K8sBetaAPIConfig — K8sBetaAPIConfig , configuration for beta APIs - `enabledApis` string[] — Enabled k8s beta APIs. - `clusterIpv4Cidr` string — The IP address range of the container pods in this cluster, in [CIDR](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) notation (e.g. `10.96.0.0/14`). Leave blank to have one automatically chosen or specify a `/14` block in `10.0.0.0/8`. - `anonymousAuthenticationConfig` AnonymousAuthenticationConfig — AnonymousAuthenticationConfig defines the settings needed to limit endpoints that allow anonymous authentication. - `mode` 'MODE_UNSPECIFIED' | 'ENABLED' | 'LIMITED' — Defines the mode of limiting anonymous access in the cluster. - `parent` string — The parent (project and location) where the cluster will be created. Specified in the format `projects/*/locations/*`. ## Response `200` Successful response --- [API](https://skmtc.net/google/apis/container.md) · [All operations](https://skmtc.net/google/apis/container/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/google/container/versions/f20e7f9e2240/schema)