✨ Add fake K8s API server

[mquhuy]

Fake API server is a tool running inside a kubernetes cluster, and "generates" in-memory api server endpoints. These endpoints can be used, for e.g., to represent the clusters created by CAPM3 using fake hardware so that CAPI confirms that the cluster was provisioned successfully.

[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

[mquhuy]

/cc @lentzi90 @kashifest @Rozzii @tuminoid @adilGhaffarDev
This was proven to work, it's ready for reviews

[tuminoid]

There is unrelated broken link failure, need to address that in another PR preferably.

[tuminoid]

Some nits for starters.

[tuminoid]

The Dockerfile is broken now.

[mquhuy]

/test metal3-centos-e2e-integration-test-main
/test metal3-ubuntu-e2e-integration-test-main

[tuminoid]

Some minor nits, but I guess the main question here is that why this should be part of CAPM3 repo in the first place? We should not bloat the repo with non-core stuff.

/cc @kashifest

[mquhuy]

Some minor nits, but I guess the main question here is that why this should be part of CAPM3 repo in the first place? We should not bloat the repo with non-core stuff.

/cc @kashifest

Thanks @tuminoid, I'm ok with putting it elsewhere, as long as it makes sense, but I think having it here was a decision we came up together at some point.

[Rozzii]

On first glance stuff looks OK, thanks for working on this. Could you please add info about the limitations in the README I assume this wouldn't be able to work with Metal3Data and DataTemplates and maybe has other limitations but I might be wrong.
AFAIK this is not a plug in place fake replacement of the whole CAPM3 so just want users to have the right expectation.

[tuminoid]

/hold
Until proper place for this code is agreed.

[mquhuy]

On first glance stuff looks OK, thanks for working on this. Could you please add info about the limitations in the README I assume this wouldn't be able to work with Metal3Data and DataTemplates and maybe has other limitations but I might be wrong. AFAIK this is not a plug in place fake replacement of the whole CAPM3 so just want users to have the right expectation.

Thanks for the suggestion! This stuff's only intended to generate the kubernetes API server on demands, so it should not be considered a replacement for CAPM3, but it's something that will work alongside CAPM3, BMO and Ironic, in case ironic is hooked with something like Fake-IPA, whose "nodes" cannot provide the functionality of a kubernetes cluster. I guess the docs needs to clarify this better.

[kashifest]

/hold cancel
We have decided that it can stay in CAPM3.
@adilGhaffarDev @Sunnatillo @mboukhalfa @tuminoid

[tuminoid]

Besides outdated versions, we need to consider what else we need due adding another go.mod into CAPM3.

• dependabot config ?
• verify-release.sh (exclude it)
• release docs (do not tag it)
• makefile (make modules, make verify)
• hack/gomod.sh

are all doing something for all go.mod files.

[tuminoid]

We're at 1.22.7 now

[tuminoid]

We're at v0.29.9

[tuminoid]

We're at v1.8.3

[Rozzii]

@mquhuy I have made K8s explicit in the PR title, because at least for me it was confusing that what API we are faking.