Build container image with every release

[migmartri]

Apart of the binary release now performed by a github action using goreleaser, we also want to offer a container image that contains the binary already bundled in, so it can be easily used in CI usecases for example.

Up until the migration of the release process from the internal infra to github actions, we have been offering the image through distribution harbor in this URI http://projects.registry.vmware.com/tanzu_isv_engineering/relok8s

The issue with that location is that it requires pushing from within VMware's VPN, which rules out the possibility of allowing the external build process (the current one using goreleaser) to be the one building and pushing the image.

That's why I suggest to also move that process to be hosted at https://github.com/features/packages, similarly to what kapp-controller does.

The task will be

• Update goreleaser to build and push the container image to github packages
• Update our runway pipeline to trigger relocate-helm-chart test from those images instead

cc/ @josvazg @petewall

[migmartri]

We need vmware-tanzu org admins to enable the container images packages functionality in our repository https://github.com/orgs/vmware-tanzu/packages

https://docs.github.com/en/packages/learn-github-packages/connecting-a-repository-to-a-package#connecting-a-repository-to-an-organization-owned-package-on-github

[migmartri]

Actually nevermind, it's not needed, I managed to push the image and connect it to the repo via labels

docker pull ghcr.io/vmware-tanzu/asset-relocation-tool-for-kubernetes:latest