Class: Aws::EKS::Types::KubernetesNetworkConfigRequest

Inherits:

Struct

Object
Struct
Aws::EKS::Types::KubernetesNetworkConfigRequest

show all

Includes:: Structure

Defined in:: lib/aws-sdk-eks/types.rb

Overview

The Kubernetes network configuration for the cluster.

Constant Summary collapse

SENSITIVE =

[]

Instance Attribute Summary collapse

#ip_family ⇒ String

Specify which IP family is used to assign Kubernetes pod and service IP addresses.
#service_ipv_4_cidr ⇒ String

Don’t specify a value if you select ‘ipv6` for ipFamily.

Instance Attribute Details

#ip_family ⇒ `String`

Specify which IP family is used to assign Kubernetes pod and service IP addresses. If you don’t specify a value, ‘ipv4` is used by default. You can only specify an IP family when you create a cluster and can’t change this value once the cluster is created. If you specify ‘ipv6`, the VPC and subnets that you specify for cluster creation must have both `IPv4` and `IPv6` CIDR blocks assigned to them. You can’t specify ‘ipv6` for clusters in China Regions.

You can only specify ‘ipv6` for `1.21` and later clusters that use version `1.10.1` or later of the Amazon VPC CNI add-on. If you specify `ipv6`, then ensure that your VPC meets the requirements listed in the considerations listed in [Assigning IPv6 addresses to pods and services] in the Amazon EKS User Guide. Kubernetes assigns services `IPv6` addresses from the unique local address range `(fc00::/7)`. You can’t specify a custom ‘IPv6` CIDR block. Pod addresses are assigned from the subnet’s ‘IPv6` CIDR.

[1]: docs.aws.amazon.com/eks/latest/userguide/cni-ipv6.html

Returns:

(String)

# File 'lib/aws-sdk-eks/types.rb', line 3565

class KubernetesNetworkConfigRequest < Struct.new(
  :service_ipv_4_cidr,
  :ip_family)
  SENSITIVE = []
  include Aws::Structure
end

#service_ipv_4_cidr ⇒ `String`

Don’t specify a value if you select ‘ipv6` for ipFamily. The CIDR block to assign Kubernetes service IP addresses from. If you don’t specify a block, Kubernetes assigns addresses from either the ‘10.100.0.0/16` or `172.20.0.0/16` CIDR blocks. We recommend that you specify a block that does not overlap with resources in other networks that are peered or connected to your VPC. The block must meet the following requirements:

Within one of the following private IP address blocks: ‘10.0.0.0/8`, `172.16.0.0/12`, or `192.168.0.0/16`.
Doesn’t overlap with any CIDR block assigned to the VPC that you selected for VPC.
Between ‘/24` and `/12`.

You can only specify a custom CIDR block when you create a cluster. You can’t change this value after the cluster is created.