Managing Amazon EKS add-ons
Amazon EKS add-ons are a curated set of add-on software for Amazon EKS clusters. All Amazon EKS add-ons:
-
include the latest security patches and bug fixes.
-
are validated by Amazon to work with Amazon EKS.
-
reduce the amount of work required to manage the add-on software.
The Amazon Web Services Management Console notifies you when a new version is available for an Amazon EKS add-on. You can simply initiate the update, and Amazon EKS updates the add-on software for you.
For a list of available add-ons, see Available Amazon EKS add-ons from Amazon EKS. For more information about Kubernetes field management, see Kubernetes field management
Prerequisites
-
An existing Amazon EKS cluster. To deploy one, see Getting started with Amazon EKS.
-
If you're creating an add-on that uses a Kubernetes service account and IAM role, then you need to have an Amazon Identity and Access Management (IAM) OpenID Connect (OIDC) provider for your cluster. To determine whether you have one for your cluster, or to create one, see Creating an IAM OIDC provider for your cluster.
Creating an add-on
You can create an Amazon EKS add-on using eksctl
, the Amazon Web Services Management Console, or the Amazon CLI. If the
add-on requires an IAM role, see the details for the specific add-on in Available Amazon EKS add-ons from
Amazon EKS for details about creating the
role.
- eksctl
-
Prerequisite
Version
0.159.0
or later of theeksctl
command line tool installed on your device or Amazon CloudShell. To install or updateeksctl
, see Installing or updating eksctl.To create an Amazon EKS add-on using
eksctl
-
View the names of add-ons available for a cluster version. Replace
with the version of your cluster.1.28
eksctl utils describe-addon-versions --kubernetes-version
1.28
| grep AddonNameAn example output is as follows.
"AddonName": "aws-ebs-csi-driver", "AddonName": "coredns", "AddonName": "kube-proxy", "AddonName": "vpc-cni", "AddonName": "adot", "AddonName": "dynatrace_dynatrace-operator", "AddonName": "upbound_universal-crossplane", "AddonName": "teleport_teleport", "AddonName": "factorhouse_kpow", [...]
-
View the versions available for the add-on that you would like to create. Replace
with the version of your cluster. Replace1.28
with the name of the add-on you want to view the versions for. The name must be one of the names returned in the previous steps.name-of-addon
eksctl utils describe-addon-versions --kubernetes-version
1.28
--namename-of-addon
| grep AddonVersionThe following output is an example of what is returned for the add-on named
vpc-cni
. You can see that the add-on has several available versions."AddonVersions": [ "AddonVersion": "v1.12.0-eksbuild.1", "AddonVersion": "v1.11.4-eksbuild.1", "AddonVersion": "v1.10.4-eksbuild.1", "AddonVersion": "v1.9.3-eksbuild.1",
-
Create an Amazon EKS add-on. Copy the command that follows to your device. Make the following modifications to the command as needed and then run the modified command:
-
Replace
with the name of your cluster.my-cluster
-
Replace
with the name of the add-on that you want to create.name-of-addon
-
If you want a version of the add-on that's earlier than the latest version, then replace
with the version number returned in the output of a previous step that you want to use.latest
-
If the add-on uses a service account role, replace
with your account ID and replace111122223333
with the name of the role. For instructions on creating a role for your service account, see the documentation for the add-on that you're creating. Specifying a service account role requires that you have an IAM OpenID Connect (OIDC) provider for your cluster. To determine whether you have one for your cluster, or to create one, see Creating an IAM OIDC provider for your cluster.role-name
If the add-on doesn't use a service account role, delete
.
arn:aws-cn:iam::--service-account-role-arn
111122223333
:role/
role-name
-
This example command overwrites the configuration of any existing self-managed version of the add-on, if there is one. If you don't want to overwrite the configuration of an existing self-managed add-on, remove the
option. If you remove the option, and the Amazon EKS add-on needs to overwrite the configuration of an existing self-managed add-on, then creation of the Amazon EKS add-on fails with an error message to help you resolve the conflict. Before specifying this option, make sure that the Amazon EKS add-on doesn't manage settings that you need to manage, because those settings are overwritten with this option.--force
eksctl create addon --cluster
my-cluster
--namename-of-addon
--versionlatest
\--service-account-role-arn
arn:aws-cn:iam::111122223333
:role/role-name
--force
-
You can see a list of all available options for the command.
eksctl create addon --help
For more information about available options see Addons
in the eksctl
documentation. -
- Amazon Web Services Management Console
-
To create an Amazon EKS add-on using the Amazon Web Services Management Console
Open the Amazon EKS console at https://console.amazonaws.cn/eks/home#/clusters
. -
In the left navigation pane, select Clusters, and then select the name of the cluster that you want to create the add-on for.
-
Choose the Add-ons tab.
-
Select Get more add-ons.
-
Choose the add-ons that you want to add to your cluster. You can add as many add-ons as you require. Once you've selected the add-ons that you want to install, choose Next.
-
On the Configure selected add-ons settings page:
-
For Version, select the version that you want to install. We recommend the version marked latest, unless the individual add-on that you're creating recommends a different version. To determine whether an add-on has a recommended version, see the documentation for the add-on that you're creating.
-
-
On the Review and add page, choose Create. After the add-on installation is complete, you see your installed add-ons.
- Amazon CLI
-
Prerequisite
Version
2.12.3
or later or1.27.160
or later of the Amazon CLI installed and configured on your device or Amazon CloudShell. You can check your current version withaws --version | cut -d / -f2 | cut -d ' ' -f1
. Package managers suchyum
,apt-get
, or Homebrew for macOS are often several versions behind the latest version of the Amazon CLI. To install the latest version, see Installing, updating, and uninstalling the Amazon CLI and Quick configuration withaws configure
in the Amazon Command Line Interface User Guide. The Amazon CLI version installed in the Amazon CloudShell may also be several versions behind the latest version. To update it, see Installing Amazon CLI to your home directory in the Amazon CloudShell User Guide.To create an Amazon EKS add-on using the Amazon CLI
-
Determine which add-ons are available. You can see all available add-ons, their type, and their publisher. Replace
with the version of your cluster.1.28
aws eks describe-addon-versions --kubernetes-version 1.28 \ --query 'addons[].{Name: addonName, Type: type}' --output table
An example output is as follows.
------------------------------------------------------- | DescribeAddonVersions | +-------------------------------+---------------------+ | Name | Type | +-------------------------------+---------------------+ | aws-ebs-csi-driver | storage | | coredns | networking | | kube-proxy | networking | | vpc-cni | networking | | adot | observability | | [...] | [...] | +-------------------------------+---------------------+
Your output might be different. In this example output, there are three different add-ons available of type
networking
and five add-ons with a publisher of typeeks
. -
You can see which versions are available for each add-on. Replace
with the version of your cluster and replace1.28
with the name of an add-on returned in the previous step.vpc-cni
aws eks describe-addon-versions --kubernetes-version
--addon-name1.28
vpc-cni
\ --query 'addons[].addonVersions[].{Version: addonVersion, Defaultversion: compatibilities[0].defaultVersion}' --output tableAn example output is as follows.
------------------------------------------ | DescribeAddonVersions | +-----------------+----------------------+ | Defaultversion | Version | +-----------------+----------------------+ | False | v1.12.0-eksbuild.1 | | True | v1.11.4-eksbuild.1 | | False | v1.10.4-eksbuild.1 | | False | v1.9.3-eksbuild.1 | +-----------------+----------------------+
The version with
True
in theDefaultversion
column is the version that the add-on is created with, by default. -
(Optional) Find the configuration options for your chosen add-on by running the following command:
aws eks describe-addon-configuration --addon-name
vpc-cni
--addon-versionv1.12.0-eksbuild.1
{ "addonName": "vpc-cni", "addonVersion": "
v1.12.0-eksbuild.1
", "configurationSchema": "{\"$ref\":\"#/definitions/VpcCni\",\"$schema\":\"http://json-schema.org/draft-06/schema#\",\"definitions\":{\"Cri\":{\"additionalProperties\":false,\"properties\":{\"hostPath\":{\"$ref\":\"#/definitions/HostPath\"}},\"title\":\"Cri\",\"type\":\"object\"},\"Env\":{\"additionalProperties\":false,\"properties\":{\"ADDITIONAL_ENI_TAGS\":{\"type\":\"string\"},\"AWS_VPC_CNI_NODE_PORT_SUPPORT\":{\"format\":\"boolean\",\"type\":\"string\"},\"AWS_VPC_ENI_MTU\":{\"format\":\"integer\",\"type\":\"string\"},\"AWS_VPC_K8S_CNI_CONFIGURE_RPFILTER\":{\"format\":\"boolean\",\"type\":\"string\"},\"AWS_VPC_K8S_CNI_CUSTOM_NETWORK_CFG\":{\"format\":\"boolean\",\"type\":\"string\"},\"AWS_VPC_K8S_CNI_EXTERNALSNAT\":{\"format\":\"boolean\",\"type\":\"string\"},\"AWS_VPC_K8S_CNI_LOGLEVEL\":{\"type\":\"string\"},\"AWS_VPC_K8S_CNI_LOG_FILE\":{\"type\":\"string\"},\"AWS_VPC_K8S_CNI_RANDOMIZESNAT\":{\"type\":\"string\"},\"AWS_VPC_K8S_CNI_VETHPREFIX\":{\"type\":\"string\"},\"AWS_VPC_K8S_PLUGIN_LOG_FILE\":{\"type\":\"string\"},\"AWS_VPC_K8S_PLUGIN_LOG_LEVEL\":{\"type\":\"string\"},\"DISABLE_INTROSPECTION\":{\"format\":\"boolean\",\"type\":\"string\"},\"DISABLE_METRICS\":{\"format\":\"boolean\",\"type\":\"string\"},\"DISABLE_NETWORK_RESOURCE_PROVISIONING\":{\"format\":\"boolean\",\"type\":\"string\"},\"ENABLE_POD_ENI\":{\"format\":\"boolean\",\"type\":\"string\"},\"ENABLE_PREFIX_DELEGATION\":{\"format\":\"boolean\",\"type\":\"string\"},\"WARM_ENI_TARGET\":{\"format\":\"integer\",\"type\":\"string\"},\"WARM_PREFIX_TARGET\":{\"format\":\"integer\",\"type\":\"string\"}},\"title\":\"Env\",\"type\":\"object\"},\"HostPath\":{\"additionalProperties\":false,\"properties\":{\"path\":{\"type\":\"string\"}},\"title\":\"HostPath\",\"type\":\"object\"},\"Limits\":{\"additionalProperties\":false,\"properties\":{\"cpu\":{\"type\":\"string\"},\"memory\":{\"type\":\"string\"}},\"title\":\"Limits\",\"type\":\"object\"},\"Resources\":{\"additionalProperties\":false,\"properties\":{\"limits\":{\"$ref\":\"#/definitions/Limits\"},\"requests\":{\"$ref\":\"#/definitions/Limits\"}},\"title\":\"Resources\",\"type\":\"object\"},\"VpcCni\":{\"additionalProperties\":false,\"properties\":{\"cri\":{\"$ref\":\"#/definitions/Cri\"},\"env\":{\"$ref\":\"#/definitions/Env\"},\"resources\":{\"$ref\":\"#/definitions/Resources\"}},\"title\":\"VpcCni\",\"type\":\"object\"}}}
" }The output is a standard JSON schema.
Here is an example of valid configuration values, in JSON format, that works with the schema above.
{ "resources": { "limits": { "cpu": "100m" } } }
Here is an example of valid configuration values, in YAML format, that works with the schema above.
resources: limits: cpu: 100m
-
Create an Amazon EKS add-on. Copy the command that follows to your device. Make the following modifications to the command as needed and then run the modified command:
-
Replace
with the name of your cluster.my-cluster
-
Replace
with an add-on name returned in the output of the previous step that you want to create.vpc-cni
-
Replace
with the version returned in the output of the previous step that you want to use.version-number
-
If the add-on uses a Kubernetes service account and IAM role, replace
with your account ID and111122223333
with the name of an existing IAM role that you've created. For instructions on creating the role, see the documentation for the add-on that you're creating. Specifying a service account role requires that you have an IAM OpenID Connect (OIDC) provider for your cluster. To determine whether you have one for your cluster, or to create one, see Creating an IAM OIDC provider for your cluster.role-name
If the add-on doesn't use a Kubernetes service account and IAM role, delete
.--service-account-role-arn arn:aws-cn:iam::
111122223333
:role/
role-name
-
These example commands overwrites the
--configuration-values
option of any existing self-managed version of the add-on, if there is one. Replace this with the desired configuration values, such as a string or a file input. If you don't want to provide configuration values, then delete the--configuration-values
option. If you don't want the Amazon CLI to overwrite the configuration of an existing self-managed add-on, remove the
option. If you remove the option, and the Amazon EKS add-on needs to overwrite the configuration of an existing self-managed add-on, then creation of the Amazon EKS add-on fails with an error message to help you resolve the conflict. Before specifying this option, make sure that the Amazon EKS add-on doesn't manage settings that you need to manage, because those settings are overwritten with this option.--resolve-conflicts OVERWRITE
aws eks create-addon --cluster-name
my-cluster
--addon-namevpc-cni
--addon-versionversion-number
\ --service-account-role-arn arn:aws-cn:iam::111122223333
:role/role-name --configuration-values '{"resources":{"limits":{"cpu":"100m"}}
}' --resolve-conflictsOVERWRITE
aws eks create-addon --cluster-name
my-cluster
--addon-namevpc-cni
--addon-versionversion-number
\ --service-account-role-arn arn:aws-cn:iam::111122223333
:role/role-name --configuration-values 'file://example
.yaml' --resolve-conflictsOVERWRITE
For a full list of available options, see
create-addon
in the Amazon EKS Command Line Reference. -
-
Updating an add-on
Amazon EKS doesn't automatically update an add-on when new versions are released or after you update your cluster to a new Kubernetes minor version. To update an add-on for an existing cluster, you must initiate the update. After you initiate the update, Amazon EKS updates the add-on for you. Before updating an add-on, review the current documentation for the add-on. For a list of available add-ons, see Available Amazon EKS add-ons from Amazon EKS. If the add-on requires an IAM role, see the details for the specific add-on in Available Amazon EKS add-ons from Amazon EKS for details about creating the role.
You can update an Amazon EKS add-on using eksctl
, the Amazon Web Services Management Console, or the Amazon CLI.
- eksctl
-
Prerequisite
Version
0.159.0
or later of theeksctl
command line tool installed on your device or Amazon CloudShell. To install or updateeksctl
, see Installing or updating eksctl.To update an Amazon EKS add-on using
eksctl
-
Determine the current add-ons and add-on versions installed on your cluster. Replace
with the name of your cluster.my-cluster
eksctl get addon --cluster
my-cluster
An example output is as follows.
NAME VERSION STATUS ISSUES IAMROLE UPDATE AVAILABLE coredns v1.8.7-eksbuild.2 ACTIVE 0 kube-proxy v1.23.7-eksbuild.1 ACTIVE 0 v1.23.8-eksbuild.2 vpc-cni v1.10.4-eksbuild.1 ACTIVE 0 v1.12.0-eksbuild.1,v1.11.4-eksbuild.1,v1.11.3-eksbuild.1,v1.11.2-eksbuild.1,v1.11.0-eksbuild.1
Your output might look different, depending on which add-ons and versions that you have on your cluster. You can see that in the previous example output, two existing add-ons on the cluster have newer versions available in the
UPDATE AVAILABLE
column. -
Update the add-on.
-
Copy the command that follows to your device. Make the following modifications to the command as needed:
-
Replace
with the name of your cluster.my-cluster
-
Replace
with the Amazon Web Services Region that your cluster is in.region
-
Replace
with the name of an add-on returned in the output of the previous step that you want to update.vpc-cni
-
If you want to update to a version earlier than the latest available version, then replace
with the version number returned in the output of the previous step that you want to use. Some add-ons have recommended versions. For more information, see the documentation for the add-on that you're updating.latest
-
If the add-on uses a Kubernetes service account and IAM role, replace
with your account ID and111122223333
with the name of an existing IAM role that you've created. For instructions on creating the role, see the documentation for the add-on that you're creating. Specifying a service account role requires that you have an IAM OpenID Connect (OIDC) provider for your cluster. To determine whether you have one for your cluster, or to create one, see Creating an IAM OIDC provider for your cluster.role-name
If the add-on doesn't use a Kubernetes service account and IAM role, delete the
serviceAccountRoleARN: arn:aws-cn:iam::
line.111122223333
:role/role-name
-
The
preserve
option preserves existing values for the add-on. If you have set custom values for add-on settings, and you don't use this option, Amazon EKS overwrites your values with its default values. If you use this option, then we recommend that you test any field and value changes on a non-production cluster before updating the add-on on your production cluster. If you change this value tooverwrite
, all settings are changed to Amazon EKS default values. If you've set custom values for any settings, they might be overwritten with Amazon EKS default values. If you change this value tonone
, Amazon EKS doesn't change the value of any settings, but the update might fail. If the update fails, you receive an error message to help you resolve the conflict.cat >update-addon.yaml <<EOF apiVersion: eksctl.io/v1alpha5 kind: ClusterConfig metadata: name:
my-cluster
region:region
addons: - name:vpc-cni
version:latest
serviceAccountRoleARN: arn:aws-cn:iam::111122223333
:role/role-name
resolveConflicts:preserve
EOF
-
-
Run the modified command to create the
update-addon.yaml
file. -
Apply the config file to your cluster.
eksctl update addon -f update-addon.yaml
For more information about updating add-ons, see Addons
in the eksctl
documentation. -
-
- Amazon Web Services Management Console
-
To update an Amazon EKS add-on using the Amazon Web Services Management Console
Open the Amazon EKS console at https://console.amazonaws.cn/eks/home#/clusters
. -
In the left navigation pane, select Clusters, and then select the name of the cluster that you want to configure the add-on for.
-
Choose the Add-ons tab.
-
Select the box in the top right of the add-on box and then choose Edit.
-
On the Configure
name of addon
page:-
Select the Version that you'd like to use. The add-on might have a recommended version. For more information, see the documentation for the add-on that you're updating.
-
For Select IAM role, you can select Inherit from node or an existing role that you created for use with the add-on. If there's no role to select, then you don't have an existing role. Regardless of which option your choose, see the documentation for the add-on that you're creating to create an IAM policy and attach it to a role. Selecting an IAM role requires that you have an IAM OpenID Connect (OIDC) provider for your cluster. To determine whether you have one for your cluster, or to create one, see Creating an IAM OIDC provider for your cluster.
-
For
Code editor
, enter any add-on specific configuration information. For more information, see the documentation for the add-on that you're updating. -
For Conflict resolution method, select one of the options. If you have set custom values for add-on settings, we recommend the Preserve option. If you don't choose this option, Amazon EKS overwrites your values with its default values. If you use this option, then we recommend that you test any field and value changes on a non-production cluster before updating the add-on on your production cluster.
-
-
Choose Update.
- Amazon CLI
-
Prerequisite
Version
2.12.3
or later or1.27.160
or later of the Amazon CLI installed and configured on your device or Amazon CloudShell. You can check your current version withaws --version | cut -d / -f2 | cut -d ' ' -f1
. Package managers suchyum
,apt-get
, or Homebrew for macOS are often several versions behind the latest version of the Amazon CLI. To install the latest version, see Installing, updating, and uninstalling the Amazon CLI and Quick configuration withaws configure
in the Amazon Command Line Interface User Guide. The Amazon CLI version installed in the Amazon CloudShell may also be several versions behind the latest version. To update it, see Installing Amazon CLI to your home directory in the Amazon CloudShell User Guide.To update an Amazon EKS add-on using the Amazon CLI
-
See a list of installed add-ons. Replace
with the name of your cluster.my-cluster
aws eks list-addons --cluster-name
my-cluster
An example output is as follows.
{ "addons": [ "coredns", "kube-proxy", "vpc-cni" ] }
-
View the current version of the add-on that you want to update. Replace
with your cluster name andmy-cluster
with the name of the add-on that you want to update.vpc-cni
aws eks describe-addon --cluster-name
my-cluster
--addon-namevpc-cni
--query "addon.addonVersion" --output textAn example output is as follows.
v1.10.4-eksbuild.1
-
You can see which versions of the add-on are available for your cluster's version. Replace
with your cluster's version and1.28
with the name of the add-on that you want to update.vpc-cni
aws eks describe-addon-versions --kubernetes-version
--addon-name1.28
vpc-cni
\ --query 'addons[].addonVersions[].{Version: addonVersion, Defaultversion: compatibilities[0].defaultVersion}' --output tableAn example output is as follows.
------------------------------------------ | DescribeAddonVersions | +-----------------+----------------------+ | Defaultversion | Version | +-----------------+----------------------+ | False | v1.12.0-eksbuild.1 | | True | v1.11.4-eksbuild.1 | | False | v1.10.4-eksbuild.1 | | False | v1.9.3-eksbuild.1 | +-----------------+----------------------+
The version with
True
in theDefaultversion
column is the version that the add-on is created with, by default. -
Update your add-on. Copy the command that follows to your device. Make the following modifications to the command, as needed, and then run the modified command.
-
Replace
with the name of your cluster.my-cluster
-
Replace
with the name of the add-on that you want to update that was returned in the output of a previous step.vpc-cni
-
Replace
with the version returned in the output of the previous step that you want to update to. Some add-ons have recommended versions. For more information, see the documentation for the add-on that you're updating.version-number
-
If the add-on uses a Kubernetes service account and IAM role, replace
with your account ID and111122223333
with the name of an existing IAM role that you've created. For instructions on creating the role, see the documentation for the add-on that you're creating. Specifying a service account role requires that you have an IAM OpenID Connect (OIDC) provider for your cluster. To determine whether you have one for your cluster, or to create one, see Creating an IAM OIDC provider for your cluster.role-name
If the add-on doesn't use a Kubernetes service account and IAM role, delete the
serviceAccountRoleARN: arn:aws-cn:iam::
line.111122223333
:role/role-name
-
The
--resolve-conflicts
PRESERVE
option preserves existing values for the add-on. If you have set custom values for add-on settings, and you don't use this option, Amazon EKS overwrites your values with its default values. If you use this option, then we recommend that you test any field and value changes on a non-production cluster before updating the add-on on your production cluster. If you change this value tooverwrite
, all settings are changed to Amazon EKS default values. If you've set custom values for any settings, they might be overwritten with Amazon EKS default values. If you change this value tonone
, Amazon EKS doesn't change the value of any settings, but the update might fail. If the update fails, you receive an error message to help you resolve the conflict.
-
If you want to remove all custom configuration then perform the update using the
option. This sets all custom configuration back to the default values. If you don't want to change your custom configuration, don't provide the--configuration-values '{}'
flag. If you want to adjust a custom configuration then replace--configuration-values
with the new parameters. To see a list of parameters, see viewing configuration schema step in the create an add-on section.{}
aws eks update-addon --cluster-name
my-cluster
--addon-namevpc-cni
--addon-versionversion-number
\ --service-account-role-arn arn:aws-cn:iam::111122223333
:role/role-name
--configuration-values '{}'
--resolve-conflictsPRESERVE
-
-
Check the status of the update. Replace
with the name of your cluster andmy-cluster
with the name of the add-on you're updating.vpc-cni
aws eks describe-addon --cluster-name
my-cluster
--addon-namevpc-cni
An example output is as follows.
{ "addon": { "addonName": "
vpc-cni
", "clusterName": "my-cluster
", "status": "UPDATING", [...]The update is complete when the status is
ACTIVE
.
-
Deleting an add-on
When you delete an Amazon EKS add-on:
-
There is no downtime for the functionality that the add-on provides.
-
If the add-on has an IAM role associated with it, the IAM role isn't removed.
-
Amazon EKS stops managing settings for the add-on.
-
The console stops notifying you when new versions are available.
-
You can't update the add-on using any Amazon tools or APIs.
-
You can choose to leave the add-on software on your cluster so that you can self-manage it, or you can remove the add-on software from your cluster. You should only remove the add-on software from your cluster if there are no resources on your cluster are dependent on the functionality that the add-on provides.
You can delete an Amazon EKS add-on from your cluster using eksctl
, the
Amazon Web Services Management Console, or the Amazon CLI.
- eksctl
-
Prerequisite
Version
0.159.0
or later of theeksctl
command line tool installed on your device or Amazon CloudShell. To install or updateeksctl
, see Installing or updating eksctl.To delete an Amazon EKS add-on using
eksctl
-
Determine the current add-ons installed on your cluster. Replace
with the name of your cluster.my-cluster
eksctl get addon --cluster
my-cluster
An example output is as follows.
NAME VERSION STATUS ISSUES IAMROLE UPDATE AVAILABLE coredns v1.8.7-eksbuild.2 ACTIVE 0 kube-proxy v1.23.7-eksbuild.1 ACTIVE 0 vpc-cni v1.10.4-eksbuild.1 ACTIVE 0 [...]
Your output might look different, depending on which add-ons and versions that you have on your cluster.
-
Delete the add-on. Replace
with the name of your cluster andmy-cluster
with the name of the add-on returned in the output of the previous step that you want to remove. If you remove thename-of-add-on
option, in addition to Amazon EKS no longer managing the add-on, the add-on software is removed from your cluster.--preserve
eksctl delete addon --cluster
my-cluster
--namename-of-addon
--preserve
-
- Amazon Web Services Management Console
-
To delete an Amazon EKS add-on using the Amazon Web Services Management Console
Open the Amazon EKS console at https://console.amazonaws.cn/eks/home#/clusters
. -
In the left navigation pane, select Clusters, and then select the name of the cluster that you want to remove the Amazon EKS add-on for.
-
Choose the Add-ons tab.
-
Select the check box in the upper right of the add-on box and then choose Remove. Select Preserve on the cluster if you want Amazon EKS to stop managing settings for the add-on, but want to retain the add-on software on your cluster so that you can self-manage all of the settings for the add-on. Type the add-on name and then select Remove.
- Amazon CLI
-
Prerequisite
Version
0.159.0
or later of theeksctl
command line tool installed on your device or Amazon CloudShell. To install or updateeksctl
, see Installing or updating eksctl.To delete an Amazon EKS add-on using the Amazon CLI
-
See a list of installed add-ons. Replace
with the name of your cluster.my-cluster
aws eks list-addons --cluster-name
my-cluster
An example output is as follows.
{ "addons": [ "coredns", "kube-proxy", "vpc-cni", "
name-of-addon
" ] } -
Delete the installed add-on. Replace
with the name of your cluster andmy-cluster
with the name of the add-on that you want to remove. Removingname-of-add-on
removes the add-on software from your cluster.--preserve
aws eks delete-addon --cluster-name
my-cluster
--addon-namename-of-addon
--preserve
The abbreviated example output is as follows.
{ "addon": { "addonName": "
name-of-add-on
", "clusterName": "my-cluster
", "status": "DELETING", [...] -
Check the status of the deletion. Replace
with the name of your cluster andmy-cluster
with the name of the add-on that you're removing.name-of-addon
aws eks describe-addon --cluster-name
my-cluster
--addon-namename-of-addon
After the add-on is deleted, the example output is as follows.
An error occurred (ResourceNotFoundException) when calling the DescribeAddon operation: No addon:
name-of-addon
found in cluster:my-cluster
-