@aws-sdk/client-eks 3.41.0 → 3.46.0

package/dist-types/EKS.d.ts

@@ -35,16 +35,16 @@ import { UpdateNodegroupConfigCommandInput, UpdateNodegroupConfigCommandOutput }
 import { UpdateNodegroupVersionCommandInput, UpdateNodegroupVersionCommandOutput } from "./commands/UpdateNodegroupVersionCommand";
 import { EKSClient } from "./EKSClient";
 /**
- * <p>Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that makes it easy for you to run Kubernetes on
- *             Amazon Web Services without needing to stand up or maintain your own Kubernetes control plane.
- *             Kubernetes is an open-source system for automating the deployment, scaling, and
- *             management of containerized applications. </p>
- *         <p>Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so you can use
- *             all the existing plugins and tooling from the Kubernetes community. Applications running
- *             on Amazon EKS are fully compatible with applications running on any standard Kubernetes
- *             environment, whether running in on-premises data centers or public clouds. This means
- *             that you can easily migrate any standard Kubernetes application to Amazon EKS without any
- *             code modification required.</p>
+ * <p>Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that makes it easy
+ *             for you to run Kubernetes on Amazon Web Services without needing to stand up or maintain
+ *             your own Kubernetes control plane. Kubernetes is an open-source system for automating
+ *             the deployment, scaling, and management of containerized applications. </p>
+ *         <p>Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so
+ *             you can use all the existing plugins and tooling from the Kubernetes community.
+ *             Applications running on Amazon EKS are fully compatible with applications
+ *             running on any standard Kubernetes environment, whether running in on-premises data
+ *             centers or public clouds. This means that you can easily migrate any standard Kubernetes
+ *             application to Amazon EKS without any code modification required.</p>
  */
 export declare class EKS extends EKSClient {
     /**
@@ -71,11 +71,12 @@ export declare class EKS extends EKSClient {
     associateIdentityProviderConfig(args: AssociateIdentityProviderConfigCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: AssociateIdentityProviderConfigCommandOutput) => void): void;
     /**
      * <p>Creates an Amazon EKS add-on.</p>
-     *         <p>Amazon EKS add-ons help to automate the provisioning and lifecycle management of common
-     *             operational software for Amazon EKS clusters. Amazon EKS add-ons can only be used with Amazon EKS
-     *             clusters running version 1.18 with platform version <code>eks.3</code> or later because
+     *         <p>Amazon EKS add-ons help to automate the provisioning and lifecycle management
+     *             of common operational software for Amazon EKS clusters. Amazon EKS
+     *             add-ons require clusters running version 1.18 or later because Amazon EKS
      *             add-ons rely on the Server-side Apply Kubernetes feature, which is only available in
-     *             Kubernetes 1.18 and later.</p>
+     *             Kubernetes 1.18 and later. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-add-ons.html">Amazon EKS add-ons</a> in
+     *             the <i>Amazon EKS User Guide</i>.</p>
      */
     createAddon(args: CreateAddonCommandInput, options?: __HttpHandlerOptions): Promise<CreateAddonCommandOutput>;
     createAddon(args: CreateAddonCommandInput, cb: (err: any, data?: CreateAddonCommandOutput) => void): void;
@@ -84,65 +85,71 @@ export declare class EKS extends EKSClient {
      * <p>Creates an Amazon EKS control plane. </p>
      *         <p>The Amazon EKS control plane consists of control plane instances that run the Kubernetes
      *             software, such as <code>etcd</code> and the API server. The control plane runs in an
-     *             account managed by Amazon Web Services, and the Kubernetes API is exposed via the Amazon EKS API server
-     *             endpoint. Each Amazon EKS cluster control plane is single-tenant and unique and runs on its
+     *             account managed by Amazon Web Services, and the Kubernetes API is exposed by the Amazon EKS API server
+     *             endpoint. Each Amazon EKS cluster control plane is single tenant and unique. It runs on its
      *             own set of Amazon EC2 instances.</p>
      *         <p>The cluster control plane is provisioned across multiple Availability Zones and
      *             fronted by an Elastic Load Balancing Network Load Balancer. Amazon EKS also provisions elastic network interfaces in your VPC
      *             subnets to provide connectivity from the control plane instances to the nodes (for
      *             example, to support <code>kubectl exec</code>, <code>logs</code>, and <code>proxy</code>
      *             data flows).</p>
-     *         <p>Amazon EKS nodes run in your Amazon Web Services account and connect to your cluster's control plane via
+     *         <p>Amazon EKS nodes run in your Amazon Web Services account and connect to your cluster's control plane over
      *             the Kubernetes API server endpoint and a certificate file that is created for your
      *             cluster.</p>
      *
-     *         <p>Cluster creation typically takes several minutes. After you create an Amazon EKS cluster,
+     *         <p>In most cases, it takes several minutes to create a cluster. After you create an Amazon EKS cluster,
      *             you must configure your Kubernetes tooling to communicate with the API server and launch
      *             nodes into your cluster. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/managing-auth.html">Managing Cluster
-     *                 Authentication</a> and <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-workers.html">Launching Amazon EKS nodes</a> in the <i>Amazon EKS User Guide</i>.</p>
+     *                 Authentication</a> and <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-workers.html">Launching Amazon EKS nodes</a> in the
+     *             <i>Amazon EKS User Guide</i>.</p>
      */
     createCluster(args: CreateClusterCommandInput, options?: __HttpHandlerOptions): Promise<CreateClusterCommandOutput>;
     createCluster(args: CreateClusterCommandInput, cb: (err: any, data?: CreateClusterCommandOutput) => void): void;
     createCluster(args: CreateClusterCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateClusterCommandOutput) => void): void;
     /**
-     * <p>Creates an Fargate profile for your Amazon EKS cluster. You must have at least one Fargate
-     *             profile in a cluster to be able to run pods on Fargate.</p>
-     *         <p>The Fargate profile allows an administrator to declare which pods run on Fargate and specify
-     *             which pods run on which Fargate profile. This declaration is done through the profile’s
-     *             selectors. Each profile can have up to five selectors that contain a namespace and
-     *             labels. A namespace is required for every selector. The label field consists of multiple
-     *             optional key-value pairs. Pods that match the selectors are scheduled on Fargate. If a
-     *             to-be-scheduled pod matches any of the selectors in the Fargate profile, then that pod is
-     *             run on Fargate.</p>
-     *         <p>When you create a Fargate profile, you must specify a pod execution role to use with the
-     *             pods that are scheduled with the profile. This role is added to the cluster's Kubernetes
-     *                 <a href="https://kubernetes.io/docs/admin/authorization/rbac/">Role Based Access
-     *                 Control</a> (RBAC) for authorization so that the <code>kubelet</code> that is
-     *             running on the Fargate infrastructure can register with your Amazon EKS cluster so that it can
-     *             appear in your cluster as a node. The pod execution role also provides IAM permissions
-     *             to the Fargate infrastructure to allow read access to Amazon ECR image repositories. For more
-     *             information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/pod-execution-role.html">Pod Execution Role</a> in the <i>Amazon EKS User Guide</i>.</p>
-     *         <p>Fargate profiles are immutable. However, you can create a new updated profile to replace
-     *             an existing profile and then delete the original after the updated profile has finished
-     *             creating.</p>
-     *         <p>If any Fargate profiles in a cluster are in the <code>DELETING</code> status, you must
-     *             wait for that Fargate profile to finish deleting before you can create any other profiles
-     *             in that cluster.</p>
-     *         <p>For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/fargate-profile.html">Fargate Profile</a> in the <i>Amazon EKS User Guide</i>.</p>
+     * <p>Creates an Fargate profile for your Amazon EKS cluster. You
+     *             must have at least one Fargate profile in a cluster to be able to run
+     *             pods on Fargate.</p>
+     *         <p>The Fargate profile allows an administrator to declare which pods run
+     *             on Fargate and specify which pods run on which Fargate
+     *             profile. This declaration is done through the profile’s selectors. Each profile can have
+     *             up to five selectors that contain a namespace and labels. A namespace is required for
+     *             every selector. The label field consists of multiple optional key-value pairs. Pods that
+     *             match the selectors are scheduled on Fargate. If a to-be-scheduled pod
+     *             matches any of the selectors in the Fargate profile, then that pod is run
+     *             on Fargate.</p>
+     *         <p>When you create a Fargate profile, you must specify a pod execution
+     *             role to use with the pods that are scheduled with the profile. This role is added to the
+     *             cluster's Kubernetes <a href="https://kubernetes.io/docs/admin/authorization/rbac/">Role Based Access Control</a> (RBAC) for authorization so that the
+     *                 <code>kubelet</code> that is running on the Fargate infrastructure
+     *             can register with your Amazon EKS cluster so that it can appear in your cluster
+     *             as a node. The pod execution role also provides IAM permissions to the
+     *                 Fargate infrastructure to allow read access to Amazon ECR
+     *             image repositories. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/pod-execution-role.html">Pod
+     *                 Execution Role</a> in the <i>Amazon EKS User Guide</i>.</p>
+     *         <p>Fargate profiles are immutable. However, you can create a new updated
+     *             profile to replace an existing profile and then delete the original after the updated
+     *             profile has finished creating.</p>
+     *         <p>If any Fargate profiles in a cluster are in the <code>DELETING</code>
+     *             status, you must wait for that Fargate profile to finish deleting before
+     *             you can create any other profiles in that cluster.</p>
+     *         <p>For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/fargate-profile.html">Fargate Profile</a> in the
+     *             <i>Amazon EKS User Guide</i>.</p>
      */
     createFargateProfile(args: CreateFargateProfileCommandInput, options?: __HttpHandlerOptions): Promise<CreateFargateProfileCommandOutput>;
     createFargateProfile(args: CreateFargateProfileCommandInput, cb: (err: any, data?: CreateFargateProfileCommandOutput) => void): void;
     createFargateProfile(args: CreateFargateProfileCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateFargateProfileCommandOutput) => void): void;
     /**
-     * <p>Creates a managed node group for an Amazon EKS cluster. You can only create a node group
-     *             for your cluster that is equal to the current Kubernetes version for the cluster. All
-     *             node groups are created with the latest AMI release version for the respective minor
-     *             Kubernetes version of the cluster, unless you deploy a custom AMI using a launch
-     *             template. For more information about using launch templates, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Launch
+     * <p>Creates a managed node group for an Amazon EKS cluster. You can only create a
+     *             node group for your cluster that is equal to the current Kubernetes version for the
+     *             cluster. All node groups are created with the latest AMI release version for the
+     *             respective minor Kubernetes version of the cluster, unless you deploy a custom AMI using
+     *             a launch template. For more information about using launch templates, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Launch
      *                 template support</a>.</p>
-     *         <p>An Amazon EKS managed node group is an Amazon EC2 Auto Scaling group and associated Amazon EC2 instances that
-     *             are managed by Amazon Web Services for an Amazon EKS cluster. Each node group uses a version of the Amazon EKS
-     *             optimized Amazon Linux 2 AMI. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html">Managed
+     *         <p>An Amazon EKS managed node group is an Amazon EC2
+     *             Auto Scaling group and associated Amazon EC2 instances that are managed by
+     *                 Amazon Web Services for an Amazon EKS cluster. Each node group uses a version
+     *             of the Amazon EKS optimized Amazon Linux 2 AMI. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html">Managed
      *                 Node Groups</a> in the <i>Amazon EKS User Guide</i>. </p>
      */
     createNodegroup(args: CreateNodegroupCommandInput, options?: __HttpHandlerOptions): Promise<CreateNodegroupCommandOutput>;
@@ -163,21 +170,22 @@ export declare class EKS extends EKSClient {
      *             are deleted properly. Otherwise, you can have orphaned resources in your VPC that
      *             prevent you from being able to delete the VPC. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/delete-cluster.html">Deleting a
      *                 Cluster</a> in the <i>Amazon EKS User Guide</i>.</p>
-     *         <p>If you have managed node groups or Fargate profiles attached to the cluster, you must
-     *             delete them first. For more information, see <a>DeleteNodegroup</a> and <a>DeleteFargateProfile</a>.</p>
+     *         <p>If you have managed node groups or Fargate profiles attached to the
+     *             cluster, you must delete them first. For more information, see <a>DeleteNodegroup</a> and <a>DeleteFargateProfile</a>.</p>
      */
     deleteCluster(args: DeleteClusterCommandInput, options?: __HttpHandlerOptions): Promise<DeleteClusterCommandOutput>;
     deleteCluster(args: DeleteClusterCommandInput, cb: (err: any, data?: DeleteClusterCommandOutput) => void): void;
     deleteCluster(args: DeleteClusterCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteClusterCommandOutput) => void): void;
     /**
      * <p>Deletes an Fargate profile.</p>
-     *         <p>When you delete a Fargate profile, any pods running on Fargate that were created with the
-     *             profile are deleted. If those pods match another Fargate profile, then they are scheduled
-     *             on Fargate with that profile. If they no longer match any Fargate profiles, then they are not
-     *             scheduled on Fargate and they may remain in a pending state.</p>
-     *         <p>Only one Fargate profile in a cluster can be in the <code>DELETING</code> status at a
-     *             time. You must wait for a Fargate profile to finish deleting before you can delete any
-     *             other profiles in that cluster.</p>
+     *         <p>When you delete a Fargate profile, any pods running on Fargate that were created with the profile are deleted. If those pods match
+     *             another Fargate profile, then they are scheduled on Fargate with that profile. If they no longer match any Fargate profiles, then
+     *             they are not scheduled on Fargate and they may remain in a pending
+     *             state.</p>
+     *         <p>Only one Fargate profile in a cluster can be in the
+     *                 <code>DELETING</code> status at a time. You must wait for a Fargate
+     *             profile to finish deleting before you can delete any other profiles in that
+     *             cluster.</p>
      */
     deleteFargateProfile(args: DeleteFargateProfileCommandInput, options?: __HttpHandlerOptions): Promise<DeleteFargateProfileCommandOutput>;
     deleteFargateProfile(args: DeleteFargateProfileCommandInput, cb: (err: any, data?: DeleteFargateProfileCommandOutput) => void): void;
@@ -189,7 +197,8 @@ export declare class EKS extends EKSClient {
     deleteNodegroup(args: DeleteNodegroupCommandInput, cb: (err: any, data?: DeleteNodegroupCommandOutput) => void): void;
     deleteNodegroup(args: DeleteNodegroupCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteNodegroupCommandOutput) => void): void;
     /**
-     * <p>Deregisters a connected cluster to remove it from the Amazon EKS control plane.</p>
+     * <p>Deregisters a connected cluster to remove it from the Amazon EKS control
+     *             plane.</p>
      */
     deregisterCluster(args: DeregisterClusterCommandInput, options?: __HttpHandlerOptions): Promise<DeregisterClusterCommandOutput>;
     deregisterCluster(args: DeregisterClusterCommandInput, cb: (err: any, data?: DeregisterClusterCommandOutput) => void): void;
@@ -239,8 +248,8 @@ export declare class EKS extends EKSClient {
     describeNodegroup(args: DescribeNodegroupCommandInput, cb: (err: any, data?: DescribeNodegroupCommandOutput) => void): void;
     describeNodegroup(args: DescribeNodegroupCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeNodegroupCommandOutput) => void): void;
     /**
-     * <p>Returns descriptive information about an update against your Amazon EKS cluster or
-     *             associated managed node group.</p>
+     * <p>Returns descriptive information about an update against your Amazon EKS
+     *             cluster or associated managed node group.</p>
      *         <p>When the status of the update is <code>Succeeded</code>, the update is complete. If an
      *             update fails, the status is <code>Failed</code>, and an error detail explains the reason
      *             for the failure.</p>
@@ -251,8 +260,8 @@ export declare class EKS extends EKSClient {
     /**
      * <p>Disassociates an identity provider configuration from a cluster. If you disassociate
      *             an identity provider from your cluster, users included in the provider can no longer
-     *             access the cluster. However, you can still access the cluster with Amazon Web Services IAM
-     *             users.</p>
+     *             access the cluster. However, you can still access the cluster with Amazon Web Services
+     *             IAM users.</p>
      */
     disassociateIdentityProviderConfig(args: DisassociateIdentityProviderConfigCommandInput, options?: __HttpHandlerOptions): Promise<DisassociateIdentityProviderConfigCommandOutput>;
     disassociateIdentityProviderConfig(args: DisassociateIdentityProviderConfigCommandInput, cb: (err: any, data?: DisassociateIdentityProviderConfigCommandOutput) => void): void;
@@ -264,14 +273,15 @@ export declare class EKS extends EKSClient {
     listAddons(args: ListAddonsCommandInput, cb: (err: any, data?: ListAddonsCommandOutput) => void): void;
     listAddons(args: ListAddonsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListAddonsCommandOutput) => void): void;
     /**
-     * <p>Lists the Amazon EKS clusters in your Amazon Web Services account in the specified Region.</p>
+     * <p>Lists the Amazon EKS clusters in your Amazon Web Services account in the
+     *             specified Region.</p>
      */
     listClusters(args: ListClustersCommandInput, options?: __HttpHandlerOptions): Promise<ListClustersCommandOutput>;
     listClusters(args: ListClustersCommandInput, cb: (err: any, data?: ListClustersCommandOutput) => void): void;
     listClusters(args: ListClustersCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListClustersCommandOutput) => void): void;
     /**
-     * <p>Lists the Fargate profiles associated with the specified cluster in your Amazon Web Services
-     *             account in the specified Region.</p>
+     * <p>Lists the Fargate profiles associated with the specified cluster in
+     *             your Amazon Web Services account in the specified Region.</p>
      */
     listFargateProfiles(args: ListFargateProfilesCommandInput, options?: __HttpHandlerOptions): Promise<ListFargateProfilesCommandOutput>;
     listFargateProfiles(args: ListFargateProfilesCommandInput, cb: (err: any, data?: ListFargateProfilesCommandOutput) => void): void;
@@ -283,8 +293,9 @@ export declare class EKS extends EKSClient {
     listIdentityProviderConfigs(args: ListIdentityProviderConfigsCommandInput, cb: (err: any, data?: ListIdentityProviderConfigsCommandOutput) => void): void;
     listIdentityProviderConfigs(args: ListIdentityProviderConfigsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListIdentityProviderConfigsCommandOutput) => void): void;
     /**
-     * <p>Lists the Amazon EKS managed node groups associated with the specified cluster in your
-     *             Amazon Web Services account in the specified Region. Self-managed node groups are not listed.</p>
+     * <p>Lists the Amazon EKS managed node groups associated with the specified cluster
+     *             in your Amazon Web Services account in the specified Region. Self-managed node groups are
+     *             not listed.</p>
      */
     listNodegroups(args: ListNodegroupsCommandInput, options?: __HttpHandlerOptions): Promise<ListNodegroupsCommandOutput>;
     listNodegroups(args: ListNodegroupsCommandInput, cb: (err: any, data?: ListNodegroupsCommandOutput) => void): void;
@@ -296,22 +307,26 @@ export declare class EKS extends EKSClient {
     listTagsForResource(args: ListTagsForResourceCommandInput, cb: (err: any, data?: ListTagsForResourceCommandOutput) => void): void;
     listTagsForResource(args: ListTagsForResourceCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListTagsForResourceCommandOutput) => void): void;
     /**
-     * <p>Lists the updates associated with an Amazon EKS cluster or managed node group in your Amazon Web Services
-     *             account, in the specified Region.</p>
+     * <p>Lists the updates associated with an Amazon EKS cluster or managed node group
+     *             in your Amazon Web Services account, in the specified Region.</p>
      */
     listUpdates(args: ListUpdatesCommandInput, options?: __HttpHandlerOptions): Promise<ListUpdatesCommandOutput>;
     listUpdates(args: ListUpdatesCommandInput, cb: (err: any, data?: ListUpdatesCommandOutput) => void): void;
     listUpdates(args: ListUpdatesCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListUpdatesCommandOutput) => void): void;
     /**
      * <p>Connects a Kubernetes cluster to the Amazon EKS control plane. </p>
-     *         <p>Any Kubernetes cluster can be connected to the Amazon EKS control plane to view current information about the cluster and its nodes.
-     *          </p>
+     *         <p>Any Kubernetes cluster can be connected to the Amazon EKS control plane to
+     *             view current information about the cluster and its nodes. </p>
      *         <p>Cluster connection requires two steps. First, send a <code>
      *                <a>RegisterClusterRequest</a>
-     *             </code> to add it to the Amazon EKS control plane.</p>
-     *         <p>Second, a <a href="https://amazon-eks.s3.us-west-2.amazonaws.com/eks-connector/manifests/eks-connector/latest/eks-connector.yaml">Manifest</a> containing the <code>activationID</code> and <code>activationCode</code> must be applied to the Kubernetes cluster through it's native provider to provide visibility.</p>
+     *             </code> to add it to the Amazon EKS
+     *             control plane.</p>
+     *         <p>Second, a <a href="https://amazon-eks.s3.us-west-2.amazonaws.com/eks-connector/manifests/eks-connector/latest/eks-connector.yaml">Manifest</a> containing the <code>activationID</code> and
+     *                 <code>activationCode</code> must be applied to the Kubernetes cluster through it's
+     *             native provider to provide visibility.</p>
      *
-     *         <p>After the Manifest is updated and applied, then the connected cluster is visible to the Amazon EKS control plane. If the Manifest is not applied within a set amount of time,
+     *         <p>After the Manifest is updated and applied, then the connected cluster is visible to
+     *             the Amazon EKS control plane. If the Manifest is not applied within three days,
      *             then the connected cluster will no longer be visible and must be deregistered. See <a>DeregisterCluster</a>.</p>
      */
     registerCluster(args: RegisterClusterCommandInput, options?: __HttpHandlerOptions): Promise<RegisterClusterCommandOutput>;
@@ -321,10 +336,9 @@ export declare class EKS extends EKSClient {
      * <p>Associates the specified tags to a resource with the specified
      *                 <code>resourceArn</code>. If existing tags on a resource are not specified in the
      *             request parameters, they are not changed. When a resource is deleted, the tags
-     *             associated with that resource are deleted as well. Tags that you create for Amazon EKS
-     *             resources do not propagate to any other resources associated with the cluster. For
-     *             example, if you tag a cluster with this operation, that tag does not automatically
-     *             propagate to the subnets and nodes associated with the cluster.</p>
+     *             associated with that resource are deleted as well. Tags that you create for Amazon EKS resources do not propagate to any other resources associated with the
+     *             cluster. For example, if you tag a cluster with this operation, that tag does not
+     *             automatically propagate to the subnets and nodes associated with the cluster.</p>
      */
     tagResource(args: TagResourceCommandInput, options?: __HttpHandlerOptions): Promise<TagResourceCommandOutput>;
     tagResource(args: TagResourceCommandInput, cb: (err: any, data?: TagResourceCommandOutput) => void): void;
@@ -342,24 +356,25 @@ export declare class EKS extends EKSClient {
     updateAddon(args: UpdateAddonCommandInput, cb: (err: any, data?: UpdateAddonCommandOutput) => void): void;
     updateAddon(args: UpdateAddonCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateAddonCommandOutput) => void): void;
     /**
-     * <p>Updates an Amazon EKS cluster configuration. Your cluster continues to function during the
-     *             update. The response output includes an update ID that you can use to track the status
-     *             of your cluster update with the <a>DescribeUpdate</a> API operation.</p>
+     * <p>Updates an Amazon EKS cluster configuration. Your cluster continues to
+     *             function during the update. The response output includes an update ID that you can use
+     *             to track the status of your cluster update with the <a>DescribeUpdate</a> API
+     *             operation.</p>
      *         <p>You can use this API operation to enable or disable exporting the Kubernetes control
-     *             plane logs for your cluster to CloudWatch Logs. By default, cluster control plane logs aren't
-     *             exported to CloudWatch Logs. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/control-plane-logs.html">Amazon EKS
-     *                 Cluster Control Plane Logs</a> in the
-     *             <i>
+     *             plane logs for your cluster to CloudWatch Logs. By default, cluster control plane
+     *             logs aren't exported to CloudWatch Logs. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/control-plane-logs.html">Amazon EKS Cluster Control Plane Logs</a> in the
+     *                 <i>
      *                <i>Amazon EKS User Guide</i>
      *             </i>.</p>
      *         <note>
-     *             <p>CloudWatch Logs ingestion, archive storage, and data scanning rates apply to exported
-     *                 control plane logs. For more information, see <a href="http://aws.amazon.com/cloudwatch/pricing/">CloudWatch Pricing</a>.</p>
+     *             <p>CloudWatch Logs ingestion, archive storage, and data scanning rates apply to
+     *                 exported control plane logs. For more information, see <a href="http://aws.amazon.com/cloudwatch/pricing/">CloudWatch
+     *                 Pricing</a>.</p>
      *         </note>
      *         <p>You can also use this API operation to enable or disable public and private access to
      *             your cluster's Kubernetes API server endpoint. By default, public access is enabled, and
-     *             private access is disabled. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html">Amazon EKS cluster
-     *                 endpoint access control</a> in the <i>
+     *             private access is disabled. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html">Amazon EKS cluster endpoint access control</a> in the
+     *                 <i>
      *                <i>Amazon EKS User Guide</i>
      *             </i>. </p>
      *         <important>
@@ -374,10 +389,9 @@ export declare class EKS extends EKSClient {
     updateClusterConfig(args: UpdateClusterConfigCommandInput, cb: (err: any, data?: UpdateClusterConfigCommandOutput) => void): void;
     updateClusterConfig(args: UpdateClusterConfigCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateClusterConfigCommandOutput) => void): void;
     /**
-     * <p>Updates an Amazon EKS cluster to the specified Kubernetes version. Your cluster continues
-     *             to function during the update. The response output includes an update ID that you can
-     *             use to track the status of your cluster update with the <a>DescribeUpdate</a>
-     *             API operation.</p>
+     * <p>Updates an Amazon EKS cluster to the specified Kubernetes version. Your
+     *             cluster continues to function during the update. The response output includes an update
+     *             ID that you can use to track the status of your cluster update with the <a>DescribeUpdate</a> API operation.</p>
      *         <p>Cluster updates are asynchronous, and they should finish within a few minutes. During
      *             an update, the cluster status moves to <code>UPDATING</code> (this status transition is
      *             eventually consistent). When the update is complete (either <code>Failed</code> or
@@ -390,17 +404,17 @@ export declare class EKS extends EKSClient {
     updateClusterVersion(args: UpdateClusterVersionCommandInput, cb: (err: any, data?: UpdateClusterVersionCommandOutput) => void): void;
     updateClusterVersion(args: UpdateClusterVersionCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateClusterVersionCommandOutput) => void): void;
     /**
-     * <p>Updates an Amazon EKS managed node group configuration. Your node group continues to
-     *             function during the update. The response output includes an update ID that you can use
-     *             to track the status of your node group update with the <a>DescribeUpdate</a>
-     *             API operation. Currently you can update the Kubernetes labels for a node group or the
-     *             scaling configuration.</p>
+     * <p>Updates an Amazon EKS managed node group configuration. Your node group
+     *             continues to function during the update. The response output includes an update ID that
+     *             you can use to track the status of your node group update with the <a>DescribeUpdate</a> API operation. Currently you can update the Kubernetes
+     *             labels for a node group or the scaling configuration.</p>
      */
     updateNodegroupConfig(args: UpdateNodegroupConfigCommandInput, options?: __HttpHandlerOptions): Promise<UpdateNodegroupConfigCommandOutput>;
     updateNodegroupConfig(args: UpdateNodegroupConfigCommandInput, cb: (err: any, data?: UpdateNodegroupConfigCommandOutput) => void): void;
     updateNodegroupConfig(args: UpdateNodegroupConfigCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateNodegroupConfigCommandOutput) => void): void;
     /**
-     * <p>Updates the Kubernetes version or AMI version of an Amazon EKS managed node group.</p>
+     * <p>Updates the Kubernetes version or AMI version of an Amazon EKS managed node
+     *             group.</p>
      *         <p>You can update a node group using a launch template only if the node group was
      *             originally deployed with a launch template. If you need to update a custom AMI in a node
      *             group that was deployed with a launch template, then update your custom AMI, specify the
@@ -410,14 +424,14 @@ export declare class EKS extends EKSClient {
      *             AMI version of a node group's current Kubernetes version by not specifying a Kubernetes
      *             version in the request. You can update to the latest AMI version of your cluster's
      *             current Kubernetes version by specifying your cluster's Kubernetes version in the
-     *             request. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-linux-ami-versions.html">Amazon EKS
-     *                 optimized Amazon Linux 2 AMI versions</a> in the <i>Amazon EKS User Guide</i>.</p>
+     *             request. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-linux-ami-versions.html">Amazon EKS optimized Amazon Linux 2 AMI versions</a> in the <i>Amazon EKS User Guide</i>.</p>
      *         <p>You cannot roll back a node group to an earlier Kubernetes version or AMI
      *             version.</p>
      *         <p>When a node in a managed node group is terminated due to a scaling action or update,
-     *             the pods in that node are drained first. Amazon EKS attempts to drain the nodes gracefully
-     *             and will fail if it is unable to do so. You can <code>force</code> the update if Amazon EKS
-     *             is unable to drain the nodes as a result of a pod disruption budget issue.</p>
+     *             the pods in that node are drained first. Amazon EKS attempts to drain the nodes
+     *             gracefully and will fail if it is unable to do so. You can <code>force</code> the update
+     *             if Amazon EKS is unable to drain the nodes as a result of a pod disruption
+     *             budget issue.</p>
      */
     updateNodegroupVersion(args: UpdateNodegroupVersionCommandInput, options?: __HttpHandlerOptions): Promise<UpdateNodegroupVersionCommandOutput>;
     updateNodegroupVersion(args: UpdateNodegroupVersionCommandInput, cb: (err: any, data?: UpdateNodegroupVersionCommandOutput) => void): void;

package/dist-types/EKSClient.d.ts

@@ -156,16 +156,16 @@ declare type EKSClientResolvedConfigType = __SmithyResolvedConfiguration<__HttpH
 export interface EKSClientResolvedConfig extends EKSClientResolvedConfigType {
 }
 /**
- * <p>Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that makes it easy for you to run Kubernetes on
- *             Amazon Web Services without needing to stand up or maintain your own Kubernetes control plane.
- *             Kubernetes is an open-source system for automating the deployment, scaling, and
- *             management of containerized applications. </p>
- *         <p>Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so you can use
- *             all the existing plugins and tooling from the Kubernetes community. Applications running
- *             on Amazon EKS are fully compatible with applications running on any standard Kubernetes
- *             environment, whether running in on-premises data centers or public clouds. This means
- *             that you can easily migrate any standard Kubernetes application to Amazon EKS without any
- *             code modification required.</p>
+ * <p>Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that makes it easy
+ *             for you to run Kubernetes on Amazon Web Services without needing to stand up or maintain
+ *             your own Kubernetes control plane. Kubernetes is an open-source system for automating
+ *             the deployment, scaling, and management of containerized applications. </p>
+ *         <p>Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so
+ *             you can use all the existing plugins and tooling from the Kubernetes community.
+ *             Applications running on Amazon EKS are fully compatible with applications
+ *             running on any standard Kubernetes environment, whether running in on-premises data
+ *             centers or public clouds. This means that you can easily migrate any standard Kubernetes
+ *             application to Amazon EKS without any code modification required.</p>
  */
 export declare class EKSClient extends __Client<__HttpHandlerOptions, ServiceInputTypes, ServiceOutputTypes, EKSClientResolvedConfig> {
     /**

package/dist-types/commands/CreateAddonCommand.d.ts

@@ -8,11 +8,12 @@ export interface CreateAddonCommandOutput extends CreateAddonResponse, __Metadat
 }
 /**
  * <p>Creates an Amazon EKS add-on.</p>
- *         <p>Amazon EKS add-ons help to automate the provisioning and lifecycle management of common
- *             operational software for Amazon EKS clusters. Amazon EKS add-ons can only be used with Amazon EKS
- *             clusters running version 1.18 with platform version <code>eks.3</code> or later because
+ *         <p>Amazon EKS add-ons help to automate the provisioning and lifecycle management
+ *             of common operational software for Amazon EKS clusters. Amazon EKS
+ *             add-ons require clusters running version 1.18 or later because Amazon EKS
  *             add-ons rely on the Server-side Apply Kubernetes feature, which is only available in
- *             Kubernetes 1.18 and later.</p>
+ *             Kubernetes 1.18 and later. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-add-ons.html">Amazon EKS add-ons</a> in
+ *             the <i>Amazon EKS User Guide</i>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/CreateClusterCommand.d.ts

@@ -10,22 +10,23 @@ export interface CreateClusterCommandOutput extends CreateClusterResponse, __Met
  * <p>Creates an Amazon EKS control plane. </p>
  *         <p>The Amazon EKS control plane consists of control plane instances that run the Kubernetes
  *             software, such as <code>etcd</code> and the API server. The control plane runs in an
- *             account managed by Amazon Web Services, and the Kubernetes API is exposed via the Amazon EKS API server
- *             endpoint. Each Amazon EKS cluster control plane is single-tenant and unique and runs on its
+ *             account managed by Amazon Web Services, and the Kubernetes API is exposed by the Amazon EKS API server
+ *             endpoint. Each Amazon EKS cluster control plane is single tenant and unique. It runs on its
  *             own set of Amazon EC2 instances.</p>
  *         <p>The cluster control plane is provisioned across multiple Availability Zones and
  *             fronted by an Elastic Load Balancing Network Load Balancer. Amazon EKS also provisions elastic network interfaces in your VPC
  *             subnets to provide connectivity from the control plane instances to the nodes (for
  *             example, to support <code>kubectl exec</code>, <code>logs</code>, and <code>proxy</code>
  *             data flows).</p>
- *         <p>Amazon EKS nodes run in your Amazon Web Services account and connect to your cluster's control plane via
+ *         <p>Amazon EKS nodes run in your Amazon Web Services account and connect to your cluster's control plane over
  *             the Kubernetes API server endpoint and a certificate file that is created for your
  *             cluster.</p>
  *
- *         <p>Cluster creation typically takes several minutes. After you create an Amazon EKS cluster,
+ *         <p>In most cases, it takes several minutes to create a cluster. After you create an Amazon EKS cluster,
  *             you must configure your Kubernetes tooling to communicate with the API server and launch
  *             nodes into your cluster. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/managing-auth.html">Managing Cluster
- *                 Authentication</a> and <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-workers.html">Launching Amazon EKS nodes</a> in the <i>Amazon EKS User Guide</i>.</p>
+ *                 Authentication</a> and <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-workers.html">Launching Amazon EKS nodes</a> in the
+ *             <i>Amazon EKS User Guide</i>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/CreateFargateProfileCommand.d.ts

@@ -7,30 +7,34 @@ export interface CreateFargateProfileCommandInput extends CreateFargateProfileRe
 export interface CreateFargateProfileCommandOutput extends CreateFargateProfileResponse, __MetadataBearer {
 }
 /**
- * <p>Creates an Fargate profile for your Amazon EKS cluster. You must have at least one Fargate
- *             profile in a cluster to be able to run pods on Fargate.</p>
- *         <p>The Fargate profile allows an administrator to declare which pods run on Fargate and specify
- *             which pods run on which Fargate profile. This declaration is done through the profile’s
- *             selectors. Each profile can have up to five selectors that contain a namespace and
- *             labels. A namespace is required for every selector. The label field consists of multiple
- *             optional key-value pairs. Pods that match the selectors are scheduled on Fargate. If a
- *             to-be-scheduled pod matches any of the selectors in the Fargate profile, then that pod is
- *             run on Fargate.</p>
- *         <p>When you create a Fargate profile, you must specify a pod execution role to use with the
- *             pods that are scheduled with the profile. This role is added to the cluster's Kubernetes
- *                 <a href="https://kubernetes.io/docs/admin/authorization/rbac/">Role Based Access
- *                 Control</a> (RBAC) for authorization so that the <code>kubelet</code> that is
- *             running on the Fargate infrastructure can register with your Amazon EKS cluster so that it can
- *             appear in your cluster as a node. The pod execution role also provides IAM permissions
- *             to the Fargate infrastructure to allow read access to Amazon ECR image repositories. For more
- *             information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/pod-execution-role.html">Pod Execution Role</a> in the <i>Amazon EKS User Guide</i>.</p>
- *         <p>Fargate profiles are immutable. However, you can create a new updated profile to replace
- *             an existing profile and then delete the original after the updated profile has finished
- *             creating.</p>
- *         <p>If any Fargate profiles in a cluster are in the <code>DELETING</code> status, you must
- *             wait for that Fargate profile to finish deleting before you can create any other profiles
- *             in that cluster.</p>
- *         <p>For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/fargate-profile.html">Fargate Profile</a> in the <i>Amazon EKS User Guide</i>.</p>
+ * <p>Creates an Fargate profile for your Amazon EKS cluster. You
+ *             must have at least one Fargate profile in a cluster to be able to run
+ *             pods on Fargate.</p>
+ *         <p>The Fargate profile allows an administrator to declare which pods run
+ *             on Fargate and specify which pods run on which Fargate
+ *             profile. This declaration is done through the profile’s selectors. Each profile can have
+ *             up to five selectors that contain a namespace and labels. A namespace is required for
+ *             every selector. The label field consists of multiple optional key-value pairs. Pods that
+ *             match the selectors are scheduled on Fargate. If a to-be-scheduled pod
+ *             matches any of the selectors in the Fargate profile, then that pod is run
+ *             on Fargate.</p>
+ *         <p>When you create a Fargate profile, you must specify a pod execution
+ *             role to use with the pods that are scheduled with the profile. This role is added to the
+ *             cluster's Kubernetes <a href="https://kubernetes.io/docs/admin/authorization/rbac/">Role Based Access Control</a> (RBAC) for authorization so that the
+ *                 <code>kubelet</code> that is running on the Fargate infrastructure
+ *             can register with your Amazon EKS cluster so that it can appear in your cluster
+ *             as a node. The pod execution role also provides IAM permissions to the
+ *                 Fargate infrastructure to allow read access to Amazon ECR
+ *             image repositories. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/pod-execution-role.html">Pod
+ *                 Execution Role</a> in the <i>Amazon EKS User Guide</i>.</p>
+ *         <p>Fargate profiles are immutable. However, you can create a new updated
+ *             profile to replace an existing profile and then delete the original after the updated
+ *             profile has finished creating.</p>
+ *         <p>If any Fargate profiles in a cluster are in the <code>DELETING</code>
+ *             status, you must wait for that Fargate profile to finish deleting before
+ *             you can create any other profiles in that cluster.</p>
+ *         <p>For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/fargate-profile.html">Fargate Profile</a> in the
+ *             <i>Amazon EKS User Guide</i>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/CreateNodegroupCommand.d.ts

@@ -7,15 +7,16 @@ export interface CreateNodegroupCommandInput extends CreateNodegroupRequest {
 export interface CreateNodegroupCommandOutput extends CreateNodegroupResponse, __MetadataBearer {
 }
 /**
- * <p>Creates a managed node group for an Amazon EKS cluster. You can only create a node group
- *             for your cluster that is equal to the current Kubernetes version for the cluster. All
- *             node groups are created with the latest AMI release version for the respective minor
- *             Kubernetes version of the cluster, unless you deploy a custom AMI using a launch
- *             template. For more information about using launch templates, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Launch
+ * <p>Creates a managed node group for an Amazon EKS cluster. You can only create a
+ *             node group for your cluster that is equal to the current Kubernetes version for the
+ *             cluster. All node groups are created with the latest AMI release version for the
+ *             respective minor Kubernetes version of the cluster, unless you deploy a custom AMI using
+ *             a launch template. For more information about using launch templates, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html">Launch
  *                 template support</a>.</p>
- *         <p>An Amazon EKS managed node group is an Amazon EC2 Auto Scaling group and associated Amazon EC2 instances that
- *             are managed by Amazon Web Services for an Amazon EKS cluster. Each node group uses a version of the Amazon EKS
- *             optimized Amazon Linux 2 AMI. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html">Managed
+ *         <p>An Amazon EKS managed node group is an Amazon EC2
+ *             Auto Scaling group and associated Amazon EC2 instances that are managed by
+ *                 Amazon Web Services for an Amazon EKS cluster. Each node group uses a version
+ *             of the Amazon EKS optimized Amazon Linux 2 AMI. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html">Managed
  *                 Node Groups</a> in the <i>Amazon EKS User Guide</i>. </p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.