sigs.k8s.io/cluster-api-provider-aws@v1.5.5/docs/book/src/topics/eks/addons.md (about)

     1  # EKS Addons
     2  
     3  [EKS Addons](https://aws.amazon.com/blogs/containers/introducing-amazon-eks-add-ons/) can be used with EKS clusters created using Cluster API Provider AWS.
     4  
     5  Addons are supported in EKS clusters using Kubernetes v1.18 or greater.
     6  
     7  ## Installing addons
     8  
     9  To install an addon you need to declare them by specifying the name, version and optionally how conflicts should be resolved in the `AWSManagedControlPlane`. For example:
    10  
    11  ```yaml
    12  kind: AWSManagedControlPlane
    13  apiVersion: controlplane.cluster.x-k8s.io/v1beta1
    14  metadata:
    15    name: "capi-managed-test-control-plane"
    16  spec:
    17    region: "eu-west-2"
    18    sshKeyName: "capi-management"
    19    version: "v1.18.0"
    20    addons:
    21      - name: "vpc-cni"
    22        version: "v1.6.3-eksbuild.1"
    23        conflictResolution: "overwrite"
    24  ```
    25  
    26  Additionally, there is a cluster [flavor](https://cluster-api.sigs.k8s.io/clusterctl/commands/config-cluster.html#flavors)
    27  called [eks-managedmachinepool-vpccni](../../templates/cluster-template-eks-managedmachinepool-vpccni.yaml) that you can use with **clusterctl**:
    28  
    29  ```shell
    30  clusterctl generate cluster my-cluster --kubernetes-version v1.18.0 --flavor eks-managedmachinepool-vpccni > my-cluster.yaml
    31  ```
    32  
    33  ## Updating Addons
    34  
    35  To update the version of an addon you need to edit the `AWSManagedControlPlane` instance and update the version of the addon you want to update. Using the example from the previous section we would do:
    36  
    37  ```yaml
    38  ...
    39    addons:
    40      - name: "vpc-cni"
    41        version: "v1.7.5-eksbuild.1"
    42        conflictResolution: "overwrite"
    43  ...
    44  ```
    45  
    46  ## Deleting Addons
    47  
    48  To delete an addon from a cluster you need to edit the `AWSManagedControlPlane` instance and remove the entry for the addon you want to delete.
    49  
    50  ## Viewing installed addons
    51  
    52  You can see what addons are installed on your EKS cluster by looking in the `Status`  of the `AWSManagedControlPlane` instance.
    53  
    54  Additionally you can run the following command:
    55  
    56  ```bash
    57  clusterawsadm eks addons list-installed -n <<eksclustername>>
    58  ```
    59  
    60  ## Viewing available addons
    61  
    62  You can see what addons are available to your EKS cluster by running the following command:
    63  
    64  ```bash
    65  clusterawsadm eks addons list-available -n <<eksclustername>>
    66  ```