Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

merge to main #195

Merged
merged 4 commits into from
Feb 11, 2024
Merged

merge to main #195

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ac39044
remove some boilerplate comments
nam20485 Feb 10, 2024
7e2f932
Merge branch 'development' into nam20485
nam20485 Feb 10, 2024
183ae39
add debugging output around kubeconfig
nam20485 Feb 11, 2024
e4aaeae
merge to development (#194)
nam20485 Feb 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 6 additions & 29 deletions .github/workflows/deploy-eks.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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

Expand Down Expand Up @@ -71,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
Expand Down
Loading