google.cloud.gcp_container_cluster module – Creates a GCP Cluster
Note
This module is part of the google.cloud collection (version 1.0.2).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install google.cloud
.
To use it in a playbook, specify: google.cloud.gcp_container_cluster
.
Requirements
The below requirements are needed on the host that executes this module.
python >= 2.6
requests >= 2.18.4
google-auth >= 1.3.0
Parameters
Parameter |
Comments |
---|---|
Configurations for the various addons available to run in the cluster. |
|
Configuration 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. |
|
Whether the Horizontal Pod Autoscaling feature is enabled in the cluster. When enabled, it ensures that a Heapster pod is running in the cluster, which is also used by the Cloud Monitoring service. Choices:
|
|
Configuration for the HTTP (L7) load balancing controller addon, which makes it easy to set up HTTP load balancers for services in a cluster. |
|
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. Choices:
|
|
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. |
|
Whether NetworkPolicy is enabled for this cluster. Choices:
|
|
The type of credential used. Choices:
|
|
Configuration for the BinaryAuthorization feature. |
|
If enabled, all container images will be validated by Binary Authorization. Choices:
|
|
The IP address range of the container pods in this cluster, in CIDR 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. |
|
Configuration of etcd encryption. |
|
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 . |
|
Denotes the state of etcd encryption. Some valid choices include: “ENCRYPTED”, “DECRYPTED” |
|
The default constraint on the maximum number of pods that can be run simultaneously on a node in the node pool of this cluster. Only honored if cluster created with IP Alias support. |
|
Constraint enforced on the max num of pods per node. |
|
An optional description of this cluster. |
|
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. Choices:
|
|
(Optional) Whether to enable Cloud TPU resources in this cluster. See the official documentation - https://cloud.google.com/tpu/docs/kubernetes-engine-setup . Choices:
|
|
Specifies which Ansible environment you’re running this module within. This should not be set unless you know what you’re doing. This only alters the User Agent string for any API requests. |
|
The software version of the master endpoint and kubelets used in the cluster when it was first created. The version can be upgraded over time. |
|
The number of nodes to create in this cluster. You must ensure that your Compute Engine resource quota 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 “nodePool” object, since this configuration (along with the “nodeConfig”) will be used to create a “NodePool” object with an auto-generated name. Do not use this and a nodePool at the same time. This field has been deprecated. Please use nodePool.initial_node_count instead. |
|
Configuration for controlling how IPs are allocated in the cluster. |
|
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 useIpAliases 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. |
|
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 . |
|
Whether a new subnetwork will be created automatically for the cluster. Choices:
|
|
The IP address range of the instance IPs in this cluster. This is applicable only if createSubnetwork 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. |
|
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 useIpAliases 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. |
|
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. |
|
A custom subnetwork name to be used if createSubnetwork is true. If this field is empty, then an automatic name will be chosen for the new subnetwork. |
|
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 useIpAliases 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. |
|
Whether alias IPs will be used for pod IPs in the cluster. Choices:
|
|
The name of the context for the kubectl config file. Will default to the cluster name. |
|
The path that the kubectl config file will be written to. The file will not be created if this path is unset. Any existing file at this path will be completely overwritten. This requires the PyYaml library. |
|
Configuration for the legacy ABAC authorization mode. |
|
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. Choices:
|
|
The location where the cluster is deployed. |
|
The list of Google Compute Engine zones in which the cluster’s nodes should be located. |
|
The logging service the cluster should use to write logs. Currently available options: logging.googleapis.com - the Google Cloud Logging service. none - no logs will be exported from the cluster. if left as an empty string,logging.googleapis.com will be used. Some valid choices include: “logging.googleapis.com”, “none” |
|
The authentication information for accessing the master endpoint. |
|
Configuration for client certificate authentication on the cluster. For clusters before v1.12, if no configuration is specified, a client certificate is issued. |
|
Issue a client certificate. Choices:
|
|
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 with a minimum of 16 characters. |
|
The username to use for HTTP basic authentication to the master endpoint. |
|
Configuration for controlling how IPs are allocated in the cluster. |
|
Define up to 50 external networks that could access Kubernetes master through HTTPS. |
|
Block specified in CIDR notation. |
|
Optional field used to identify cidr blocks. |
|
Whether or not master authorized networks is enabled. Choices:
|
|
The monitoring service the cluster should use to write metrics. Currently available options: monitoring.googleapis.com - the Google Cloud Monitoring service. none - no metrics will be exported from the cluster. if left as an empty string, monitoring.googleapis.com will be used. Some valid choices include: “monitoring.googleapis.com”, “none” |
|
The name of this cluster. The name must be unique within this project and location, and can be up to 40 characters. Must be Lowercase letters, numbers, and hyphens only. Must start with a letter. Must end with a number or a letter. |
|
The name of the Google Compute Engine network to which the cluster is connected. If left unspecified, the default network will be used. |
|
Network configurations . |
|
Whether the cluster disables default in-node sNAT rules. In-node sNAT rules will be disabled when defaultSnatStatus is disabled. Choices:
|
|
Whether Intra-node visibility is enabled for this cluster. This makes same node pod to pod traffic visible for VPC network. Choices:
|
|
Configuration options for the NetworkPolicy feature. |
|
Whether network policy is enabled on the cluster. Choices:
|
|
The selected network policy provider. Some valid choices include: “PROVIDER_UNSPECIFIED”, “CALICO” |
|
Parameters used in creating the cluster’s nodes. For requests, this field should only be used in lieu of a “nodePool” object, since this configuration (along with the “initialNodeCount”) will be used to create a “NodePool” object with an auto-generated name. Do not use this and a nodePool at the same time. For responses, this field will be populated with the node configuration of the first node pool. If unspecified, the defaults are used. |
|
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. |
|
The number of accelerator cards exposed to an instance. |
|
The accelerator type resource name. |
|
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. |
|
Type of the disk attached to each node (e.g. ‘pd-standard’ or ‘pd-ssd’) If unspecified, the default disk type is ‘pd-standard’ . |
|
The image type to use for this node. Note that for a given image type, the latest version of it will be used. |
|
The map of Kubernetes labels (key/value pairs) to be applied to each node. These will added in addition to any default label(s) that Kubernetes may apply to the node. In case of conflict in label keys, the applied set may differ depending on the Kubernetes version – it’s best to assume the behavior is undefined and conflicts should be avoided. For more information, including usage and the valid values, see: http://kubernetes.io/v1.1/docs/user-guide/labels.html An object containing a list of “key”: value pairs. Example: { “name”: “wrench”, “mass”: “1.3kg”, “count”: “3” }. |
|
The number of local SSD disks to be attached to the node. The limit for this value is dependant upon the maximum number of disks available on a machine per zone. See: https://cloud.google.com/compute/docs/disks/local-ssd#local_ssd_limits for more information. |
|
The name of a Google Compute Engine machine type (e.g. n1-standard-1). If unspecified, the default machine type is n1-standard-1. |
|
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 four reserved keys: “instance-template”, “kube-env”, “startup-script”, and “user-data” 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. An object containing a list of “key”: value pairs. Example: { “name”: “wrench”, “mass”: “1.3kg”, “count”: “3” }. |
|
Minimum CPU platform to be used by this instance. The instance may be scheduled on the specified or newer CPU platform. |
|
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 Google Container Registry). If unspecified, no scopes are added, unless Cloud Logging or Cloud Monitoring are enabled, in which case their required scopes will be added. |
|
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. Choices:
|
|
The Google Cloud Platform Service Account to be used by the node VMs. If no Service Account is specified, the “default” service account is used. |
|
Shielded Instance options. |
|
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. Choices:
|
|
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. Choices:
|
|
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. |
|
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/ . |
|
Effect for taint. Some valid choices include: “EFFECT_UNSPECIFIED”, “NO_SCHEDULE”, “PREFER_NO_SCHEDULE”, “NO_EXECUTE” |
|
Key for taint. |
|
Value for taint. |
|
Configuration for a private cluster. |
|
Whether the master’s internal IP address is used as the cluster endpoint. Choices:
|
|
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. Choices:
|
|
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. |
|
The Google Cloud Platform project to use. |
|
ReleaseChannel indicates which release channel a cluster is subscribed to. Release channels are arranged in order of risk and frequency of updates. |
|
Which release channel the cluster is subscribed to. Some valid choices include: “UNSPECIFIED”, “RAPID”, “REGULAR”, “STABLE” |
|
The resource labels for the cluster to use to annotate any related Google Compute Engine resources. |
|
Array of scopes to be used |
|
The contents of a Service Account JSON file, either in a dictionary or as a JSON string that represents it. |
|
An optional service account email address if machineaccount is selected and the user does not wish to use the default email. |
|
The path of a Service Account JSON file if serviceaccount is selected as type. |
|
Shielded Nodes configuration. |
|
Whether Shielded Nodes features are enabled on all nodes in this cluster. Choices:
|
|
Whether the given object should exist in GCP Choices:
|
|
The name of the Google Compute Engine subnetwork to which the cluster is connected. |
Examples
- name: create a cluster
google.cloud.gcp_container_cluster:
name: my-cluster
initial_node_count: 2
master_auth:
username: cluster_admin
password: my-secret-password
node_config:
machine_type: n1-standard-4
disk_size_gb: 500
location: us-central1-a
project: test_project
auth_kind: serviceaccount
service_account_file: "/tmp/auth.pem"
state: present
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
Configurations for the various addons available to run in the cluster. Returned: success |
|
Configuration 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. Returned: success |
|
Whether the Horizontal Pod Autoscaling feature is enabled in the cluster. When enabled, it ensures that a Heapster pod is running in the cluster, which is also used by the Cloud Monitoring service. Returned: success |
|
Configuration for the HTTP (L7) load balancing controller addon, which makes it easy to set up HTTP load balancers for services in a cluster. Returned: success |
|
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. Returned: success |
|
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. Returned: success |
|
Whether NetworkPolicy is enabled for this cluster. Returned: success |
|
Configuration for the BinaryAuthorization feature. Returned: success |
|
If enabled, all container images will be validated by Binary Authorization. Returned: success |
|
The IP address range of the container pods in this cluster, in CIDR 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. Returned: success |
|
Which conditions caused the current cluster state. Returned: success |
|
Machine-friendly representation of the condition. Returned: success |
|
Human-friendly representation of the condition. Returned: success |
|
The time the cluster was created, in RFC3339 text format. Returned: success |
|
The current software version of the master endpoint. Returned: success |
|
The number of nodes currently in the cluster. Returned: success |
|
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. Returned: success |
|
Configuration of etcd encryption. Returned: success |
|
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 . Returned: success |
|
Denotes the state of etcd encryption. Returned: success |
|
The default constraint on the maximum number of pods that can be run simultaneously on a node in the node pool of this cluster. Only honored if cluster created with IP Alias support. Returned: success |
|
Constraint enforced on the max num of pods per node. Returned: success |
|
An optional description of this cluster. Returned: success |
|
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. Returned: success |
|
(Optional) Whether to enable Cloud TPU resources in this cluster. See the official documentation - https://cloud.google.com/tpu/docs/kubernetes-engine-setup . Returned: success |
|
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. Returned: success |
|
The time the cluster will be automatically deleted in RFC3339 text format. Returned: success |
|
The software version of the master endpoint and kubelets used in the cluster when it was first created. The version can be upgraded over time. Returned: success |
|
The number of nodes to create in this cluster. You must ensure that your Compute Engine resource quota 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 “nodePool” object, since this configuration (along with the “nodeConfig”) will be used to create a “NodePool” object with an auto-generated name. Do not use this and a nodePool at the same time. This field has been deprecated. Please use nodePool.initial_node_count instead. Returned: success |
|
Configuration for controlling how IPs are allocated in the cluster. Returned: success |
|
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 useIpAliases 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. Returned: success |
|
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 . Returned: success |
|
Whether a new subnetwork will be created automatically for the cluster. Returned: success |
|
The IP address range of the instance IPs in this cluster. This is applicable only if createSubnetwork 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. Returned: success |
|
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 useIpAliases 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. Returned: success |
|
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. Returned: success |
|
A custom subnetwork name to be used if createSubnetwork is true. If this field is empty, then an automatic name will be chosen for the new subnetwork. Returned: success |
|
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 useIpAliases 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. Returned: success |
|
Whether alias IPs will be used for pod IPs in the cluster. Returned: success |
|
The name of the context for the kubectl config file. Will default to the cluster name. Returned: success |
|
The path that the kubectl config file will be written to. The file will not be created if this path is unset. Any existing file at this path will be completely overwritten. This requires the PyYaml library. Returned: success |
|
The fingerprint of the set of labels for this cluster. Returned: success |
|
Configuration for the legacy ABAC authorization mode. Returned: success |
|
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. Returned: success |
|
The location where the cluster is deployed. Returned: success |
|
The list of Google Compute Engine zones in which the cluster’s nodes should be located. Returned: success |
|
The logging service the cluster should use to write logs. Currently available options: logging.googleapis.com - the Google Cloud Logging service. none - no logs will be exported from the cluster. if left as an empty string,logging.googleapis.com will be used. Returned: success |
|
The authentication information for accessing the master endpoint. Returned: success |
|
Base64-encoded public certificate used by clients to authenticate to the cluster endpoint. Returned: success |
|
Configuration for client certificate authentication on the cluster. For clusters before v1.12, if no configuration is specified, a client certificate is issued. Returned: success |
|
Issue a client certificate. Returned: success |
|
Base64-encoded private key used by clients to authenticate to the cluster endpoint. Returned: success |
|
Base64-encoded public certificate that is the root of trust for the cluster. Returned: success |
|
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 with a minimum of 16 characters. Returned: success |
|
The username to use for HTTP basic authentication to the master endpoint. Returned: success |
|
Configuration for controlling how IPs are allocated in the cluster. Returned: success |
|
Define up to 50 external networks that could access Kubernetes master through HTTPS. Returned: success |
|
Block specified in CIDR notation. Returned: success |
|
Optional field used to identify cidr blocks. Returned: success |
|
Whether or not master authorized networks is enabled. Returned: success |
|
The monitoring service the cluster should use to write metrics. Currently available options: monitoring.googleapis.com - the Google Cloud Monitoring service. none - no metrics will be exported from the cluster. if left as an empty string, monitoring.googleapis.com will be used. Returned: success |
|
The name of this cluster. The name must be unique within this project and location, and can be up to 40 characters. Must be Lowercase letters, numbers, and hyphens only. Must start with a letter. Must end with a number or a letter. Returned: success |
|
The name of the Google Compute Engine network to which the cluster is connected. If left unspecified, the default network will be used. Returned: success |
|
Network configurations . Returned: success |
|
Whether the cluster disables default in-node sNAT rules. In-node sNAT rules will be disabled when defaultSnatStatus is disabled. Returned: success |
|
Whether Intra-node visibility is enabled for this cluster. This makes same node pod to pod traffic visible for VPC network. Returned: success |
|
The relative name of the Google Compute Engine network to which the cluster is connected. Example: projects/my-project/global/networks/my-network . Returned: success |
|
The relative name of the Google Compute Engine subnetwork to which the cluster is connected. Example: projects/my-project/regions/us-central1/subnetworks/my-subnet . Returned: success |
|
Configuration options for the NetworkPolicy feature. Returned: success |
|
Whether network policy is enabled on the cluster. Returned: success |
|
The selected network policy provider. Returned: success |
|
Parameters used in creating the cluster’s nodes. For requests, this field should only be used in lieu of a “nodePool” object, since this configuration (along with the “initialNodeCount”) will be used to create a “NodePool” object with an auto-generated name. Do not use this and a nodePool at the same time. For responses, this field will be populated with the node configuration of the first node pool. If unspecified, the defaults are used. Returned: success |
|
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. Returned: success |
|
The number of accelerator cards exposed to an instance. Returned: success |
|
The accelerator type resource name. Returned: success |
|
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. Returned: success |
|
Type of the disk attached to each node (e.g. ‘pd-standard’ or ‘pd-ssd’) If unspecified, the default disk type is ‘pd-standard’ . Returned: success |
|
The image type to use for this node. Note that for a given image type, the latest version of it will be used. Returned: success |
|
The map of Kubernetes labels (key/value pairs) to be applied to each node. These will added in addition to any default label(s) that Kubernetes may apply to the node. In case of conflict in label keys, the applied set may differ depending on the Kubernetes version – it’s best to assume the behavior is undefined and conflicts should be avoided. For more information, including usage and the valid values, see: http://kubernetes.io/v1.1/docs/user-guide/labels.html An object containing a list of “key”: value pairs. Example: { “name”: “wrench”, “mass”: “1.3kg”, “count”: “3” }. Returned: success |
|
The number of local SSD disks to be attached to the node. The limit for this value is dependant upon the maximum number of disks available on a machine per zone. See: https://cloud.google.com/compute/docs/disks/local-ssd#local_ssd_limits for more information. Returned: success |
|
The name of a Google Compute Engine machine type (e.g. n1-standard-1). If unspecified, the default machine type is n1-standard-1. Returned: success |
|
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 four reserved keys: “instance-template”, “kube-env”, “startup-script”, and “user-data” 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. An object containing a list of “key”: value pairs. Example: { “name”: “wrench”, “mass”: “1.3kg”, “count”: “3” }. Returned: success |
|
Minimum CPU platform to be used by this instance. The instance may be scheduled on the specified or newer CPU platform. Returned: success |
|
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 Google Container Registry). If unspecified, no scopes are added, unless Cloud Logging or Cloud Monitoring are enabled, in which case their required scopes will be added. Returned: success |
|
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. Returned: success |
|
The Google Cloud Platform Service Account to be used by the node VMs. If no Service Account is specified, the “default” service account is used. Returned: success |
|
Shielded Instance options. Returned: success |
|
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. Returned: success |
|
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. Returned: success |
|
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. Returned: success |
|
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/ . Returned: success |
|
Effect for taint. Returned: success |
|
Key for taint. Returned: success |
|
Value for taint. Returned: success |
|
The size of the address space on each node for hosting containers. This is provisioned from within the container_ipv4_cidr range. Returned: success |
|
Node pools belonging to this cluster. Returned: success |
|
Name of the node pool. Returned: success |
|
Configuration for a private cluster. Returned: success |
|
Whether the master’s internal IP address is used as the cluster endpoint. Returned: success |
|
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. Returned: success |
|
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. Returned: success |
|
The internal IP address of this cluster’s master endpoint. Returned: success |
|
The external IP address of this cluster’s master endpoint. Returned: success |
|
ReleaseChannel indicates which release channel a cluster is subscribed to. Release channels are arranged in order of risk and frequency of updates. Returned: success |
|
Which release channel the cluster is subscribed to. Returned: success |
|
The resource labels for the cluster to use to annotate any related Google Compute Engine resources. Returned: success |
|
The IP address range of the Kubernetes services in this cluster, in CIDR notation (e.g. 1.2.3.4/29). Service addresses are typically put in the last /16 from the container CIDR. Returned: success |
|
Shielded Nodes configuration. Returned: success |
|
Whether Shielded Nodes features are enabled on all nodes in this cluster. Returned: success |
|
The current status of this cluster. Returned: success |
|
Additional information about the current status of this cluster, if available. Returned: success |
|
The name of the Google Compute Engine subnetwork to which the cluster is connected. Returned: success |
|
The IP address range of the Cloud TPUs in this cluster, in [CIDR](http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) notation (e.g. 1.2.3.4/29). Returned: success |
Authors
Google Inc. (@googlecloudplatform)