|
28 | 28 | "AMITypes": { |
29 | 29 | "base": null, |
30 | 30 | "refs": { |
31 | | - "CreateNodegroupRequest$amiType": "<p>The AMI type for your node group. GPU instance types should use the <code>AL2_x86_64_GPU</code> AMI type, which uses the Amazon EKS-optimized Linux AMI with GPU support. Non-GPU instances should use the <code>AL2_x86_64</code> AMI type, which uses the Amazon EKS-optimized Linux AMI. If you specify <code>launchTemplate</code>, and your launch template uses a custom AMI, then don't specify <code>amiType</code>, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html\">Launch template support</a> in the Amazon EKS User Guide.</p>", |
| 31 | + "CreateNodegroupRequest$amiType": "<p>The AMI type for your node group. GPU instance types should use the <code>AL2_x86_64_GPU</code> AMI type. Non-GPU instances should use the <code>AL2_x86_64</code> AMI type. Arm instances should use the <code>AL2_ARM_64</code> AMI type. All types use the Amazon EKS-optimized Amazon Linux 2 AMI. If you specify <code>launchTemplate</code>, and your launch template uses a custom AMI, then don't specify <code>amiType</code>, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html\">Launch template support</a> in the Amazon EKS User Guide.</p>", |
32 | 32 | "Nodegroup$amiType": "<p>If the node group was deployed using a launch template with a custom AMI, then this is <code>CUSTOM</code>. For node groups that weren't deployed using a launch template, this is the AMI type that was specified in the node group configuration.</p>" |
33 | 33 | } |
34 | 34 | }, |
|
69 | 69 | "base": null, |
70 | 70 | "refs": { |
71 | 71 | "CreateNodegroupRequest$diskSize": "<p>The root device disk size (in GiB) for your node group instances. The default disk size is 20 GiB. If you specify <code>launchTemplate</code>, then don't specify <code>diskSize</code>, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html\">Launch template support</a> in the Amazon EKS User Guide.</p>", |
72 | | - "Nodegroup$diskSize": "<p>If the node group wasn't deployed with a launch template, then this is the disk size in the node group configuration. If the node group was deployed with a launch template, then <code>diskSize</code> is <code>null</code>.</p>" |
| 72 | + "Nodegroup$diskSize": "<p>If the node group wasn't deployed with a launch template, then this is the disk size in the node group configuration. If the node group was deployed with a launch template, then this is <code>null</code>.</p>" |
73 | 73 | } |
74 | 74 | }, |
75 | 75 | "Capacity": { |
|
309 | 309 | "NodegroupHealth$issues": "<p>Any issues that are associated with the node group. </p>" |
310 | 310 | } |
311 | 311 | }, |
| 312 | + "KubernetesNetworkConfigRequest": { |
| 313 | + "base": "<p>The Kubernetes network configuration for the cluster.</p>", |
| 314 | + "refs": { |
| 315 | + "CreateClusterRequest$kubernetesNetworkConfig": "<p>The Kubernetes network configuration for the cluster.</p>" |
| 316 | + } |
| 317 | + }, |
| 318 | + "KubernetesNetworkConfigResponse": { |
| 319 | + "base": "<p>The Kubernetes network configuration for the cluster.</p>", |
| 320 | + "refs": { |
| 321 | + "Cluster$kubernetesNetworkConfig": "<p>Network configuration settings for your cluster.</p>" |
| 322 | + } |
| 323 | + }, |
312 | 324 | "LaunchTemplateSpecification": { |
313 | 325 | "base": "<p>An object representing a node group launch template specification. The launch template cannot include <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateNetworkInterface.html\"> <code>SubnetId</code> </a>, <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_IamInstanceProfile.html\"> <code>IamInstanceProfile</code> </a>, <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RequestSpotInstances.html\"> <code>RequestSpotInstances</code> </a>, <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_HibernationOptionsRequest.html\"> <code>HibernationOptions</code> </a>, or <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_TerminateInstances.html\"> <code>TerminateInstances</code> </a>, or the node group deployment or update will fail. For more information about launch templates, see <a href=\"https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateLaunchTemplate.html\"> <code>CreateLaunchTemplate</code> </a> in the Amazon EC2 API Reference. For more information about using launch templates with Amazon EKS, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html\">Launch template support</a> in the Amazon EKS User Guide.</p> <p>Specify either <code>name</code> or <code>id</code>, but not both.</p>", |
314 | 326 | "refs": { |
315 | | - "CreateNodegroupRequest$launchTemplate": "<p>An object representing a node group's launch template specification. If specified, then do not specify <code>instanceTypes</code>, <code>diskSize</code>, or <code>remoteAccess</code>. If specified, make sure that the launch template meets the requirements in <code>launchTemplateSpecification</code>.</p>", |
| 327 | + "CreateNodegroupRequest$launchTemplate": "<p>An object representing a node group's launch template specification. If specified, then do not specify <code>instanceTypes</code>, <code>diskSize</code>, or <code>remoteAccess</code> and make sure that the launch template meets the requirements in <code>launchTemplateSpecification</code>.</p>", |
316 | 328 | "Nodegroup$launchTemplate": "<p>If a launch template was used to create the node group, then this is the launch template that was used.</p>", |
317 | 329 | "UpdateNodegroupVersionRequest$launchTemplate": "<p>An object representing a node group's launch template specification. You can only update a node group using a launch template if the node group was originally deployed with a launch template.</p>" |
318 | 330 | } |
|
478 | 490 | "base": "<p>An object representing the remote access configuration for the managed node group.</p>", |
479 | 491 | "refs": { |
480 | 492 | "CreateNodegroupRequest$remoteAccess": "<p>The remote access (SSH) configuration to use with your node group. If you specify <code>launchTemplate</code>, then don't specify <code>remoteAccess</code>, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html\">Launch template support</a> in the Amazon EKS User Guide.</p>", |
481 | | - "Nodegroup$remoteAccess": "<p>If the node group wasn't deployed with a launch template, then this is the remote access configuration that is associated with the node group. If the node group was deployed with a launch template, then <code>remoteAccess</code> is <code>null</code>.</p>" |
| 493 | + "Nodegroup$remoteAccess": "<p>If the node group wasn't deployed with a launch template, then this is the remote access configuration that is associated with the node group. If the node group was deployed with a launch template, then this is <code>null</code>.</p>" |
482 | 494 | } |
483 | 495 | }, |
484 | 496 | "ResourceInUseException": { |
|
564 | 576 | "InvalidRequestException$nodegroupName": "<p>The Amazon EKS managed node group associated with the exception.</p>", |
565 | 577 | "InvalidRequestException$message": null, |
566 | 578 | "Issue$message": "<p>The error message associated with the issue.</p>", |
| 579 | + "KubernetesNetworkConfigRequest$serviceIpv4Cidr": "<p>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:</p> <ul> <li> <p>Within one of the following private IP address blocks: 10.0.0.0/8, 172.16.0.0.0/12, or 192.168.0.0/16.</p> </li> <li> <p>Doesn't overlap with any CIDR block assigned to the VPC that you selected for VPC.</p> </li> <li> <p>Between /24 and /12.</p> </li> </ul> <important> <p>You can only specify a custom CIDR block when you create a cluster and can't change this value once the cluster is created.</p> </important>", |
| 580 | + "KubernetesNetworkConfigResponse$serviceIpv4Cidr": "<p>The CIDR block that Kubernetes service IP addresses are assigned from. If you didn't specify a CIDR block, 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 cannot be changed.</p>", |
567 | 581 | "LaunchTemplateSpecification$name": "<p>The name of the launch template.</p>", |
568 | 582 | "LaunchTemplateSpecification$version": "<p>The version of the launch template to use. If no version is specified, then the template's default version is used.</p>", |
569 | 583 | "LaunchTemplateSpecification$id": "<p>The ID of the launch template.</p>", |
|
645 | 659 | "ListFargateProfilesResponse$fargateProfileNames": "<p>A list of all of the Fargate profiles associated with the specified cluster.</p>", |
646 | 660 | "ListNodegroupsResponse$nodegroups": "<p>A list of all of the node groups associated with the specified cluster.</p>", |
647 | 661 | "ListUpdatesResponse$updateIds": "<p>A list of all the updates for the specified cluster and Region.</p>", |
648 | | - "Nodegroup$instanceTypes": "<p>If the node group wasn't deployed with a launch template, then this is the instance type that is associated with the node group. If the node group was deployed with a launch template, then <code>instanceTypes</code> is <code>null</code>.</p>", |
| 662 | + "Nodegroup$instanceTypes": "<p>If the node group wasn't deployed with a launch template, then this is the instance type that is associated with the node group. If the node group was deployed with a launch template, then this is <code>null</code>.</p>", |
649 | 663 | "Nodegroup$subnets": "<p>The subnets that were specified for the Auto Scaling group that is associated with your node group.</p>", |
650 | 664 | "RemoteAccessConfig$sourceSecurityGroups": "<p>The security groups that are allowed SSH access (port 22) to the worker nodes. If you specify an Amazon EC2 SSH key but do not specify a source security group when you create a managed node group, then port 22 on the worker nodes is opened to the internet (0.0.0.0/0). For more information, see <a href=\"https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html\">Security Groups for Your VPC</a> in the <i>Amazon Virtual Private Cloud User Guide</i>.</p>", |
651 | 665 | "UnsupportedAvailabilityZoneException$validZones": "<p>The supported Availability Zones for your account. Choose subnets in these Availability Zones for your cluster.</p>", |
|
0 commit comments