#[non_exhaustive]pub struct KubernetesNetworkConfigRequest {
pub service_ipv4_cidr: Option<String>,
pub ip_family: Option<IpFamily>,
pub elastic_load_balancing: Option<ElasticLoadBalancing>,
}
Expand description
The Kubernetes network configuration for the cluster.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.service_ipv4_cidr: Option<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
, or192.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.
ip_family: Option<IpFamily>
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.
elastic_load_balancing: Option<ElasticLoadBalancing>
Request to enable or disable the load balancing capability on your EKS Auto Mode cluster. For more information, see EKS Auto Mode load balancing capability in the Amazon EKS User Guide.
Implementations§
Source§impl KubernetesNetworkConfigRequest
impl KubernetesNetworkConfigRequest
Sourcepub fn service_ipv4_cidr(&self) -> Option<&str>
pub fn service_ipv4_cidr(&self) -> Option<&str>
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
, or192.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.
Sourcepub fn ip_family(&self) -> Option<&IpFamily>
pub fn ip_family(&self) -> Option<&IpFamily>
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.
Sourcepub fn elastic_load_balancing(&self) -> Option<&ElasticLoadBalancing>
pub fn elastic_load_balancing(&self) -> Option<&ElasticLoadBalancing>
Request to enable or disable the load balancing capability on your EKS Auto Mode cluster. For more information, see EKS Auto Mode load balancing capability in the Amazon EKS User Guide.
Source§impl KubernetesNetworkConfigRequest
impl KubernetesNetworkConfigRequest
Sourcepub fn builder() -> KubernetesNetworkConfigRequestBuilder
pub fn builder() -> KubernetesNetworkConfigRequestBuilder
Creates a new builder-style object to manufacture KubernetesNetworkConfigRequest
.
Trait Implementations§
Source§impl Clone for KubernetesNetworkConfigRequest
impl Clone for KubernetesNetworkConfigRequest
Source§fn clone(&self) -> KubernetesNetworkConfigRequest
fn clone(&self) -> KubernetesNetworkConfigRequest
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl PartialEq for KubernetesNetworkConfigRequest
impl PartialEq for KubernetesNetworkConfigRequest
Source§fn eq(&self, other: &KubernetesNetworkConfigRequest) -> bool
fn eq(&self, other: &KubernetesNetworkConfigRequest) -> bool
self
and other
values to be equal, and is used by ==
.impl StructuralPartialEq for KubernetesNetworkConfigRequest
Auto Trait Implementations§
impl Freeze for KubernetesNetworkConfigRequest
impl RefUnwindSafe for KubernetesNetworkConfigRequest
impl Send for KubernetesNetworkConfigRequest
impl Sync for KubernetesNetworkConfigRequest
impl Unpin for KubernetesNetworkConfigRequest
impl UnwindSafe for KubernetesNetworkConfigRequest
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left
is true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left(&self)
returns true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the foreground set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red()
and
green()
, which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg()
:
use yansi::{Paint, Color};
painted.fg(Color::White);
Set foreground color to white using white()
.
use yansi::Paint;
painted.white();
Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the background set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red()
and
on_green()
, which have the same functionality but
are pithier.
§Example
Set background color to red using fg()
:
use yansi::{Paint, Color};
painted.bg(Color::Red);
Set background color to red using on_red()
.
use yansi::Paint;
painted.on_red();
Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute
value
.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold()
and
underline()
, which have the same functionality
but are pithier.
§Example
Make text bold using attr()
:
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);
Make text bold using using bold()
.
use yansi::Paint;
painted.bold();
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi
Quirk
value
.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask()
and
wrap()
, which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk()
:
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);
Enable wrapping using wrap()
.
use yansi::Paint;
painted.wrap();
Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition
value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted
only when both stdout
and stderr
are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);