ClusterIpAllocationPolicyArgs

data class ClusterIpAllocationPolicyArgs(val clusterIpv4CidrBlock: Output<String>? = null, val clusterSecondaryRangeName: Output<String>? = null, val servicesIpv4CidrBlock: Output<String>? = null, val servicesSecondaryRangeName: Output<String>? = null) : ConvertibleToJava<ClusterIpAllocationPolicyArgs>

Constructors

Link copied to clipboard
fun ClusterIpAllocationPolicyArgs(clusterIpv4CidrBlock: Output<String>? = null, clusterSecondaryRangeName: Output<String>? = null, servicesIpv4CidrBlock: Output<String>? = null, servicesSecondaryRangeName: Output<String>? = null)

Functions

Link copied to clipboard
open override fun toJava(): ClusterIpAllocationPolicyArgs

Properties

Link copied to clipboard
val clusterIpv4CidrBlock: Output<String>? = null

The IP address range for the cluster pod IPs. 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 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.

Link copied to clipboard
val clusterSecondaryRangeName: Output<String>? = null

The name of the existing secondary range in the cluster's subnetwork to use for pod IP addresses. Alternatively, cluster_ipv4_cidr_block can be used to automatically create a GKE-managed one.

Link copied to clipboard
val servicesIpv4CidrBlock: Output<String>? = null

The IP address range of the services IPs in this cluster. 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 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.

Link copied to clipboard
val servicesSecondaryRangeName: Output<String>? = null

The name of the existing secondary range in the cluster's subnetwork to use for service ClusterIPs. Alternatively, services_ipv4_cidr_block can be used to automatically create a GKE-managed one.