Skip to content

Version helm charts #82

@alukach

Description

@alukach

We are currently publishing Helm charts on every deployment to main:

name: Publish Helm Chart
on:
push:
branches:
- main
paths:
- 'helm/**'
- '.github/workflows/publish-helm.yaml'
release:
types: [created]

I assume that we should likely version these charts and only publish on release, similar to how we treat our Docker images:

name: Publish Docker image
on:
release:
types: [published]

@batpad please correct me if I'm misunderstanding the nature of how Helm charts are typically managed.

Removing the on: push section of our actions is trivial. However, I'm unsure where we should inject ${{ github.event.release.tag_name }} for proper tagging. For whatever reason, we get pretty funky with our Docker Images:

- name: Extract metadata (tags, labels) for Docker
id: meta
uses: docker/metadata-action@v5
with:
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
tags: |
type=raw,value=${{ github.event.release.tag_name }}
type=raw,value=latest,enable=${{ github.event.release.prerelease == false }}
- name: Build and push Docker image
uses: docker/build-push-action@v5
with:
context: .
push: true
platforms: linux/amd64,linux/arm64
tags: ${{ steps.meta.outputs.tags }}
labels: ${{ steps.meta.outputs.labels }}

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions