Github Action for executing Helm commands on EKS (using aws-iam-authenticator).
The Helm version installed is Helm3.
This action was inspired by kubernetes-action.
This Github Action was created with EKS in mind, therefore the following example refers to it.
plugins
: you can specify a list of Helm plugins you'd like to install and use later on in your command. eg. helm-secrets or helm-diff. This action does not support only a specific list of Helm plugins, rather any Helm plugin as long as you supply its URL. You can use the following example as a reference.command
: your kubectl/helm command. This supports multiline as per the Github Actions workflow syntax.
example for multiline:
...
with:
command: |
helm upgrade --install my-release chart/repo
kubectl get pods
name: deploy
on:
push:
branches:
- master
- develop
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: AWS Credentials
uses: aws-actions/configure-aws-credentials@v1
with:
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
aws-region: us-east-1
- name: helm deploy
uses: koslib/helm-eks-action@master
env:
KUBE_CONFIG_DATA: ${{ secrets.KUBE_CONFIG_DATA }}
with:
plugins: "https://github.com/jkroepke/helm-secrets" # optional
command: helm upgrade <release name> --install --wait <chart> -f <path to values.yaml>
Use the output of your command in later steps
steps:
- name: Get URL
id: url
uses: koslib/helm-eks-action@master
env:
KUBE_CONFIG_DATA: ${{ secrets.KUBE_CONFIG_DATA }}
with:
command: kubectl get svc my_svc -o json | jq -r '.status.loadBalancer.ingress[0].hostname'
- name: Print Response
run: echo "Response was ${{ steps.url.outputs.response }}"
Create a GitHub Secret for each of the following values:
KUBE_CONFIG_DATA
Your kube config file in base64-encrypted form. You can do that with
cat $HOME/.kube/config | base64
-
AWS_ACCESS_KEY_ID
-
AWS_SECRET_ACCESS_KEY
Pull requests, issues or feedback of any kind are more than welcome by anyone!