From ac39044e6c09c08a682137441bace91e3e789f2f Mon Sep 17 00:00:00 2001 From: Nathan Miller Date: Sat, 10 Feb 2024 09:17:48 -0800 Subject: [PATCH 1/2] remove some boilerplate comments --- .github/workflows/deploy-eks.yml | 26 +------------------------- 1 file changed, 1 insertion(+), 25 deletions(-) diff --git a/.github/workflows/deploy-eks.yml b/.github/workflows/deploy-eks.yml index b88c848d..98fdbed6 100644 --- a/.github/workflows/deploy-eks.yml +++ b/.github/workflows/deploy-eks.yml @@ -1,28 +1,4 @@ -# This workflow will build and push a new container image to Amazon ECR, -# and then will deploy a new task definition to Amazon ECS, when there is a push to the "development" branch. -# -# To use this workflow, you will need to complete the following set-up steps: -# -# 1. Create an ECR repository to store your images. -# For example: `aws ecr create-repository --repository-name my-ecr-repo --region us-east-2`. -# Replace the value of the `ECR_REPOSITORY` environment variable in the workflow below with your repository's name. -# Replace the value of the `AWS_REGION` environment variable in the workflow below with your repository's region. -# -# 2. Create an ECS task definition, an ECS cluster, and an ECS service. -# For example, follow the Getting Started guide on the ECS console: -# https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun -# Replace the value of the `ECS_SERVICE` environment variable in the workflow below with the name you set for the Amazon ECS service. -# Replace the value of the `ECS_CLUSTER` environment variable in the workflow below with the name you set for the cluster. -# -# 3. Store your ECS task definition as a JSON file in your repository. -# The format should follow the output of `aws ecs register-task-definition --generate-cli-skeleton`. -# Replace the value of the `ECS_TASK_DEFINITION` environment variable in the workflow below with the path to the JSON file. -# Replace the value of the `CONTAINER_NAME` environment variable in the workflow below with the name of the container -# in the `containerDefinitions` section of the task definition. -# -# 4. Store an IAM user access key in GitHub Actions secrets named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`. -# See the documentation for each action used below for the recommended IAM policies for this IAM user, -# and best practices on handling the access key credentials. +# This workflow will restart the deployment to affect a deployment of a new image in the EKS cluster name: Deploy to Amazon EKS From 183ae393b7d4c398eb134053838feaeaaee5d242 Mon Sep 17 00:00:00 2001 From: Nathan Miller Date: Sat, 10 Feb 2024 16:11:43 -0800 Subject: [PATCH 2/2] add debugging output around kubeconfig --- .github/workflows/deploy-eks.yml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/.github/workflows/deploy-eks.yml b/.github/workflows/deploy-eks.yml index 98fdbed6..240d50ba 100644 --- a/.github/workflows/deploy-eks.yml +++ b/.github/workflows/deploy-eks.yml @@ -47,11 +47,12 @@ jobs: # KUBE_CONFIG: ${{ secrets.KUBECONFIG }} - name: Configure kubectl via Secret Env - env: - KUBE_CONFIG: ${{ secrets.KUBECONFIG }} run: | - echo $KUBE_CONFIG > ${{ github.workspace }}/kubeconfig - export KUBECONFIG=${{ github.workspace }}/kubeconfig + echo ${{ secrets.KUBECONFIG }} > ${{ github.workspace }}/kubeconfig + export KUBECONFIG=${{ github.workspace }}/kubeconfig + echo $KUBECONFIG + cat $KUBECONFIG + kubectl config view kubectl config get-contexts kubectl config use-context eks-uswest2-cluster kubectl version