Skip to content

EKS

Jump to bottom
Christian Hueller edited this page Jun 8, 2020 · 17 revisions

EKS

If you are running the make targets locally, be sure to have met the Local requirements.

Getting a EKS cluster configured for CAP

$> EKS_ZONE_NAME=<name of dns zone> EKS_ZONE_ID=<id of dns zone> BACKEND=eks make k8s

EKS_ZONE_NAME and EKS_ZONE_ID are required for automatic addition of dns entries on aws zone53. You can find the values in the aws route53 web console.

This target leverages CAP-Terraform to deploy a EKS cluster prepared for CAP. The cluster comes with Helm/Tiller installed, RBACs and a hostpath storageclass, yet the storageclass has for name gp2.

The target downloads all needed aws binaries and authenticator plugins and sets them up in buildir/*.

Needs aws predefined env vars for credentials present (see https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html), e.g.:

AWS_ACCESS_KEY_ID=AKIAIOSFODNN7EXAMPLE
AWS_SECRET_ACCESS_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
AWS_DEFAULT_REGION=us-west-2

If you want to use existing credentials e.g. n your home directory, you can run

AWS_ACCESS_KEY_ID=$(grep aws_access_key_id ~/.aws/credentials | awk '{ print $3 }')
AWS_SECRET_ACCESS_KEY=$(grep aws_secret_access_key ~/.aws/credentials | awk '{ print $3 }')
AWS_DEFAULT_REGION=$(grep region ~/.aws/config | awk '{ print $3 }')

Destroying the deployment of EKS

Since the infrastructure is living on EKS, instead of deleting the corresponding build folder, please run:

$> BACKEND=eks make clean

Deploying EKS and CAP 1.5 on top

Note: 🚧 manual steps required!

Since cap-terraform gives us so far a cluster with storageclass named gp2, one would need to:

  1. Deploy an eks cluster:
    $> BACKEND=eks make k8s
  1. Get the charts and the scf-config-values.yaml file:
    $> BACKEND=eks make scf-chart scf-gen-config

  1. Manually change the storageclass name from persistent to gp2 in buildeks/scf-config-values.yaml

  2. Install scf

    $> BACKEND=eks make scf-deploy
  1. Since Ingress/domain of the EKS cluster is not set up, work within the cluster by creating a pod containing catapult, and getting into it.

Clone this wiki locally