✨ 🌱 Make configSecret configurable per component

[rbjorklin]

What this PR does / why we need it:
This builds on the extensibility introduced in #638.

• This makes the connection between the configSecret and the component/provider using said config clearer.
• Reduces duplication of the configSecret logic across templates by moving it into a helper.

This has been implemented in such a way that it is backwards compatible and will default to the existing behaviour. If you want to use the new behaviour you would have to do something like this:

core:
  cluster-api:
    version: v1.9.6
    configSecret:
      name: my-custom-core-config
      namespace: capi-system

infrastructure:
  azure:
    namespace: capz-system
    version: v1.19.1
    configSecret:
      name: azure-variables
      namespace: capz-system

while also removing the configSecret key at the root level of the values.yaml file.

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]

[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 damdo for approval. For more information see the 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

[k8s-ci-robot]

Hi @rbjorklin. 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	23e7903
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-cluster-api-operator/deploys/67f5a05efc0f91000850b7be
😎 Deploy Preview	https://deploy-preview-780--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 site configuration.

[dmvolod]

/ok-to-test

[sathieu]

@rbjorklin Thanks for this. Following the same idea, can you add fetchConfig, manager.featureGates, additionalDeployments, manifestPatches, and additionalManifests configurable per provider?

[rbjorklin]

@rbjorklin Thanks for this. Following the same idea, can you add fetchConfig, manager.featureGates, additionalDeployments, manifestPatches, and additionalManifests configurable per provider?

manifestPatches and additionalManifests were already implemented in the referenced PR #638. I'll see if I can get the others added though.