@aws-sdk/client-eks 3.312.0 → 3.316.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -35,452 +35,230 @@ import { UpdateClusterVersionCommandInput, UpdateClusterVersionCommandOutput } f
35
35
  import { UpdateNodegroupConfigCommandInput, UpdateNodegroupConfigCommandOutput } from "./commands/UpdateNodegroupConfigCommand";
36
36
  import { UpdateNodegroupVersionCommandInput, UpdateNodegroupVersionCommandOutput } from "./commands/UpdateNodegroupVersionCommand";
37
37
  import { EKSClient } from "./EKSClient";
38
- /**
39
- * @public
40
- * <p>Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that makes it easy
41
- * for you to run Kubernetes on Amazon Web Services without needing to stand up or maintain
42
- * your own Kubernetes control plane. Kubernetes is an open-source system for automating
43
- * the deployment, scaling, and management of containerized applications. </p>
44
- * <p>Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so
45
- * you can use all the existing plugins and tooling from the Kubernetes community.
46
- * Applications running on Amazon EKS are fully compatible with applications
47
- * running on any standard Kubernetes environment, whether running in on-premises data
48
- * centers or public clouds. This means that you can easily migrate any standard Kubernetes
49
- * application to Amazon EKS without any code modification required.</p>
50
- */
51
- export declare class EKS extends EKSClient {
38
+ export interface EKS {
52
39
  /**
53
- * @public
54
- * <p>Associate encryption configuration to an existing cluster.</p>
55
- * <p>You can use this API to enable encryption on existing clusters which do not have
56
- * encryption already enabled. This allows you to implement a defense-in-depth security
57
- * strategy without migrating applications to new Amazon EKS clusters.</p>
40
+ * @see {@link AssociateEncryptionConfigCommand}
58
41
  */
59
42
  associateEncryptionConfig(args: AssociateEncryptionConfigCommandInput, options?: __HttpHandlerOptions): Promise<AssociateEncryptionConfigCommandOutput>;
60
43
  associateEncryptionConfig(args: AssociateEncryptionConfigCommandInput, cb: (err: any, data?: AssociateEncryptionConfigCommandOutput) => void): void;
61
44
  associateEncryptionConfig(args: AssociateEncryptionConfigCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: AssociateEncryptionConfigCommandOutput) => void): void;
62
45
  /**
63
- * @public
64
- * <p>Associate an identity provider configuration to a cluster.</p>
65
- * <p>If you want to authenticate identities using an identity provider, you can create an
66
- * identity provider configuration and associate it to your cluster. After configuring
67
- * authentication to your cluster you can create Kubernetes <code>roles</code> and
68
- * <code>clusterroles</code> to assign permissions to the roles, and then bind the
69
- * roles to the identities using Kubernetes <code>rolebindings</code> and
70
- * <code>clusterrolebindings</code>. For more information see <a href="https://kubernetes.io/docs/reference/access-authn-authz/rbac/">Using RBAC
71
- * Authorization</a> in the Kubernetes documentation.</p>
46
+ * @see {@link AssociateIdentityProviderConfigCommand}
72
47
  */
73
48
  associateIdentityProviderConfig(args: AssociateIdentityProviderConfigCommandInput, options?: __HttpHandlerOptions): Promise<AssociateIdentityProviderConfigCommandOutput>;
74
49
  associateIdentityProviderConfig(args: AssociateIdentityProviderConfigCommandInput, cb: (err: any, data?: AssociateIdentityProviderConfigCommandOutput) => void): void;
75
50
  associateIdentityProviderConfig(args: AssociateIdentityProviderConfigCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: AssociateIdentityProviderConfigCommandOutput) => void): void;
76
51
  /**
77
- * @public
78
- * <p>Creates an Amazon EKS add-on.</p>
79
- * <p>Amazon EKS add-ons help to automate the provisioning and lifecycle management
80
- * of common operational software for Amazon EKS clusters. For more information,
81
- * 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>
52
+ * @see {@link CreateAddonCommand}
82
53
  */
83
54
  createAddon(args: CreateAddonCommandInput, options?: __HttpHandlerOptions): Promise<CreateAddonCommandOutput>;
84
55
  createAddon(args: CreateAddonCommandInput, cb: (err: any, data?: CreateAddonCommandOutput) => void): void;
85
56
  createAddon(args: CreateAddonCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateAddonCommandOutput) => void): void;
86
57
  /**
87
- * @public
88
- * <p>Creates an Amazon EKS control plane. </p>
89
- * <p>The Amazon EKS control plane consists of control plane instances that run the
90
- * Kubernetes software, such as <code>etcd</code> and the API server. The control plane
91
- * runs in an account managed by Amazon Web Services, and the Kubernetes API is exposed by
92
- * the Amazon EKS API server endpoint. Each Amazon EKS cluster control
93
- * plane is single tenant and unique. It runs on its own set of Amazon EC2
94
- * instances.</p>
95
- * <p>The cluster control plane is provisioned across multiple Availability Zones and
96
- * fronted by an Elastic Load Balancing
97
- * Network Load Balancer. Amazon EKS also provisions elastic network interfaces in
98
- * your VPC subnets to provide connectivity from the control plane instances to the nodes
99
- * (for example, to support <code>kubectl exec</code>, <code>logs</code>, and
100
- * <code>proxy</code> data flows).</p>
101
- * <p>Amazon EKS nodes run in your Amazon Web Services account and connect to your
102
- * cluster's control plane over the Kubernetes API server endpoint and a certificate file
103
- * that is created for your cluster.</p>
104
- * <p>In most cases, it takes several minutes to create a cluster. After you create an
105
- * Amazon EKS cluster, you must configure your Kubernetes tooling to
106
- * communicate with the API server and launch nodes into your cluster. For more
107
- * 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
108
- * Amazon EKS nodes</a> in the <i>Amazon EKS User Guide</i>.</p>
58
+ * @see {@link CreateClusterCommand}
109
59
  */
110
60
  createCluster(args: CreateClusterCommandInput, options?: __HttpHandlerOptions): Promise<CreateClusterCommandOutput>;
111
61
  createCluster(args: CreateClusterCommandInput, cb: (err: any, data?: CreateClusterCommandOutput) => void): void;
112
62
  createCluster(args: CreateClusterCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateClusterCommandOutput) => void): void;
113
63
  /**
114
- * @public
115
- * <p>Creates an Fargate profile for your Amazon EKS cluster. You
116
- * must have at least one Fargate profile in a cluster to be able to run
117
- * pods on Fargate.</p>
118
- * <p>The Fargate profile allows an administrator to declare which pods run
119
- * on Fargate and specify which pods run on which Fargate
120
- * profile. This declaration is done through the profile’s selectors. Each profile can have
121
- * up to five selectors that contain a namespace and labels. A namespace is required for
122
- * every selector. The label field consists of multiple optional key-value pairs. Pods that
123
- * match the selectors are scheduled on Fargate. If a to-be-scheduled pod
124
- * matches any of the selectors in the Fargate profile, then that pod is run
125
- * on Fargate.</p>
126
- * <p>When you create a Fargate profile, you must specify a pod execution
127
- * role to use with the pods that are scheduled with the profile. This role is added to the
128
- * cluster's Kubernetes <a href="https://kubernetes.io/docs/admin/authorization/rbac/">Role Based Access Control</a> (RBAC) for authorization so that the
129
- * <code>kubelet</code> that is running on the Fargate infrastructure
130
- * can register with your Amazon EKS cluster so that it can appear in your cluster
131
- * as a node. The pod execution role also provides IAM permissions to the
132
- * Fargate infrastructure to allow read access to Amazon ECR
133
- * image repositories. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/pod-execution-role.html">Pod
134
- * Execution Role</a> in the <i>Amazon EKS User Guide</i>.</p>
135
- * <p>Fargate profiles are immutable. However, you can create a new updated
136
- * profile to replace an existing profile and then delete the original after the updated
137
- * profile has finished creating.</p>
138
- * <p>If any Fargate profiles in a cluster are in the <code>DELETING</code>
139
- * status, you must wait for that Fargate profile to finish deleting before
140
- * you can create any other profiles in that cluster.</p>
141
- * <p>For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/fargate-profile.html">Fargate Profile</a> in the
142
- * <i>Amazon EKS User Guide</i>.</p>
64
+ * @see {@link CreateFargateProfileCommand}
143
65
  */
144
66
  createFargateProfile(args: CreateFargateProfileCommandInput, options?: __HttpHandlerOptions): Promise<CreateFargateProfileCommandOutput>;
145
67
  createFargateProfile(args: CreateFargateProfileCommandInput, cb: (err: any, data?: CreateFargateProfileCommandOutput) => void): void;
146
68
  createFargateProfile(args: CreateFargateProfileCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateFargateProfileCommandOutput) => void): void;
147
69
  /**
148
- * @public
149
- * <p>Creates a managed node group for an Amazon EKS cluster. You can only create a
150
- * node group for your cluster that is equal to the current Kubernetes version for the
151
- * cluster. All node groups are created with the latest AMI release version for the
152
- * respective minor Kubernetes version of the cluster, unless you deploy a custom AMI using
153
- * 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
154
- * template support</a>.</p>
155
- * <p>An Amazon EKS managed node group is an Amazon EC2
156
- * Auto Scaling group and associated Amazon EC2 instances that are managed by
157
- * Amazon Web Services for an Amazon EKS cluster. For more information, see
158
- * <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>
159
- * <note>
160
- * <p>Windows AMI types are only supported for commercial Regions that support Windows
161
- * Amazon EKS.</p>
162
- * </note>
70
+ * @see {@link CreateNodegroupCommand}
163
71
  */
164
72
  createNodegroup(args: CreateNodegroupCommandInput, options?: __HttpHandlerOptions): Promise<CreateNodegroupCommandOutput>;
165
73
  createNodegroup(args: CreateNodegroupCommandInput, cb: (err: any, data?: CreateNodegroupCommandOutput) => void): void;
166
74
  createNodegroup(args: CreateNodegroupCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateNodegroupCommandOutput) => void): void;
167
75
  /**
168
- * @public
169
- * <p>Delete an Amazon EKS add-on.</p>
170
- * <p>When you remove the add-on, it will also be deleted from the cluster. You can always
171
- * manually start an add-on on the cluster using the Kubernetes API.</p>
76
+ * @see {@link DeleteAddonCommand}
172
77
  */
173
78
  deleteAddon(args: DeleteAddonCommandInput, options?: __HttpHandlerOptions): Promise<DeleteAddonCommandOutput>;
174
79
  deleteAddon(args: DeleteAddonCommandInput, cb: (err: any, data?: DeleteAddonCommandOutput) => void): void;
175
80
  deleteAddon(args: DeleteAddonCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteAddonCommandOutput) => void): void;
176
81
  /**
177
- * @public
178
- * <p>Deletes the Amazon EKS cluster control plane.</p>
179
- * <p>If you have active services in your cluster that are associated with a load balancer,
180
- * you must delete those services before deleting the cluster so that the load balancers
181
- * are deleted properly. Otherwise, you can have orphaned resources in your VPC that
182
- * 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
183
- * Cluster</a> in the <i>Amazon EKS User Guide</i>.</p>
184
- * <p>If you have managed node groups or Fargate profiles attached to the
185
- * cluster, you must delete them first. For more information, see <a>DeleteNodegroup</a> and <a>DeleteFargateProfile</a>.</p>
82
+ * @see {@link DeleteClusterCommand}
186
83
  */
187
84
  deleteCluster(args: DeleteClusterCommandInput, options?: __HttpHandlerOptions): Promise<DeleteClusterCommandOutput>;
188
85
  deleteCluster(args: DeleteClusterCommandInput, cb: (err: any, data?: DeleteClusterCommandOutput) => void): void;
189
86
  deleteCluster(args: DeleteClusterCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteClusterCommandOutput) => void): void;
190
87
  /**
191
- * @public
192
- * <p>Deletes an Fargate profile.</p>
193
- * <p>When you delete a Fargate profile, any pods running on Fargate that were created with the profile are deleted. If those pods match
194
- * another Fargate profile, then they are scheduled on Fargate with that profile. If they no longer match any Fargate profiles, then
195
- * they are not scheduled on Fargate and they may remain in a pending
196
- * state.</p>
197
- * <p>Only one Fargate profile in a cluster can be in the
198
- * <code>DELETING</code> status at a time. You must wait for a Fargate
199
- * profile to finish deleting before you can delete any other profiles in that
200
- * cluster.</p>
88
+ * @see {@link DeleteFargateProfileCommand}
201
89
  */
202
90
  deleteFargateProfile(args: DeleteFargateProfileCommandInput, options?: __HttpHandlerOptions): Promise<DeleteFargateProfileCommandOutput>;
203
91
  deleteFargateProfile(args: DeleteFargateProfileCommandInput, cb: (err: any, data?: DeleteFargateProfileCommandOutput) => void): void;
204
92
  deleteFargateProfile(args: DeleteFargateProfileCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteFargateProfileCommandOutput) => void): void;
205
93
  /**
206
- * @public
207
- * <p>Deletes an Amazon EKS node group for a cluster.</p>
94
+ * @see {@link DeleteNodegroupCommand}
208
95
  */
209
96
  deleteNodegroup(args: DeleteNodegroupCommandInput, options?: __HttpHandlerOptions): Promise<DeleteNodegroupCommandOutput>;
210
97
  deleteNodegroup(args: DeleteNodegroupCommandInput, cb: (err: any, data?: DeleteNodegroupCommandOutput) => void): void;
211
98
  deleteNodegroup(args: DeleteNodegroupCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeleteNodegroupCommandOutput) => void): void;
212
99
  /**
213
- * @public
214
- * <p>Deregisters a connected cluster to remove it from the Amazon EKS control
215
- * plane.</p>
100
+ * @see {@link DeregisterClusterCommand}
216
101
  */
217
102
  deregisterCluster(args: DeregisterClusterCommandInput, options?: __HttpHandlerOptions): Promise<DeregisterClusterCommandOutput>;
218
103
  deregisterCluster(args: DeregisterClusterCommandInput, cb: (err: any, data?: DeregisterClusterCommandOutput) => void): void;
219
104
  deregisterCluster(args: DeregisterClusterCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DeregisterClusterCommandOutput) => void): void;
220
105
  /**
221
- * @public
222
- * <p>Describes an Amazon EKS add-on.</p>
106
+ * @see {@link DescribeAddonCommand}
223
107
  */
224
108
  describeAddon(args: DescribeAddonCommandInput, options?: __HttpHandlerOptions): Promise<DescribeAddonCommandOutput>;
225
109
  describeAddon(args: DescribeAddonCommandInput, cb: (err: any, data?: DescribeAddonCommandOutput) => void): void;
226
110
  describeAddon(args: DescribeAddonCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeAddonCommandOutput) => void): void;
227
111
  /**
228
- * @public
229
- * <p>Returns configuration options.</p>
112
+ * @see {@link DescribeAddonConfigurationCommand}
230
113
  */
231
114
  describeAddonConfiguration(args: DescribeAddonConfigurationCommandInput, options?: __HttpHandlerOptions): Promise<DescribeAddonConfigurationCommandOutput>;
232
115
  describeAddonConfiguration(args: DescribeAddonConfigurationCommandInput, cb: (err: any, data?: DescribeAddonConfigurationCommandOutput) => void): void;
233
116
  describeAddonConfiguration(args: DescribeAddonConfigurationCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeAddonConfigurationCommandOutput) => void): void;
234
117
  /**
235
- * @public
236
- * <p>Describes the versions for an add-on. Information such as the Kubernetes versions that you
237
- * can use the add-on with, the <code>owner</code>, <code>publisher</code>, and the
238
- * <code>type</code> of the add-on are returned. </p>
118
+ * @see {@link DescribeAddonVersionsCommand}
239
119
  */
240
120
  describeAddonVersions(args: DescribeAddonVersionsCommandInput, options?: __HttpHandlerOptions): Promise<DescribeAddonVersionsCommandOutput>;
241
121
  describeAddonVersions(args: DescribeAddonVersionsCommandInput, cb: (err: any, data?: DescribeAddonVersionsCommandOutput) => void): void;
242
122
  describeAddonVersions(args: DescribeAddonVersionsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeAddonVersionsCommandOutput) => void): void;
243
123
  /**
244
- * @public
245
- * <p>Returns descriptive information about an Amazon EKS cluster.</p>
246
- * <p>The API server endpoint and certificate authority data returned by this operation are
247
- * required for <code>kubelet</code> and <code>kubectl</code> to communicate with your
248
- * Kubernetes API server. For more information, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html">Create a
249
- * kubeconfig for Amazon EKS</a>.</p>
250
- * <note>
251
- * <p>The API server endpoint and certificate authority data aren't available until the
252
- * cluster reaches the <code>ACTIVE</code> state.</p>
253
- * </note>
124
+ * @see {@link DescribeClusterCommand}
254
125
  */
255
126
  describeCluster(args: DescribeClusterCommandInput, options?: __HttpHandlerOptions): Promise<DescribeClusterCommandOutput>;
256
127
  describeCluster(args: DescribeClusterCommandInput, cb: (err: any, data?: DescribeClusterCommandOutput) => void): void;
257
128
  describeCluster(args: DescribeClusterCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeClusterCommandOutput) => void): void;
258
129
  /**
259
- * @public
260
- * <p>Returns descriptive information about an Fargate profile.</p>
130
+ * @see {@link DescribeFargateProfileCommand}
261
131
  */
262
132
  describeFargateProfile(args: DescribeFargateProfileCommandInput, options?: __HttpHandlerOptions): Promise<DescribeFargateProfileCommandOutput>;
263
133
  describeFargateProfile(args: DescribeFargateProfileCommandInput, cb: (err: any, data?: DescribeFargateProfileCommandOutput) => void): void;
264
134
  describeFargateProfile(args: DescribeFargateProfileCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeFargateProfileCommandOutput) => void): void;
265
135
  /**
266
- * @public
267
- * <p>Returns descriptive information about an identity provider configuration.</p>
136
+ * @see {@link DescribeIdentityProviderConfigCommand}
268
137
  */
269
138
  describeIdentityProviderConfig(args: DescribeIdentityProviderConfigCommandInput, options?: __HttpHandlerOptions): Promise<DescribeIdentityProviderConfigCommandOutput>;
270
139
  describeIdentityProviderConfig(args: DescribeIdentityProviderConfigCommandInput, cb: (err: any, data?: DescribeIdentityProviderConfigCommandOutput) => void): void;
271
140
  describeIdentityProviderConfig(args: DescribeIdentityProviderConfigCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeIdentityProviderConfigCommandOutput) => void): void;
272
141
  /**
273
- * @public
274
- * <p>Returns descriptive information about an Amazon EKS node group.</p>
142
+ * @see {@link DescribeNodegroupCommand}
275
143
  */
276
144
  describeNodegroup(args: DescribeNodegroupCommandInput, options?: __HttpHandlerOptions): Promise<DescribeNodegroupCommandOutput>;
277
145
  describeNodegroup(args: DescribeNodegroupCommandInput, cb: (err: any, data?: DescribeNodegroupCommandOutput) => void): void;
278
146
  describeNodegroup(args: DescribeNodegroupCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeNodegroupCommandOutput) => void): void;
279
147
  /**
280
- * @public
281
- * <p>Returns descriptive information about an update against your Amazon EKS
282
- * cluster or associated managed node group or Amazon EKS add-on.</p>
283
- * <p>When the status of the update is <code>Succeeded</code>, the update is complete. If an
284
- * update fails, the status is <code>Failed</code>, and an error detail explains the reason
285
- * for the failure.</p>
148
+ * @see {@link DescribeUpdateCommand}
286
149
  */
287
150
  describeUpdate(args: DescribeUpdateCommandInput, options?: __HttpHandlerOptions): Promise<DescribeUpdateCommandOutput>;
288
151
  describeUpdate(args: DescribeUpdateCommandInput, cb: (err: any, data?: DescribeUpdateCommandOutput) => void): void;
289
152
  describeUpdate(args: DescribeUpdateCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DescribeUpdateCommandOutput) => void): void;
290
153
  /**
291
- * @public
292
- * <p>Disassociates an identity provider configuration from a cluster. If you disassociate
293
- * an identity provider from your cluster, users included in the provider can no longer
294
- * access the cluster. However, you can still access the cluster with Amazon Web Services
295
- * IAM users.</p>
154
+ * @see {@link DisassociateIdentityProviderConfigCommand}
296
155
  */
297
156
  disassociateIdentityProviderConfig(args: DisassociateIdentityProviderConfigCommandInput, options?: __HttpHandlerOptions): Promise<DisassociateIdentityProviderConfigCommandOutput>;
298
157
  disassociateIdentityProviderConfig(args: DisassociateIdentityProviderConfigCommandInput, cb: (err: any, data?: DisassociateIdentityProviderConfigCommandOutput) => void): void;
299
158
  disassociateIdentityProviderConfig(args: DisassociateIdentityProviderConfigCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DisassociateIdentityProviderConfigCommandOutput) => void): void;
300
159
  /**
301
- * @public
302
- * <p>Lists the available add-ons.</p>
160
+ * @see {@link ListAddonsCommand}
303
161
  */
304
162
  listAddons(args: ListAddonsCommandInput, options?: __HttpHandlerOptions): Promise<ListAddonsCommandOutput>;
305
163
  listAddons(args: ListAddonsCommandInput, cb: (err: any, data?: ListAddonsCommandOutput) => void): void;
306
164
  listAddons(args: ListAddonsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListAddonsCommandOutput) => void): void;
307
165
  /**
308
- * @public
309
- * <p>Lists the Amazon EKS clusters in your Amazon Web Services account in the
310
- * specified Region.</p>
166
+ * @see {@link ListClustersCommand}
311
167
  */
312
168
  listClusters(args: ListClustersCommandInput, options?: __HttpHandlerOptions): Promise<ListClustersCommandOutput>;
313
169
  listClusters(args: ListClustersCommandInput, cb: (err: any, data?: ListClustersCommandOutput) => void): void;
314
170
  listClusters(args: ListClustersCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListClustersCommandOutput) => void): void;
315
171
  /**
316
- * @public
317
- * <p>Lists the Fargate profiles associated with the specified cluster in
318
- * your Amazon Web Services account in the specified Region.</p>
172
+ * @see {@link ListFargateProfilesCommand}
319
173
  */
320
174
  listFargateProfiles(args: ListFargateProfilesCommandInput, options?: __HttpHandlerOptions): Promise<ListFargateProfilesCommandOutput>;
321
175
  listFargateProfiles(args: ListFargateProfilesCommandInput, cb: (err: any, data?: ListFargateProfilesCommandOutput) => void): void;
322
176
  listFargateProfiles(args: ListFargateProfilesCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListFargateProfilesCommandOutput) => void): void;
323
177
  /**
324
- * @public
325
- * <p>A list of identity provider configurations.</p>
178
+ * @see {@link ListIdentityProviderConfigsCommand}
326
179
  */
327
180
  listIdentityProviderConfigs(args: ListIdentityProviderConfigsCommandInput, options?: __HttpHandlerOptions): Promise<ListIdentityProviderConfigsCommandOutput>;
328
181
  listIdentityProviderConfigs(args: ListIdentityProviderConfigsCommandInput, cb: (err: any, data?: ListIdentityProviderConfigsCommandOutput) => void): void;
329
182
  listIdentityProviderConfigs(args: ListIdentityProviderConfigsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListIdentityProviderConfigsCommandOutput) => void): void;
330
183
  /**
331
- * @public
332
- * <p>Lists the Amazon EKS managed node groups associated with the specified cluster
333
- * in your Amazon Web Services account in the specified Region. Self-managed node groups are
334
- * not listed.</p>
184
+ * @see {@link ListNodegroupsCommand}
335
185
  */
336
186
  listNodegroups(args: ListNodegroupsCommandInput, options?: __HttpHandlerOptions): Promise<ListNodegroupsCommandOutput>;
337
187
  listNodegroups(args: ListNodegroupsCommandInput, cb: (err: any, data?: ListNodegroupsCommandOutput) => void): void;
338
188
  listNodegroups(args: ListNodegroupsCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListNodegroupsCommandOutput) => void): void;
339
189
  /**
340
- * @public
341
- * <p>List the tags for an Amazon EKS resource.</p>
190
+ * @see {@link ListTagsForResourceCommand}
342
191
  */
343
192
  listTagsForResource(args: ListTagsForResourceCommandInput, options?: __HttpHandlerOptions): Promise<ListTagsForResourceCommandOutput>;
344
193
  listTagsForResource(args: ListTagsForResourceCommandInput, cb: (err: any, data?: ListTagsForResourceCommandOutput) => void): void;
345
194
  listTagsForResource(args: ListTagsForResourceCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListTagsForResourceCommandOutput) => void): void;
346
195
  /**
347
- * @public
348
- * <p>Lists the updates associated with an Amazon EKS cluster or managed node group
349
- * in your Amazon Web Services account, in the specified Region.</p>
196
+ * @see {@link ListUpdatesCommand}
350
197
  */
351
198
  listUpdates(args: ListUpdatesCommandInput, options?: __HttpHandlerOptions): Promise<ListUpdatesCommandOutput>;
352
199
  listUpdates(args: ListUpdatesCommandInput, cb: (err: any, data?: ListUpdatesCommandOutput) => void): void;
353
200
  listUpdates(args: ListUpdatesCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListUpdatesCommandOutput) => void): void;
354
201
  /**
355
- * @public
356
- * <p>Connects a Kubernetes cluster to the Amazon EKS control plane. </p>
357
- * <p>Any Kubernetes cluster can be connected to the Amazon EKS control plane to
358
- * view current information about the cluster and its nodes. </p>
359
- * <p>Cluster connection requires two steps. First, send a <code>
360
- * <a>RegisterClusterRequest</a>
361
- * </code> to add it to the Amazon EKS
362
- * control plane.</p>
363
- * <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
364
- * <code>activationCode</code> must be applied to the Kubernetes cluster through it's
365
- * native provider to provide visibility.</p>
366
- * <p>After the Manifest is updated and applied, then the connected cluster is visible to
367
- * the Amazon EKS control plane. If the Manifest is not applied within three days,
368
- * then the connected cluster will no longer be visible and must be deregistered. See <a>DeregisterCluster</a>.</p>
202
+ * @see {@link RegisterClusterCommand}
369
203
  */
370
204
  registerCluster(args: RegisterClusterCommandInput, options?: __HttpHandlerOptions): Promise<RegisterClusterCommandOutput>;
371
205
  registerCluster(args: RegisterClusterCommandInput, cb: (err: any, data?: RegisterClusterCommandOutput) => void): void;
372
206
  registerCluster(args: RegisterClusterCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: RegisterClusterCommandOutput) => void): void;
373
207
  /**
374
- * @public
375
- * <p>Associates the specified tags to a resource with the specified
376
- * <code>resourceArn</code>. If existing tags on a resource are not specified in the
377
- * request parameters, they are not changed. When a resource is deleted, the tags
378
- * 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
379
- * cluster. For example, if you tag a cluster with this operation, that tag does not
380
- * automatically propagate to the subnets and nodes associated with the cluster.</p>
208
+ * @see {@link TagResourceCommand}
381
209
  */
382
210
  tagResource(args: TagResourceCommandInput, options?: __HttpHandlerOptions): Promise<TagResourceCommandOutput>;
383
211
  tagResource(args: TagResourceCommandInput, cb: (err: any, data?: TagResourceCommandOutput) => void): void;
384
212
  tagResource(args: TagResourceCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: TagResourceCommandOutput) => void): void;
385
213
  /**
386
- * @public
387
- * <p>Deletes specified tags from a resource.</p>
214
+ * @see {@link UntagResourceCommand}
388
215
  */
389
216
  untagResource(args: UntagResourceCommandInput, options?: __HttpHandlerOptions): Promise<UntagResourceCommandOutput>;
390
217
  untagResource(args: UntagResourceCommandInput, cb: (err: any, data?: UntagResourceCommandOutput) => void): void;
391
218
  untagResource(args: UntagResourceCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UntagResourceCommandOutput) => void): void;
392
219
  /**
393
- * @public
394
- * <p>Updates an Amazon EKS add-on.</p>
220
+ * @see {@link UpdateAddonCommand}
395
221
  */
396
222
  updateAddon(args: UpdateAddonCommandInput, options?: __HttpHandlerOptions): Promise<UpdateAddonCommandOutput>;
397
223
  updateAddon(args: UpdateAddonCommandInput, cb: (err: any, data?: UpdateAddonCommandOutput) => void): void;
398
224
  updateAddon(args: UpdateAddonCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateAddonCommandOutput) => void): void;
399
225
  /**
400
- * @public
401
- * <p>Updates an Amazon EKS cluster configuration. Your cluster continues to
402
- * function during the update. The response output includes an update ID that you can use
403
- * to track the status of your cluster update with the <a>DescribeUpdate</a> API
404
- * operation.</p>
405
- * <p>You can use this API operation to enable or disable exporting the Kubernetes control
406
- * plane logs for your cluster to CloudWatch Logs. By default, cluster control plane
407
- * 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
408
- * <i>
409
- * <i>Amazon EKS User Guide</i>
410
- * </i>.</p>
411
- * <note>
412
- * <p>CloudWatch Logs ingestion, archive storage, and data scanning rates apply to
413
- * exported control plane logs. For more information, see <a href="http://aws.amazon.com/cloudwatch/pricing/">CloudWatch
414
- * Pricing</a>.</p>
415
- * </note>
416
- * <p>You can also use this API operation to enable or disable public and private access to
417
- * your cluster's Kubernetes API server endpoint. By default, public access is enabled, and
418
- * 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
419
- * <i>
420
- * <i>Amazon EKS User Guide</i>
421
- * </i>. </p>
422
- * <important>
423
- * <p>You can't update the subnets or security group IDs for an existing cluster.</p>
424
- * </important>
425
- * <p>Cluster updates are asynchronous, and they should finish within a few minutes. During
426
- * an update, the cluster status moves to <code>UPDATING</code> (this status transition is
427
- * eventually consistent). When the update is complete (either <code>Failed</code> or
428
- * <code>Successful</code>), the cluster status moves to <code>Active</code>.</p>
226
+ * @see {@link UpdateClusterConfigCommand}
429
227
  */
430
228
  updateClusterConfig(args: UpdateClusterConfigCommandInput, options?: __HttpHandlerOptions): Promise<UpdateClusterConfigCommandOutput>;
431
229
  updateClusterConfig(args: UpdateClusterConfigCommandInput, cb: (err: any, data?: UpdateClusterConfigCommandOutput) => void): void;
432
230
  updateClusterConfig(args: UpdateClusterConfigCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateClusterConfigCommandOutput) => void): void;
433
231
  /**
434
- * @public
435
- * <p>Updates an Amazon EKS cluster to the specified Kubernetes version. Your
436
- * cluster continues to function during the update. The response output includes an update
437
- * ID that you can use to track the status of your cluster update with the <a>DescribeUpdate</a> API operation.</p>
438
- * <p>Cluster updates are asynchronous, and they should finish within a few minutes. During
439
- * an update, the cluster status moves to <code>UPDATING</code> (this status transition is
440
- * eventually consistent). When the update is complete (either <code>Failed</code> or
441
- * <code>Successful</code>), the cluster status moves to <code>Active</code>.</p>
442
- * <p>If your cluster has managed node groups attached to it, all of your node groups’
443
- * Kubernetes versions must match the cluster’s Kubernetes version in order to update the
444
- * cluster to a new Kubernetes version.</p>
232
+ * @see {@link UpdateClusterVersionCommand}
445
233
  */
446
234
  updateClusterVersion(args: UpdateClusterVersionCommandInput, options?: __HttpHandlerOptions): Promise<UpdateClusterVersionCommandOutput>;
447
235
  updateClusterVersion(args: UpdateClusterVersionCommandInput, cb: (err: any, data?: UpdateClusterVersionCommandOutput) => void): void;
448
236
  updateClusterVersion(args: UpdateClusterVersionCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateClusterVersionCommandOutput) => void): void;
449
237
  /**
450
- * @public
451
- * <p>Updates an Amazon EKS managed node group configuration. Your node group
452
- * continues to function during the update. The response output includes an update ID that
453
- * 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
454
- * labels for a node group or the scaling configuration.</p>
238
+ * @see {@link UpdateNodegroupConfigCommand}
455
239
  */
456
240
  updateNodegroupConfig(args: UpdateNodegroupConfigCommandInput, options?: __HttpHandlerOptions): Promise<UpdateNodegroupConfigCommandOutput>;
457
241
  updateNodegroupConfig(args: UpdateNodegroupConfigCommandInput, cb: (err: any, data?: UpdateNodegroupConfigCommandOutput) => void): void;
458
242
  updateNodegroupConfig(args: UpdateNodegroupConfigCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateNodegroupConfigCommandOutput) => void): void;
459
243
  /**
460
- * @public
461
- * <p>Updates the Kubernetes version or AMI version of an Amazon EKS managed node
462
- * group.</p>
463
- * <p>You can update a node group using a launch template only if the node group was
464
- * originally deployed with a launch template. If you need to update a custom AMI in a node
465
- * group that was deployed with a launch template, then update your custom AMI, specify the
466
- * new ID in a new version of the launch template, and then update the node group to the
467
- * new version of the launch template.</p>
468
- * <p>If you update without a launch template, then you can update to the latest available
469
- * AMI version of a node group's current Kubernetes version by not specifying a Kubernetes version in
470
- * the request. You can update to the latest AMI version of your cluster's current Kubernetes
471
- * version by specifying your cluster's Kubernetes version in the request. For information about
472
- * Linux versions, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-linux-ami-versions.html">Amazon EKS optimized Amazon Linux AMI versions</a> in the
473
- * <i>Amazon EKS User Guide</i>. For information about Windows versions, see <a href="https://docs.aws.amazon.com/eks/latest/userguide/eks-ami-versions-windows.html">Amazon EKS optimized Windows AMI versions</a> in the
474
- * <i>Amazon EKS User Guide</i>. </p>
475
- * <p>You cannot roll back a node group to an earlier Kubernetes version or AMI
476
- * version.</p>
477
- * <p>When a node in a managed node group is terminated due to a scaling action or update,
478
- * the pods in that node are drained first. Amazon EKS attempts to drain the nodes
479
- * gracefully and will fail if it is unable to do so. You can <code>force</code> the update
480
- * if Amazon EKS is unable to drain the nodes as a result of a pod disruption
481
- * budget issue.</p>
244
+ * @see {@link UpdateNodegroupVersionCommand}
482
245
  */
483
246
  updateNodegroupVersion(args: UpdateNodegroupVersionCommandInput, options?: __HttpHandlerOptions): Promise<UpdateNodegroupVersionCommandOutput>;
484
247
  updateNodegroupVersion(args: UpdateNodegroupVersionCommandInput, cb: (err: any, data?: UpdateNodegroupVersionCommandOutput) => void): void;
485
248
  updateNodegroupVersion(args: UpdateNodegroupVersionCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateNodegroupVersionCommandOutput) => void): void;
486
249
  }
250
+ /**
251
+ * @public
252
+ * <p>Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that makes it easy
253
+ * for you to run Kubernetes on Amazon Web Services without needing to stand up or maintain
254
+ * your own Kubernetes control plane. Kubernetes is an open-source system for automating
255
+ * the deployment, scaling, and management of containerized applications. </p>
256
+ * <p>Amazon EKS runs up-to-date versions of the open-source Kubernetes software, so
257
+ * you can use all the existing plugins and tooling from the Kubernetes community.
258
+ * Applications running on Amazon EKS are fully compatible with applications
259
+ * running on any standard Kubernetes environment, whether running in on-premises data
260
+ * centers or public clouds. This means that you can easily migrate any standard Kubernetes
261
+ * application to Amazon EKS without any code modification required.</p>
262
+ */
263
+ export declare class EKS extends EKSClient implements EKS {
264
+ }
@@ -140,7 +140,7 @@ import {
140
140
  UpdateNodegroupVersionCommandOutput,
141
141
  } from "./commands/UpdateNodegroupVersionCommand";
142
142
  import { EKSClient } from "./EKSClient";
143
- export declare class EKS extends EKSClient {
143
+ export interface EKS {
144
144
  associateEncryptionConfig(
145
145
  args: AssociateEncryptionConfigCommandInput,
146
146
  options?: __HttpHandlerOptions
@@ -603,3 +603,4 @@ export declare class EKS extends EKSClient {
603
603
  cb: (err: any, data?: UpdateNodegroupVersionCommandOutput) => void
604
604
  ): void;
605
605
  }
606
+ export declare class EKS extends EKSClient implements EKS {}
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@aws-sdk/client-eks",
3
3
  "description": "AWS SDK for JavaScript Eks Client for Node.js, Browser and React Native",
4
- "version": "3.312.0",
4
+ "version": "3.316.0",
5
5
  "scripts": {
6
6
  "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
7
7
  "build:cjs": "tsc -p tsconfig.cjs.json",
@@ -21,9 +21,9 @@
21
21
  "dependencies": {
22
22
  "@aws-crypto/sha256-browser": "3.0.0",
23
23
  "@aws-crypto/sha256-js": "3.0.0",
24
- "@aws-sdk/client-sts": "3.312.0",
24
+ "@aws-sdk/client-sts": "3.316.0",
25
25
  "@aws-sdk/config-resolver": "3.310.0",
26
- "@aws-sdk/credential-provider-node": "3.310.0",
26
+ "@aws-sdk/credential-provider-node": "3.316.0",
27
27
  "@aws-sdk/fetch-http-handler": "3.310.0",
28
28
  "@aws-sdk/hash-node": "3.310.0",
29
29
  "@aws-sdk/invalid-dependency": "3.310.0",
@@ -40,14 +40,14 @@
40
40
  "@aws-sdk/node-config-provider": "3.310.0",
41
41
  "@aws-sdk/node-http-handler": "3.310.0",
42
42
  "@aws-sdk/protocol-http": "3.310.0",
43
- "@aws-sdk/smithy-client": "3.310.0",
43
+ "@aws-sdk/smithy-client": "3.316.0",
44
44
  "@aws-sdk/types": "3.310.0",
45
45
  "@aws-sdk/url-parser": "3.310.0",
46
46
  "@aws-sdk/util-base64": "3.310.0",
47
47
  "@aws-sdk/util-body-length-browser": "3.310.0",
48
48
  "@aws-sdk/util-body-length-node": "3.310.0",
49
- "@aws-sdk/util-defaults-mode-browser": "3.310.0",
50
- "@aws-sdk/util-defaults-mode-node": "3.310.0",
49
+ "@aws-sdk/util-defaults-mode-browser": "3.316.0",
50
+ "@aws-sdk/util-defaults-mode-node": "3.316.0",
51
51
  "@aws-sdk/util-endpoints": "3.310.0",
52
52
  "@aws-sdk/util-retry": "3.310.0",
53
53
  "@aws-sdk/util-user-agent-browser": "3.310.0",