📖 Update prerequisites for installing Metal3 provider

[fmuyassarov]

What this PR does / why we need it:
From release v0.5.0 of Cluster-api-provider-metal3, the following
environment variables don't need to be exported because Baremetal
Operator is now decoupled from CAPM3. Instead, they need to be
exported when installing Baremetal Operator manually (not via
clusterctl).

[k8s-ci-robot]

Hi @fmuyassarov. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

[fmuyassarov]

/cc @kashifest

[k8s-ci-robot]

@fmuyassarov: GitHub didn't allow me to request PR reviews from the following users: kashifest.

Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @kashifest

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/test-infra repository.

[fmuyassarov]

/cc @fabriziopandini

[sbueringer]

/ok-to-test

If I got it correctly the metal3 provider before v0.5 (aka v0.4) is compliant with the CAPI v1alpha3 contract?

I'm not sure in which versions of the book this comment should be added.

[fmuyassarov]

/ok-to-test

If I got it correctly the metal3 provider before v0.5 (aka v0.4) is compliant with the CAPI v1alpha3 contract?

I'm not sure in which versions of the book this comment should be added.

Yes. Here is the compatibility table

| CAPM3 version | Cluster API version | CAPM3 Release |
|---------------|---------------------|---------------|
| v1alpha4      | v1alpha3            | v0.4.X        |
| v1alpha5      | v1alpha4            | v0.5.X        |
| v1beta1       | v1beta1             | v1.0.X        |

As such, I will need to backport it to release-0.4 branch (CAPI v1a4 & CAPM3 v1alpha5).

[fabriziopandini]

/lgtm

[fmuyassarov]

/cc @vincepri

[killianmuldoon]

/lgtm

[fabriziopandini]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

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

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

[fabriziopandini]

/cherry-pick release-1.0
given that this can avoid user problems

[k8s-infra-cherrypick-robot]

@fabriziopandini: once the present PR merges, I will cherry-pick it on top of release-1.0 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.0
given that this can avoid user problems

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/test-infra repository.

[k8s-infra-cherrypick-robot]

@fabriziopandini: new pull request created: #5655

In response to this:

/cherry-pick release-1.0
given that this can avoid user problems

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/test-infra repository.

[fmuyassarov]

@fabriziopandini thank you very much for the cherry-pick and review.