🌱 Add release github workflow

[mquhuy]

Now that the release workflow is working in IPAM, we can also add it to BMO repo.

[metal3-io-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign kashifest for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tuminoid]

We were supposed to add it after 1.9 so we can iron out all the issues to avoid fixing multiple repos. I don't think we have a single clean run in IPAM yet, nor have done patch releases with it etc.

We also agreed to make it reusable workflow before taking it in other repos.
/hold

[mquhuy]

We were supposed to add it after 1.9 so we can iron out all the issues to avoid fixing multiple repos. I don't think we have a single clean run in IPAM yet, nor have done patch releases with it etc.

We also agreed to make it reusable workflow before taking it in other repos. /hold

My intention is to have this in if we have IPAM release working. In case it doesn't work out, we should fix this PR and then test it out. IMO without taking this into use in other repos, it will take a long time to have a fully working solution.

The current setup in IPAM only fails in the build image step, which can be relatively easy to patch.

[tuminoid]

Let's have this discussion in CAPM3 PR, no point pasting commentary to both PRs.
metal3-io/cluster-api-provider-metal3#2161

[metal3-io-bot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.