✨ move keepalived here from BMO repo

[Rozzii]

This PR:

• Moves the project used to build the Metal3 keepalived container from
  the BMO repository to this repository

These changes were needed for two related reasons.

• The community has decided that there is no reason to keep the keepalived
  files in BMO and they much better fit for the utility-images repository.

Related issues:

• Remove files from the project baremetal-operator#2085

[tuminoid]

Need to bring in the image building workflow as well, as well as parts of release workflow, and parts of release documentation too.

[Rozzii]

What is left to discuss with the community what release tags to use in the future for keepalived, as right now I don't see any reason to follow BMO releases/ release tags for keepalived.

The other PR that removes keepalived from BMO is also in progress.

I would also suggest doing a release of keepalived after this PR has been merged, as part of the release we would test whether everything works as expected and I would suggest choosing a release tag that is detached from BMO.

[tuminoid]

What is left to discuss with the community what release tags to use in the future for keepalived, as right now I don't see any reason to follow BMO releases/ release tags for keepalived.

No, we should release keepalived when there is relevant changes.

The other PR that removes keepalived from BMO is also in progress.

👍

I would also suggest doing a release of keepalived after this PR has been merged, as part of the release we would test whether everything works as expected and I would suggest choosing a release tag that is detached from BMO.

Absolutely. As we did with ironic-client, it is also good time to give it some attention, bump anything there is to bump etc, then release.

[tuminoid]

/hold

The release process needs to be agreed and then all the automation/docs adapted to match.

[tuminoid]

As discussed offline, let's split this into three PRs:

1. clean move PR, no modifications except necessary paths etc
2. add the functionality/changes required for the read-only filesystem improvement
3. add release logic separately (but keep the basic image build workflow)

This keeps the changes clean and testable, and also we don't need release logic until there is something new to release, like the read-only changes. Adapting the current release automation without branch support needs to be implemented carefully and generic enough so we can port that over to mariadb and other repos where we do similar lightweight releases going forward.

[Rozzii]

Release related stuff has been reoved from this PR,
Read only support is handled by BMO PR: metal3-io/baremetal-operator#2279
After the above mentioned PR has been merged this PR can be merged also.

[Rozzii]

After discussing offline a more about this comment metal3-io/baremetal-operator#2279 (review) I have made the decision to act accordingly so now this PR only moves keepalived here and I will make addition PRs to implement the RO-FS support here and not in the BMO repo or as part of the move process so that we will have a cleaner history. @tuminoid

[Rozzii]

/hold cancel
Reason is explained above .

[tuminoid]

/lgtm

[kashifest]

/approve

[lentzi90]

/approve

[metal3-io-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kashifest, lentzi90

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [lentzi90]

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