🌱 Add FKAS build to PR checks

[peppi-lotta]

Add FKAS build to PR checks runs when something changes under ./hack/fake-apiserver file.
Related PR: metal3-io/cluster-api-provider-metal3#2814

[tuminoid]

What's the status with this and the Github workflows? This is not needed right?

[peppi-lotta]

I think this is ready to merge. This adds fkas image building as one check that PRs run. I think it's enough to have the check on the main branch and future release branches. It would require some changes to the CAPM3 release branches to make this work on them and this is why I've oped to add the build test only on main branch.

[tuminoid]

/approve
/hold
for one more fix.

[metal3-io-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tuminoid

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 [tuminoid]

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

[tuminoid]

/override metal3-ubuntu-e2e-integration-test-main
/cc @lentzi90
/unhold

[metal3-io-bot]

@tuminoid: Overrode contexts on behalf of tuminoid: metal3-ubuntu-e2e-integration-test-main

In response to this:

/override metal3-ubuntu-e2e-integration-test-main
/cc @lentzi90
/unhold

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.

[lentzi90]

/lgtm

[metal3-io-bot]

@peppi-lotta: Updated the job-config configmap in namespace prow at cluster default using the following files:

• key cluster-api-provider-metal3.yaml using file prow/config/jobs/metal3-io/cluster-api-provider-metal3.yaml

In response to this:

Add FKAS build to PR checks runs when something changes under ./hack/fake-apiserver file.
Related PR: metal3-io/cluster-api-provider-metal3#2814

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.