Quickstart: Deploy a web app and store data

Create a cluster-config.yaml file and paste the following contents into it. Replace region-code with a valid Region, such as us-east-1

Example output is as follows:

apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig

metadata:
  name: web-quickstart
  region: region-code

managedNodeGroups:
  - name: eks-mng
    instanceType: t3.medium
    desiredCapacity: 2

iam:
  withOIDC: true
  serviceAccounts:
  - metadata:
      name: aws-load-balancer-controller
      namespace: kube-system
    wellKnownPolicies:
      awsLoadBalancerController: true

addons:
  - name: aws-ebs-csi-driver
    wellKnownPolicies: # Adds an IAM service account
      ebsCSIController: true

cloudWatch:
 clusterLogging:
   enableTypes: ["*"]
   logRetentionInDays: 30

Create the Amazon EKS cluster and specify the cluster-config.yaml.

eksctl create cluster -f cluster-config.yaml

Upon completion, you should see the following response output:

2024-07-04 21:47:53 [✔]  EKS cluster "web-quickstart" in "region-code" region is ready

Set the CLUSTER_REGION environment variable for your Amazon EKS cluster. Replace the sample value for region-code.

export CLUSTER_REGION=region-code
            

Set the CLUSTER_VPC environment variable for your Amazon EKS cluster.

export CLUSTER_VPC=$(aws eks describe-cluster --name web-quickstart --region $CLUSTER_REGION --query "cluster.resourcesVpcConfig.vpcId" --output text)

Use Helm to add the Amazon EKS chart repository to Helm.

helm repo add eks https://aws.github.io/eks-charts

Update the repositories to ensure Helm is aware of the latest versions of the charts:

helm repo update eks

Run the following Helm command to simultaneously install the Custom Resource Definitions (CRDs) and the main controller for the AWS Load Balancer Controller (AWS LBC). To skip the CRD installation, pass the --skip-crds flag, which might be useful if the CRDs are already installed, if specific version compatibility is required, or in environments with strict access control and customization needs.

helm install aws-load-balancer-controller eks/aws-load-balancer-controller \
    --namespace kube-system \
    --set clusterName=web-quickstart \
    --set serviceAccount.create=false \
    --set region=${CLUSTER_REGION} \
    --set vpcId=${CLUSTER_VPC} \
    --set serviceAccount.name=aws-load-balancer-controller

You should see the following response output:

NAME: aws-load-balancer-controller
LAST DEPLOYED: Wed July 3 19:43:12 2024
NAMESPACE: kube-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
AWS Load Balancer controller installed!

Create a Kubernetes namespace called game-2048 with the --save-config flag.

kubectl create namespace game-2048 --save-config

You should see the following response output:

namespace/game-2048 created

Deploy the 2048 Game Sample application.

kubectl apply -n game-2048 -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.8.0/docs/examples/2048/2048_full.yaml

This manifest sets up a Kubernetes Deployment, Service, and Ingress for the game-2048 namespace, creating the necessary resources to deploy and expose the game-2048 application within the cluster. It includes the creation of a service named service-2048 that exposes the deployment on port 80, and an Ingress resource named ingress-2048 that defines routing rules for incoming HTTP traffic and annotations for an internet-facing Application Load Balancer (ALB). You should see the following response output:

namespace/game-2048 configured
deployment.apps/deployment-2048 created
service/service-2048 created
ingress.networking.k8s.io/ingress-2048 created

Run the following command to get the Ingress resource for the game-2048 namespace.

kubectl get ingress -n game-2048

You should see the following response output:

NAME           CLASS   HOSTS   ADDRESS                                                                    PORTS   AGE
ingress-2048   alb     *       k8s-game2048-ingress2-eb379a0f83-378466616.region-code.elb.amazonaws.com   80      31s

You’ll need to wait several minutes for the Application Load Balancer (ALB) to provision before you begin the following steps.

Open a web browser and enter the ADDRESS from the previous step to access the web application. For example:

k8s-game2048-ingress2-eb379a0f83-378466616.region-code.elb.amazonaws.com

You should see the 2048 game in your browser. Play!

Create a Storage Class for the EBS CSI Driver:

kubectl apply -n game-2048 -f https://raw.githubusercontent.com/kubernetes-sigs/aws-ebs-csi-driver/master/examples/kubernetes/dynamic-provisioning/manifests/storageclass.yaml

Create a Persistent Volume Claim (PVC) to request storage for your game data. Create a file named ebs-pvc.yaml and add the following content to it:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: game-data-pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 10Gi
  storageClassName: ebs-sc

Apply the PVC to your cluster:

kubectl apply -f ebs-pvc.yaml

You should see the following response output:

persistentvolumeclaim/game-data-pvc created

Now, you need to update your 2048 game deployment to use this PVC for storing data. The following deployment is configured to use the PVC for storing game data. Create a file named ebs-deployment.yaml and add the following contents to it:

apiVersion: apps/v1
kind: Deployment
metadata:
  namespace: game-2048
  name: deployment-2048
spec:
  replicas: 3  # Adjust the number of replicas as needed
  selector:
    matchLabels:
      app.kubernetes.io/name: app-2048
  template:
    metadata:
      labels:
        app.kubernetes.io/name: app-2048
    spec:
      containers:
        - name: app-2048
          image: public.ecr.aws/l6m2t8p7/docker-2048:latest
          imagePullPolicy: Always
          ports:
            - containerPort: 80
          volumeMounts:
            - name: game-data
              mountPath: /var/lib/2048
      volumes:
        - name: game-data
          persistentVolumeClaim:
            claimName: game-data-pvc

Apply the updated deployment:

kubectl apply -f ebs-deployment.yaml

You should see the following response output:

deployment.apps/deployment-2048 configured