✨ add fetchConfig support to IPAMProvider in chart

[manetherenio]

What this PR does / why we need it:
While attempting to perform an air-gapped installation of the cluster-api operator using in-cluster IPAM, the helm chart does not utilize fetchConfig for the IPAMProvider CR, so there isn't a way to point the IPAM container to anything other than registry.k8s.io/capi-ipam-ic/cluster-api-ipam-in-cluster-controller:v1.0.1. Since I am trying to point all containers towards a local registry, I need to have the IPAMProvider fetch a LAN-located config which will point towards the disconnected container registry instead of generating its own. The IPAMProvider CRD already supports this, it just needs an update to the Helm chart to allow it to work properly.

Basically extending these steps:

https://cluster-api-operator.sigs.k8s.io/03_topics/02_configuration/01_air-gapped-environtment.html?highlight=air-gap#air-gapped-environment

But for the IPAM provider as well as the Infrastructure provider.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[k8s-ci-robot]

Welcome @manetherenio!

It looks like this is your first PR to kubernetes-sigs/cluster-api-operator 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-operator has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @manetherenio. 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-sigs/prow repository.

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-operator ready!

Name	Link
🔨 Latest commit	1fcd8ba
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-cluster-api-operator/deploys/6833da2f61f7480008759a5d
😎 Deploy Preview	https://deploy-preview-817--kubernetes-sigs-cluster-api-operator.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[furkatgofurov7]

/ok-to-test

[furkatgofurov7]

Thanks for the PR @manetherenio!

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: furkatgofurov7

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

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

[alexander-demicev]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 840081828830b8b9a6e4aa71f631ad45c5238137