EKS Anywhere curated package management

Common tasks for managing curated packages.

1: Harbor

The main goal of EKS Anywhere curated packages is to make it easy to install, configure and maintain operational components in an EKS Anywhere cluster. EKS Anywhere curated packages offers to run secure and tested operational components on EKS Anywhere clusters. Please check out EKS Anywhere curated packages for more details.

Check the existence of package controller

kubectl get pods -n eksa-packages | grep "eks-anywhere-packages"

Skip the following installation steps if the returned result is not empty.

Important

To install EKS Anywhere, create an EKS Anywhere cluster or review the EKS Anywhere system requirements. See the Getting started
guide for details.
Check if the version of eksctl anywhere is v0.9.0 or above with the following commands:
```
eksctl anywhere version
```
Make sure cert-manager is up and running in the cluster.

Install package controller

Install the package controller

eksctl anywhere install packagecontroller --kube-version 1.21

Check the package controller

kubectl get pods -n eksa-packages

Example command output

NAME                                       READY   STATUS     RESTARTS   AGE
eks-anywhere-packages-57778bc88f-587tq     2/2     Running    0          16h

Curated package list

See packages for the complete curated package list.

1 - Harbor

Install/upgrade/uninstall Harbor

Important

If your cluster was created with a release of EKS Anywhere prior to v0.9.0, you may need to install the package controller.

Install

Generate the package configuration

eksctl anywhere generate package harbor --source cluster > packages.yaml

Add the desired configuration to packages.yaml

Please see complete configuration options for all configuration options and their default values.

Important

All configuration options are listed in dot notations (e.g., expose.tls.enabled) in the doc, but they have to be transformed to hierachical structures when specified in the config section in the YAML spec.
Harbor web portal is exposed through NodePort by default, and its default port number is 30003 with TLS enabled and 30002 with TLS disabled.
TLS is enabled by default for connections to Harbor web portal, and a secret resource named harbor-tls-secret is required for that purpose. It can be provisioned through cert-manager or manually with the following command using self-signed certificate:
```
kubectl create secret tls harbor-tls-secret --cert=[path to certificate file] --key=[path to key file] -n eksa-packages
```
secretKey has to be set as a string of 16 characters for encryption.

TLS example with auto certificate generation

apiVersion: packages.eks.amazonaws.com/v1alpha1
kind: Package
metadata:
   name: my-harbor
   namespace: eksa-packages
spec:
   packageName: harbor
   config: |-
      secretKey: "use-a-secret-key"
      externalURL: https://harbor.eksa.demo:30003
      expose:
         tls:
            certSource: auto
            auto:
               commonName: "harbor.eksa.demo"

Non-TLS example

apiVersion: packages.eks.amazonaws.com/v1alpha1
kind: Package
metadata:
   name: my-harbor
   namespace: eksa-packages
spec:
   packageName: harbor
   config: |-
      secretKey: "use-a-secret-key"
      externalURL: http://harbor.eksa.demo:30002
      expose:
         tls:
            enabled: false

Install Harbor

eksctl anywhere create packages -f packages.yaml

Check Harbor

eksctl anywhere get packages

Example command output

NAME        PACKAGE   AGE     STATE       CURRENTVERSION             TARGETVERSION        DETAIL
my-harbor   harbor    5m34s   installed   v2.5.0                     v2.5.0 (latest)

Harbor web portal is accessible at whatever externalURL is set to. See complete configuration options for all default values.

Harbor web portal

Upgrade

Note

New versions of software packages will be automatically downloaded but not automatically installed. You can always manually run eksctl to check and install updates.

Verify a new bundle is available

eksctl anywhere get packagebundle

Example command output

NAME         VERSION   STATE
v1.21-1000   1.21      active (upgrade available)
v1.21-1001   1.21      inactive

Upgrade Harbor

eksctl anywhere upgrade packages --bundle-version v1.21-1001

Check Harbor

eksctl anywhere get packages

Example command output

NAME        PACKAGE   AGE     STATE       CURRENTVERSION             TARGETVERSION        DETAIL
my-harbor   Harbor    14m     installed   v2.5.1                     v2.5.1 (latest)

Uninstall

Uninstall Harbor
Important
- By default, PVCs created for jobservice and registry are not removed during a package delete operation, which can be changed by leaving persistence.resourcePolicy empty.
```
eksctl anywhere delete package my-harbor
```