Skip to content
Example Workflow to deploy a static website to an existing Amazon EKS cluster
Branch: master
Clone or download
parkr Merge pull request #4 from actions/codeowners
Add a CODEOWNERS file to streamline review.
Latest commit f4ff58a Feb 12, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Add a CODEOWNERS file to streamline review. Feb 9, 2019
site Initial commit Oct 16, 2018
Dockerfile Initial commit Oct 16, 2018
LICENSE Create LICENSE Oct 16, 2018
README.md Fix broken link in README Dec 20, 2018
config.yml Initial commit Oct 16, 2018
nginx.conf Initial commit Oct 16, 2018

README.md

Amazon Web Service (AWS) - GitHub Action Example

An example workflow, using the GitHub Action for AWS to build, tag, and deploy a container image to a running Kubernetes cluster on EKS.

Workflow

The example workflow will trigger on every push to this repo.

For pushes to a feature branch, the workflow will:

  1. Build the Docker image from the included Dockerfile
  2. Tag and push the image to Amazon Elastic Container Registry

For pushes to the default branch (master), in addition to the above Actions, the workflow will:

  1. Create a deployment using config.yml on the running EKS cluster with the latest container image

Prerequisites

  1. Create an Amazon user with EKS IAM role permissions to EKS - eks user role

  2. Create a Repository in Amazon Elastic Container Registry to push images to

  3. Follow the Getting Started Guide to set up a cluster on EKS

  4. Generate a kubectl config with credentials to access the cluster - for example: aws eks update-kubeconfig --name $CLUSTER_NAME --region $AWS_DEFAULT_REGION - base64 encode this file and save this as the KUBE_CONFIG_DATA secret

    cat $HOME/.kube/config | base64

You can’t perform that action at this time.