Skip to content

Build and release Helm packages on s3 repositories using Github Actions.

License

Notifications You must be signed in to change notification settings

shellbear/helm-release-action

Use this GitHub action with your project
Add this Action to an existing workflow or create a new one
View on Marketplace

Repository files navigation

helm-release-action

Build and release Helm packages on s3 repositories using Github Actions.

Instructions on how to set up a S3 bucket as a helm chart repository: https://andrewlock.net/how-to-create-a-helm-chart-repository-using-amazon-s3/.

Changelog

Examples

Using aws-actions/configure-aws-credentials@v1 action to configure S3 access:

name: Release
on: [push]
jobs:
  build:
    name: Chart release
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2
      - name: Configure 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: eu-west-1
      - name: Helm release
        uses: shellbear/helm-release-action@v0.2
        with:
          repo: s3://s3-bucket-example/
          chart: ./deployment/helm

Parameters

Inputs

Required

  • repo: The S3 Helm repository bucket URL.

Optional

  • version: Override Helm chart version.
  • chart: Helm chart path. (default: ./)
  • forceRelease: If set to false and the chart already exists, exit normally and do not trigger an error. (default: true).
  • packageExtraArgs: Helm package command extra arguments.
  • relativeUrls: Helm-s3 push option for creating URLs that are relative to the Index location. By default, URLs are the full path using s3:// protocol. If you intend to serve your Helm repository via http(s), you should enable this option. (default: false)

Build with

  • helm-s3
  • helm-pack: used instead of helm package command to suport --value flag.

Author