Package-level declarations
Types
AcceleratorConfig represents a Hardware Accelerator request.
AdditionalPodRangesConfig is the configuration for additional pod secondary ranges supporting the ClusterUpdate message.
Configuration for the addons that can be automatically spun up in the cluster, enabling additional functionality.
Specifies options for controlling advanced machine features.
Configuration for returning group information from authenticators.
Autopilot is the configuration for Autopilot settings on the cluster.
AutoprovisioningNodePoolDefaults contains defaults for a node pool created by NAP.
AutoUpgradeOptions defines the set of options for the user to control how the Auto Upgrades will proceed.
Parameters for using BigQuery as the destination of resource usage export.
Configuration for Binary Authorization.
Settings for blue-green upgrade.
CidrBlock contains an optional name and one CIDR block.
Configuration for client certificates on the cluster.
Configuration options for the Cloud Run feature.
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.
ConfidentialNodes is configuration for the confidential nodes feature, which makes nodes run on confidential VMs.
Configuration options for the Config Connector add-on.
Parameters for controlling consumption metering.
Configuration for fine-grained cost management feature.
Time window specified for daily maintenance operations.
Configuration of etcd encryption.
DefaultSnatStatus contains the desired state of whether default sNAT should be disabled on the cluster.
Configuration for NodeLocal DNSCache
DNSConfig contains the desired set of options for configuring clusterDNS.
EphemeralStorageLocalSsdConfig contains configuration for the node ephemeral storage using Local SSD.
Configuration of Fast Socket feature.
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
Fleet is the fleet configuration for the cluster.
GatewayAPIConfig contains the desired config of Gateway API on this cluster.
Configuration for the Compute Engine PD CSI driver.
GcfsConfig contains configurations of Google Container File System (image streaming).
Configuration for the GCP Filestore CSI driver.
Configuration for the Backup for GKE Agent.
GPUSharingConfig represents the GPU sharing configuration for Hardware Accelerators.
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.
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.
IdentityServiceConfig is configuration for Identity Service which allows customers to use external identity providers with the K8S API
Configuration for controlling how IPs are allocated in the cluster.
Configuration for the Kubernetes Dashboard.
Configuration for the legacy Attribute Based Access Control authorization mode.
Parameters that can be configured on Linux nodes.
LocalNvmeSsdBlockConfig contains configuration for using raw-block local NVMe SSD.
LoggingComponentConfig is cluster logging component configuration.
LoggingConfig is cluster logging configuration.
LoggingVariantConfig specifies the behaviour of the logging component.
Represents the Maintenance exclusion option.
MaintenancePolicy defines the maintenance policy to be used for the cluster.
MaintenanceWindow defines the maintenance window to be used for the cluster.
ManagedPrometheusConfig defines the configuration for Google Cloud Managed Service for Prometheus.
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.
The authentication information for accessing the master endpoint. Authentication can be done using HTTP basic auth or using client certificates.
Constraints applied to pods.
Configuration for issuance of mTLS keys and certificates to Kubernetes pods.
MonitoringComponentConfig is cluster monitoring component configuration.
MonitoringConfig is cluster monitoring configuration.
NetworkConfig reports the relative names of network & subnetwork.
Configuration of all network bandwidth tiers
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.
Configuration options for the NetworkPolicy feature. https://kubernetes.io/docs/concepts/services-networking/networkpolicies/
Collection of Compute Engine network tags that can be applied to a node's underlying VM instance.
Subset of NodeConfig message that has defaults.
Parameters that describe the nodes in a cluster. GKE Autopilot clusters do not recognize parameters in NodeConfig
. Use AutoprovisioningNodePoolDefaults instead.
Node kubelet configs.
NodeManagement defines the set of node management services turned on for the node pool.
Parameters for node pool-level network config.
Node pool configs that apply to all auto-provisioned node pools in autopilot clusters and node auto-provisioning enabled clusters.
NodePoolAutoscaling contains information required by cluster autoscaler to adjust the size of the node pool to the current cluster usage.
Subset of Nodepool message that has defaults.
NodePoolLoggingConfig specifies logging configuration for nodepools.
NodePool contains the name and configuration for a cluster's node pool. Node pools are a set of nodes (i.e. VM's), with a common configuration and specification, under the control of the cluster master. They may have a set of Kubernetes labels applied to them, which may be used to reference them during pod scheduling. They may also be resized up or down, to accommodate the workload.
Kubernetes taint is composed of three fields: key, value, and effect. Effect can only be one of three types: NoSchedule, PreferNoSchedule or NoExecute. See here for more information, including usage and the valid values.
NotificationConfig is the configuration of notifications.
PlacementPolicy defines the placement policy used by the node pool.
PRIVATE FIELD Config for pod CIDR size overprovisioning.
Configuration options for private clusters.
Configuration for controlling master global access settings.
Pub/Sub specific notification config.
Represents an arbitrary window of time that recurs.
ReleaseChannelConfig exposes configuration for a release channel.
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.
ReservationAffinity is the configuration of desired reservation which instances could take capacity from.
Contains information about amount of some resource in the cluster. For memory, value should be in GB.
Configuration for exporting cluster resource usages.
SandboxConfig contains configurations of the sandbox to use for the node.
Config to block services with externalIPs field.
A set of Shielded Instance options.
Configuration of Shielded Nodes feature.
Standard rollout policy is the default policy for blue-green.
StatusCondition describes why a cluster or a node pool has a certain status (e.g., ERROR or DEGRADED).
Represents an arbitrary window of time.
UpdateInfo contains resource (instance groups, etc), status and other intermediate information relevant to a node pool upgrade.
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.
VerticalPodAutoscaling contains global, per-cluster information required by Vertical Pod Autoscaler to automatically adjust the resources of pods controlled by it.
Configuration of gVNIC feature.
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
Configuration for the use of Kubernetes Service Accounts in GCP IAM policies.
WorkloadMetadataConfig defines the metadata configuration to expose to workloads on the node pool.