kube's Introduction

Github Action for Kubernetes CLI

Image based on debian11
Fork from patoxs
docker push redalvagui/kube:latest

Usage

.github/workflows/eks.yml

The yaml file should look like

on: push
name: deploy
env:
  IMAGE: 'bash:5.2'
  NAMESPACE: 'test'
jobs:
  deploy:
    name: Deploy to cluster
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@master

    - name: deploy to cluster
      uses: RAcl/kube@main
      env:
        KUBE_CONFIG: ${{ secrets.KUBE_CONFIG_DATA }}
        AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
        AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
        AWS_DEFAULT_REGION: ${{ secrets.AWS_DEFAULT_REGION }}
      with:
        args: set image --record deployment.apps/my-app my-app=${{ env.IMAGE }} -n ${{ env.NAMESPACE }}

    - name: verify deployment
      uses: RAcl/kube@main
      env:
        KUBE_CONFIG: ${{ secrets.KUBE_CONFIG_DATA }}
        AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
        AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
        AWS_DEFAULT_REGION: ${{ secrets.AWS_DEFAULT_REGION }}
      with:
        args: rollout status deployment.apps/my-app -n ${{ env.NAMESPACE }}

Secrets

KUBE_CONFIG_DATA – required: A base64-encoded kubeconfig file with credentials for Kubernetes to access the cluster. You can get it by running the following command:
```
cat $HOME/.kube/config | base64
```
AWS_ACCESS_KEY_ID – required: AWS account access key ID, located in the credentials file. You can get it by running the following command:
```
cat ~/.aws/credentials
```
AWS_SECRET_ACCESS_KEY – required: AWS account secret access key, located in the credentials file. You can get it by running the following command:
```
cat ~/.aws/credentials
```
AWS_DEFAULT_REGION – no-required: AWS region where the deployment will be made. Default region is us-east-1

Recommend Projects