Struct rusoto_eks::EksClient

pub struct EksClient { /* fields omitted */ }

A client for the Amazon EKS API.

Implementations

impl EksClient

pub fn new(region: Region) -> EksClient

Creates a client backed by the default tokio event loop.

The client will use the default credentials provider and tls client.

pub fn new_with<P, D>(
    request_dispatcher: D,
    credentials_provider: P,
    region: Region
) -> EksClient where
    P: ProvideAwsCredentials + Send + Sync + 'static,
    D: DispatchSignedRequest + Send + Sync + 'static, 

pub fn new_with_client(client: Client, region: Region) -> EksClient

Trait Implementations

impl Clone for EksClient

pub fn clone(&self) -> EksClient

Returns a copy of the value.

pub fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Eks for EksClient

pub fn create_cluster<'life0, 'async_trait>(
    &'life0 self,
    input: CreateClusterRequest
) -> Pin<Box<dyn Future<Output = Result<CreateClusterResponse, RusotoError<CreateClusterError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Creates an Amazon EKS control plane.

The Amazon EKS control plane consists of control plane instances that run the Kubernetes software, such as etcd and the API server. The control plane runs in an account managed by AWS, 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 own set of Amazon EC2 instances.

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 worker nodes (for example, to support kubectl exec, logs, and proxy data flows).

Amazon EKS worker nodes run in your AWS account and connect to your cluster's control plane via the Kubernetes API server endpoint and a certificate file that is created for your cluster.

You can use the endpointPublicAccess and endpointPrivateAccess parameters 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 Amazon EKS Cluster Endpoint Access Control in the Amazon EKS User Guide .

You can use the logging parameter 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 Amazon EKS Cluster Control Plane Logs in the Amazon EKS User Guide .

CloudWatch Logs ingestion, archive storage, and data scanning rates apply to exported control plane logs. For more information, see Amazon CloudWatch Pricing.

Cluster creation typically takes between 10 and 15 minutes. After you create an Amazon EKS cluster, you must configure your Kubernetes tooling to communicate with the API server and launch worker nodes into your cluster. For more information, see Managing Cluster Authentication and Launching Amazon EKS Worker Nodes in the Amazon EKS User Guide.

pub fn create_fargate_profile<'life0, 'async_trait>(
    &'life0 self,
    input: CreateFargateProfileRequest
) -> Pin<Box<dyn Future<Output = Result<CreateFargateProfileResponse, RusotoError<CreateFargateProfileError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Creates an AWS 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.

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.

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 Role Based Access Control (RBAC) for authorization so that the kubelet 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 Pod Execution Role in the Amazon EKS User Guide.

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.

If any Fargate profiles in a cluster are in the DELETING status, you must wait for that Fargate profile to finish deleting before you can create any other profiles in that cluster.

For more information, see AWS Fargate Profile in the Amazon EKS User Guide.

pub fn create_nodegroup<'life0, 'async_trait>(
    &'life0 self,
    input: CreateNodegroupRequest
) -> Pin<Box<dyn Future<Output = Result<CreateNodegroupResponse, RusotoError<CreateNodegroupError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Creates a managed worker 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.

An Amazon EKS managed node group is an Amazon EC2 Auto Scaling group and associated Amazon EC2 instances that are managed by AWS for an Amazon EKS cluster. Each node group uses a version of the Amazon EKS-optimized Amazon Linux 2 AMI. For more information, see Managed Node Groups in the Amazon EKS User Guide.

pub fn delete_cluster<'life0, 'async_trait>(
    &'life0 self,
    input: DeleteClusterRequest
) -> Pin<Box<dyn Future<Output = Result<DeleteClusterResponse, RusotoError<DeleteClusterError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Deletes the Amazon EKS cluster control plane.

If you have active services in your cluster that are associated with a load balancer, you must delete those services before deleting the cluster so that the load balancers 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 Deleting a Cluster in the Amazon EKS User Guide.

If you have managed node groups or Fargate profiles attached to the cluster, you must delete them first. For more information, see DeleteNodegroup and DeleteFargateProfile.

pub fn delete_fargate_profile<'life0, 'async_trait>(
    &'life0 self,
    input: DeleteFargateProfileRequest
) -> Pin<Box<dyn Future<Output = Result<DeleteFargateProfileResponse, RusotoError<DeleteFargateProfileError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Deletes an AWS Fargate profile.

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.

Only one Fargate profile in a cluster can be in the DELETING status at a time. You must wait for a Fargate profile to finish deleting before you can delete any other profiles in that cluster.

pub fn delete_nodegroup<'life0, 'async_trait>(
    &'life0 self,
    input: DeleteNodegroupRequest
) -> Pin<Box<dyn Future<Output = Result<DeleteNodegroupResponse, RusotoError<DeleteNodegroupError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Deletes an Amazon EKS node group for a cluster.

pub fn describe_cluster<'life0, 'async_trait>(
    &'life0 self,
    input: DescribeClusterRequest
) -> Pin<Box<dyn Future<Output = Result<DescribeClusterResponse, RusotoError<DescribeClusterError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Returns descriptive information about an Amazon EKS cluster.

The API server endpoint and certificate authority data returned by this operation are required for kubelet and kubectl to communicate with your Kubernetes API server. For more information, see Create a kubeconfig for Amazon EKS.

The API server endpoint and certificate authority data aren't available until the cluster reaches the ACTIVE state.

pub fn describe_fargate_profile<'life0, 'async_trait>(
    &'life0 self,
    input: DescribeFargateProfileRequest
) -> Pin<Box<dyn Future<Output = Result<DescribeFargateProfileResponse, RusotoError<DescribeFargateProfileError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Returns descriptive information about an AWS Fargate profile.

pub fn describe_nodegroup<'life0, 'async_trait>(
    &'life0 self,
    input: DescribeNodegroupRequest
) -> Pin<Box<dyn Future<Output = Result<DescribeNodegroupResponse, RusotoError<DescribeNodegroupError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Returns descriptive information about an Amazon EKS node group.

pub fn describe_update<'life0, 'async_trait>(
    &'life0 self,
    input: DescribeUpdateRequest
) -> Pin<Box<dyn Future<Output = Result<DescribeUpdateResponse, RusotoError<DescribeUpdateError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Returns descriptive information about an update against your Amazon EKS cluster or associated managed node group.

When the status of the update is Succeeded, the update is complete. If an update fails, the status is Failed, and an error detail explains the reason for the failure.

pub fn list_clusters<'life0, 'async_trait>(
    &'life0 self,
    input: ListClustersRequest
) -> Pin<Box<dyn Future<Output = Result<ListClustersResponse, RusotoError<ListClustersError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Lists the Amazon EKS clusters in your AWS account in the specified Region.

pub fn list_fargate_profiles<'life0, 'async_trait>(
    &'life0 self,
    input: ListFargateProfilesRequest
) -> Pin<Box<dyn Future<Output = Result<ListFargateProfilesResponse, RusotoError<ListFargateProfilesError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Lists the AWS Fargate profiles associated with the specified cluster in your AWS account in the specified Region.

pub fn list_nodegroups<'life0, 'async_trait>(
    &'life0 self,
    input: ListNodegroupsRequest
) -> Pin<Box<dyn Future<Output = Result<ListNodegroupsResponse, RusotoError<ListNodegroupsError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Lists the Amazon EKS managed node groups associated with the specified cluster in your AWS account in the specified Region. Self-managed node groups are not listed.

pub fn list_tags_for_resource<'life0, 'async_trait>(
    &'life0 self,
    input: ListTagsForResourceRequest
) -> Pin<Box<dyn Future<Output = Result<ListTagsForResourceResponse, RusotoError<ListTagsForResourceError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

List the tags for an Amazon EKS resource.

pub fn list_updates<'life0, 'async_trait>(
    &'life0 self,
    input: ListUpdatesRequest
) -> Pin<Box<dyn Future<Output = Result<ListUpdatesResponse, RusotoError<ListUpdatesError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Lists the updates associated with an Amazon EKS cluster or managed node group in your AWS account, in the specified Region.

pub fn tag_resource<'life0, 'async_trait>(
    &'life0 self,
    input: TagResourceRequest
) -> Pin<Box<dyn Future<Output = Result<TagResourceResponse, RusotoError<TagResourceError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Associates the specified tags to a resource with the specified resourceArn. 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 worker nodes associated with the cluster.

pub fn untag_resource<'life0, 'async_trait>(
    &'life0 self,
    input: UntagResourceRequest
) -> Pin<Box<dyn Future<Output = Result<UntagResourceResponse, RusotoError<UntagResourceError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Deletes specified tags from a resource.

pub fn update_cluster_config<'life0, 'async_trait>(
    &'life0 self,
    input: UpdateClusterConfigRequest
) -> Pin<Box<dyn Future<Output = Result<UpdateClusterConfigResponse, RusotoError<UpdateClusterConfigError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

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 DescribeUpdate API operation.

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 Amazon EKS Cluster Control Plane Logs in the Amazon EKS User Guide .

CloudWatch Logs ingestion, archive storage, and data scanning rates apply to exported control plane logs. For more information, see Amazon CloudWatch Pricing.

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 Amazon EKS Cluster Endpoint Access Control in the Amazon EKS User Guide .

At this time, you can not update the subnets or security group IDs for an existing cluster.

Cluster updates are asynchronous, and they should finish within a few minutes. During an update, the cluster status moves to UPDATING (this status transition is eventually consistent). When the update is complete (either Failed or Successful), the cluster status moves to Active.

pub fn update_cluster_version<'life0, 'async_trait>(
    &'life0 self,
    input: UpdateClusterVersionRequest
) -> Pin<Box<dyn Future<Output = Result<UpdateClusterVersionResponse, RusotoError<UpdateClusterVersionError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

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 DescribeUpdate API operation.

Cluster updates are asynchronous, and they should finish within a few minutes. During an update, the cluster status moves to UPDATING (this status transition is eventually consistent). When the update is complete (either Failed or Successful), the cluster status moves to Active.

If your cluster has managed node groups attached to it, all of your node groups’ Kubernetes versions must match the cluster’s Kubernetes version in order to update the cluster to a new Kubernetes version.

pub fn update_nodegroup_config<'life0, 'async_trait>(
    &'life0 self,
    input: UpdateNodegroupConfigRequest
) -> Pin<Box<dyn Future<Output = Result<UpdateNodegroupConfigResponse, RusotoError<UpdateNodegroupConfigError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

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 DescribeUpdate API operation. Currently you can update the Kubernetes labels for a node group or the scaling configuration.

pub fn update_nodegroup_version<'life0, 'async_trait>(
    &'life0 self,
    input: UpdateNodegroupVersionRequest
) -> Pin<Box<dyn Future<Output = Result<UpdateNodegroupVersionResponse, RusotoError<UpdateNodegroupVersionError>>> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Updates the Kubernetes version or AMI version of an Amazon EKS managed node group.

You can update to the latest available 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 Amazon EKS-Optimized Linux AMI Versions in the Amazon EKS User Guide.

You cannot roll back a node group to an earlier Kubernetes version or AMI version.

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 force the update if Amazon EKS is unable to drain the nodes as a result of a pod disruption budget issue.