#[non_exhaustive]pub struct CreateNodegroupInput {Show 19 fields
pub cluster_name: Option<String>,
pub nodegroup_name: Option<String>,
pub scaling_config: Option<NodegroupScalingConfig>,
pub disk_size: Option<i32>,
pub subnets: Option<Vec<String>>,
pub instance_types: Option<Vec<String>>,
pub ami_type: Option<AmiTypes>,
pub remote_access: Option<RemoteAccessConfig>,
pub node_role: Option<String>,
pub labels: Option<HashMap<String, String>>,
pub taints: Option<Vec<Taint>>,
pub tags: Option<HashMap<String, String>>,
pub client_request_token: Option<String>,
pub launch_template: Option<LaunchTemplateSpecification>,
pub update_config: Option<NodegroupUpdateConfig>,
pub node_repair_config: Option<NodeRepairConfig>,
pub capacity_type: Option<CapacityTypes>,
pub version: Option<String>,
pub release_version: Option<String>,
}
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.cluster_name: Option<String>
The name of your cluster.
nodegroup_name: Option<String>
The unique name to give your node group.
scaling_config: Option<NodegroupScalingConfig>
The scaling configuration details for the Auto Scaling group that is created for your node group.
disk_size: Option<i32>
The root device disk size (in GiB) for your node group instances. The default disk size is 20 GiB for Linux and Bottlerocket. The default disk size is 50 GiB for Windows. If you specify launchTemplate
, then don't specify diskSize
, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Customizing managed nodes with launch templates in the Amazon EKS User Guide.
subnets: Option<Vec<String>>
The subnets to use for the Auto Scaling group that is created for your node group. If you specify launchTemplate
, then don't specify SubnetId
in your launch template, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Customizing managed nodes with launch templates in the Amazon EKS User Guide.
instance_types: Option<Vec<String>>
Specify the instance types for a node group. If you specify a GPU instance type, make sure to also specify an applicable GPU AMI type with the amiType
parameter. If you specify launchTemplate
, then you can specify zero or one instance type in your launch template or you can specify 0-20 instance types for instanceTypes
. If however, you specify an instance type in your launch template and specify any instanceTypes
, the node group deployment will fail. If you don't specify an instance type in a launch template or for instanceTypes
, then t3.medium
is used, by default. If you specify Spot
for capacityType
, then we recommend specifying multiple values for instanceTypes
. For more information, see Managed node group capacity types and Customizing managed nodes with launch templates in the Amazon EKS User Guide.
ami_type: Option<AmiTypes>
The AMI type for your node group. If you specify launchTemplate
, and your launch template uses a custom AMI, then don't specify amiType
, or the node group deployment will fail. If your launch template uses a Windows custom AMI, then add eks:kube-proxy-windows
to your Windows nodes rolearn
in the aws-auth
ConfigMap
. For more information about using launch templates with Amazon EKS, see Customizing managed nodes with launch templates in the Amazon EKS User Guide.
remote_access: Option<RemoteAccessConfig>
The remote access configuration to use with your node group. For Linux, the protocol is SSH. For Windows, the protocol is RDP. If you specify launchTemplate
, then don't specify remoteAccess
, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Customizing managed nodes with launch templates in the Amazon EKS User Guide.
node_role: Option<String>
The Amazon Resource Name (ARN) of the IAM role to associate with your node group. The Amazon EKS worker node kubelet
daemon makes calls to Amazon Web Services APIs on your behalf. Nodes receive permissions for these API calls through an IAM instance profile and associated policies. Before you can launch nodes and register them into a cluster, you must create an IAM role for those nodes to use when they are launched. For more information, see Amazon EKS node IAM role in the Amazon EKS User Guide . If you specify launchTemplate
, then don't specify IamInstanceProfile
in your launch template, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Customizing managed nodes with launch templates in the Amazon EKS User Guide.
labels: Option<HashMap<String, String>>
The Kubernetes labels
to apply to the nodes in the node group when they are created.
taints: Option<Vec<Taint>>
The Kubernetes taints to be applied to the nodes in the node group. For more information, see Node taints on managed node groups.
Metadata that assists with categorization and organization. Each tag consists of a key and an optional value. You define both. Tags don't propagate to any other cluster or Amazon Web Services resources.
client_request_token: Option<String>
A unique, case-sensitive identifier that you provide to ensure the idempotency of the request.
launch_template: Option<LaunchTemplateSpecification>
An object representing a node group's launch template specification. When using this object, don't directly specify instanceTypes
, diskSize
, or remoteAccess
. You cannot later specify a different launch template ID or name than what was used to create the node group.
Make sure that the launch template meets the requirements in launchTemplateSpecification
. Also refer to Customizing managed nodes with launch templates in the Amazon EKS User Guide.
update_config: Option<NodegroupUpdateConfig>
The node group update configuration.
node_repair_config: Option<NodeRepairConfig>
The node auto repair configuration for the node group.
capacity_type: Option<CapacityTypes>
The capacity type for your node group.
version: Option<String>
The Kubernetes version to use for your managed nodes. By default, the Kubernetes version of the cluster is used, and this is the only accepted specified value. If you specify launchTemplate
, and your launch template uses a custom AMI, then don't specify version
, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Customizing managed nodes with launch templates in the Amazon EKS User Guide.
release_version: Option<String>
The AMI version of the Amazon EKS optimized AMI to use with your node group. By default, the latest available AMI version for the node group's current Kubernetes version is used. For information about Linux versions, see Amazon EKS optimized Amazon Linux AMI versions in the Amazon EKS User Guide. Amazon EKS managed node groups support the November 2022 and later releases of the Windows AMIs. For information about Windows versions, see Amazon EKS optimized Windows AMI versions in the Amazon EKS User Guide.
If you specify launchTemplate
, and your launch template uses a custom AMI, then don't specify releaseVersion
, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Customizing managed nodes with launch templates in the Amazon EKS User Guide.
Implementations§
Source§impl CreateNodegroupInput
impl CreateNodegroupInput
Sourcepub fn cluster_name(&self) -> Option<&str>
pub fn cluster_name(&self) -> Option<&str>
The name of your cluster.
Sourcepub fn nodegroup_name(&self) -> Option<&str>
pub fn nodegroup_name(&self) -> Option<&str>
The unique name to give your node group.
Sourcepub fn scaling_config(&self) -> Option<&NodegroupScalingConfig>
pub fn scaling_config(&self) -> Option<&NodegroupScalingConfig>
The scaling configuration details for the Auto Scaling group that is created for your node group.
Sourcepub fn disk_size(&self) -> Option<i32>
pub fn disk_size(&self) -> Option<i32>
The root device disk size (in GiB) for your node group instances. The default disk size is 20 GiB for Linux and Bottlerocket. The default disk size is 50 GiB for Windows. If you specify launchTemplate
, then don't specify diskSize
, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Customizing managed nodes with launch templates in the Amazon EKS User Guide.
Sourcepub fn subnets(&self) -> &[String]
pub fn subnets(&self) -> &[String]
The subnets to use for the Auto Scaling group that is created for your node group. If you specify launchTemplate
, then don't specify SubnetId
in your launch template, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Customizing managed nodes with launch templates in the Amazon EKS User Guide.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .subnets.is_none()
.
Sourcepub fn instance_types(&self) -> &[String]
pub fn instance_types(&self) -> &[String]
Specify the instance types for a node group. If you specify a GPU instance type, make sure to also specify an applicable GPU AMI type with the amiType
parameter. If you specify launchTemplate
, then you can specify zero or one instance type in your launch template or you can specify 0-20 instance types for instanceTypes
. If however, you specify an instance type in your launch template and specify any instanceTypes
, the node group deployment will fail. If you don't specify an instance type in a launch template or for instanceTypes
, then t3.medium
is used, by default. If you specify Spot
for capacityType
, then we recommend specifying multiple values for instanceTypes
. For more information, see Managed node group capacity types and Customizing managed nodes with launch templates in the Amazon EKS User Guide.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .instance_types.is_none()
.
Sourcepub fn ami_type(&self) -> Option<&AmiTypes>
pub fn ami_type(&self) -> Option<&AmiTypes>
The AMI type for your node group. If you specify launchTemplate
, and your launch template uses a custom AMI, then don't specify amiType
, or the node group deployment will fail. If your launch template uses a Windows custom AMI, then add eks:kube-proxy-windows
to your Windows nodes rolearn
in the aws-auth
ConfigMap
. For more information about using launch templates with Amazon EKS, see Customizing managed nodes with launch templates in the Amazon EKS User Guide.
Sourcepub fn remote_access(&self) -> Option<&RemoteAccessConfig>
pub fn remote_access(&self) -> Option<&RemoteAccessConfig>
The remote access configuration to use with your node group. For Linux, the protocol is SSH. For Windows, the protocol is RDP. If you specify launchTemplate
, then don't specify remoteAccess
, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Customizing managed nodes with launch templates in the Amazon EKS User Guide.
Sourcepub fn node_role(&self) -> Option<&str>
pub fn node_role(&self) -> Option<&str>
The Amazon Resource Name (ARN) of the IAM role to associate with your node group. The Amazon EKS worker node kubelet
daemon makes calls to Amazon Web Services APIs on your behalf. Nodes receive permissions for these API calls through an IAM instance profile and associated policies. Before you can launch nodes and register them into a cluster, you must create an IAM role for those nodes to use when they are launched. For more information, see Amazon EKS node IAM role in the Amazon EKS User Guide . If you specify launchTemplate
, then don't specify IamInstanceProfile
in your launch template, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Customizing managed nodes with launch templates in the Amazon EKS User Guide.
Sourcepub fn labels(&self) -> Option<&HashMap<String, String>>
pub fn labels(&self) -> Option<&HashMap<String, String>>
The Kubernetes labels
to apply to the nodes in the node group when they are created.
Sourcepub fn taints(&self) -> &[Taint]
pub fn taints(&self) -> &[Taint]
The Kubernetes taints to be applied to the nodes in the node group. For more information, see Node taints on managed node groups.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .taints.is_none()
.
Metadata that assists with categorization and organization. Each tag consists of a key and an optional value. You define both. Tags don't propagate to any other cluster or Amazon Web Services resources.
Sourcepub fn client_request_token(&self) -> Option<&str>
pub fn client_request_token(&self) -> Option<&str>
A unique, case-sensitive identifier that you provide to ensure the idempotency of the request.
Sourcepub fn launch_template(&self) -> Option<&LaunchTemplateSpecification>
pub fn launch_template(&self) -> Option<&LaunchTemplateSpecification>
An object representing a node group's launch template specification. When using this object, don't directly specify instanceTypes
, diskSize
, or remoteAccess
. You cannot later specify a different launch template ID or name than what was used to create the node group.
Make sure that the launch template meets the requirements in launchTemplateSpecification
. Also refer to Customizing managed nodes with launch templates in the Amazon EKS User Guide.
Sourcepub fn update_config(&self) -> Option<&NodegroupUpdateConfig>
pub fn update_config(&self) -> Option<&NodegroupUpdateConfig>
The node group update configuration.
Sourcepub fn node_repair_config(&self) -> Option<&NodeRepairConfig>
pub fn node_repair_config(&self) -> Option<&NodeRepairConfig>
The node auto repair configuration for the node group.
Sourcepub fn capacity_type(&self) -> Option<&CapacityTypes>
pub fn capacity_type(&self) -> Option<&CapacityTypes>
The capacity type for your node group.
Sourcepub fn version(&self) -> Option<&str>
pub fn version(&self) -> Option<&str>
The Kubernetes version to use for your managed nodes. By default, the Kubernetes version of the cluster is used, and this is the only accepted specified value. If you specify launchTemplate
, and your launch template uses a custom AMI, then don't specify version
, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Customizing managed nodes with launch templates in the Amazon EKS User Guide.
Sourcepub fn release_version(&self) -> Option<&str>
pub fn release_version(&self) -> Option<&str>
The AMI version of the Amazon EKS optimized AMI to use with your node group. By default, the latest available AMI version for the node group's current Kubernetes version is used. For information about Linux versions, see Amazon EKS optimized Amazon Linux AMI versions in the Amazon EKS User Guide. Amazon EKS managed node groups support the November 2022 and later releases of the Windows AMIs. For information about Windows versions, see Amazon EKS optimized Windows AMI versions in the Amazon EKS User Guide.
If you specify launchTemplate
, and your launch template uses a custom AMI, then don't specify releaseVersion
, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see Customizing managed nodes with launch templates in the Amazon EKS User Guide.
Source§impl CreateNodegroupInput
impl CreateNodegroupInput
Sourcepub fn builder() -> CreateNodegroupInputBuilder
pub fn builder() -> CreateNodegroupInputBuilder
Creates a new builder-style object to manufacture CreateNodegroupInput
.
Trait Implementations§
Source§impl Clone for CreateNodegroupInput
impl Clone for CreateNodegroupInput
Source§fn clone(&self) -> CreateNodegroupInput
fn clone(&self) -> CreateNodegroupInput
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for CreateNodegroupInput
impl Debug for CreateNodegroupInput
Source§impl PartialEq for CreateNodegroupInput
impl PartialEq for CreateNodegroupInput
impl StructuralPartialEq for CreateNodegroupInput
Auto Trait Implementations§
impl Freeze for CreateNodegroupInput
impl RefUnwindSafe for CreateNodegroupInput
impl Send for CreateNodegroupInput
impl Sync for CreateNodegroupInput
impl Unpin for CreateNodegroupInput
impl UnwindSafe for CreateNodegroupInput
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);