All k8s-shredder binaries, container image and helm chart are released using github actions workflows. See release workflow and release chart workflow for more details.
For publishing a new release follow below steps:
export NEW_VERSION=vX.Y.Z
git tag -a ${NEW_VERSION} -m "Release ${NEW_VERSION}"
git push origin ${NEW_VERSION}
For release process we're using goreleaser. You must install it first before being able to
release a new version.
Config file for goreleaser can be found in goreleaser file
GoReleaser requires an API token with the repo scope selected to deploy the artifacts to GitHub.
For generating a new token, you can create one from tokens section. For more details see
creating-a-personal-access-token
For publishing a new release follow below steps:
export NEW_VERSION=vX.Y.Z
git tag -a ${NEW_VERSION} -m "Release ${NEW_VERSION}"
git push origin ${NEW_VERSION}
export GITHUB_TOKEN=<your_github_PAT_token>
docker login ghcr.io
Username: <your_github_username>
Password: <your_github_PAT_token>
make publish
You can check if the new release and associated artifacts were properly pushed into GitHub by accessing k8s-shredder releases