Copyright | (c) 2013-2023 Brendan Hay |
---|---|
License | Mozilla Public License, v. 2.0. |
Maintainer | Brendan Hay |
Stability | auto-generated |
Portability | non-portable (GHC extensions) |
Safe Haskell | Safe-Inferred |
Language | Haskell2010 |
Synopsis
- data KubernetesNetworkConfigResponse = KubernetesNetworkConfigResponse' {}
- newKubernetesNetworkConfigResponse :: KubernetesNetworkConfigResponse
- kubernetesNetworkConfigResponse_ipFamily :: Lens' KubernetesNetworkConfigResponse (Maybe IpFamily)
- kubernetesNetworkConfigResponse_serviceIpv4Cidr :: Lens' KubernetesNetworkConfigResponse (Maybe Text)
- kubernetesNetworkConfigResponse_serviceIpv6Cidr :: Lens' KubernetesNetworkConfigResponse (Maybe Text)
Documentation
data KubernetesNetworkConfigResponse Source #
The Kubernetes network configuration for the cluster. The response contains a value for serviceIpv6Cidr or serviceIpv4Cidr, but not both.
See: newKubernetesNetworkConfigResponse
smart constructor.
KubernetesNetworkConfigResponse' | |
|
Instances
newKubernetesNetworkConfigResponse :: KubernetesNetworkConfigResponse Source #
Create a value of KubernetesNetworkConfigResponse
with all optional fields omitted.
Use generic-lens or optics to modify other optional fields.
The following record fields are available, with the corresponding lenses provided for backwards compatibility:
$sel:ipFamily:KubernetesNetworkConfigResponse'
, kubernetesNetworkConfigResponse_ipFamily
- The IP family used to assign Kubernetes pod and service IP addresses.
The IP family is always ipv4
, unless you have a 1.21
or later
cluster running version 1.10.1 or later of the Amazon VPC CNI add-on and
specified ipv6
when you created the cluster.
$sel:serviceIpv4Cidr:KubernetesNetworkConfigResponse'
, kubernetesNetworkConfigResponse_serviceIpv4Cidr
- The CIDR block that Kubernetes pod and service IP addresses are assigned
from. Kubernetes assigns addresses from an IPv4 CIDR block assigned to a
subnet that the node is in. If you didn't specify a CIDR block when you
created the cluster, then Kubernetes assigns addresses from either the
10.100.0.0/16
or 172.20.0.0/16
CIDR blocks. If this was specified,
then it was specified when the cluster was created and it can't be
changed.
$sel:serviceIpv6Cidr:KubernetesNetworkConfigResponse'
, kubernetesNetworkConfigResponse_serviceIpv6Cidr
- The CIDR block that Kubernetes pod and service IP addresses are assigned
from if you created a 1.21 or later cluster with version 1.10.1 or later
of the Amazon VPC CNI add-on and specified ipv6
for ipFamily when
you created the cluster. Kubernetes assigns service addresses from the
unique local address range (fc00::/7
) because you can't specify a
custom IPv6 CIDR block when you create the cluster.
kubernetesNetworkConfigResponse_ipFamily :: Lens' KubernetesNetworkConfigResponse (Maybe IpFamily) Source #
The IP family used to assign Kubernetes pod and service IP addresses.
The IP family is always ipv4
, unless you have a 1.21
or later
cluster running version 1.10.1 or later of the Amazon VPC CNI add-on and
specified ipv6
when you created the cluster.
kubernetesNetworkConfigResponse_serviceIpv4Cidr :: Lens' KubernetesNetworkConfigResponse (Maybe Text) Source #
The CIDR block that Kubernetes pod and service IP addresses are assigned
from. Kubernetes assigns addresses from an IPv4 CIDR block assigned to a
subnet that the node is in. If you didn't specify a CIDR block when you
created the cluster, then Kubernetes assigns addresses from either the
10.100.0.0/16
or 172.20.0.0/16
CIDR blocks. If this was specified,
then it was specified when the cluster was created and it can't be
changed.
kubernetesNetworkConfigResponse_serviceIpv6Cidr :: Lens' KubernetesNetworkConfigResponse (Maybe Text) Source #
The CIDR block that Kubernetes pod and service IP addresses are assigned
from if you created a 1.21 or later cluster with version 1.10.1 or later
of the Amazon VPC CNI add-on and specified ipv6
for ipFamily when
you created the cluster. Kubernetes assigns service addresses from the
unique local address range (fc00::/7
) because you can't specify a
custom IPv6 CIDR block when you create the cluster.