Explain how to install cert-manager using Flux

[wallrj]

Preview: https://deploy-preview-1338--cert-manager-website.netlify.app/docs/installation/helm/#install-the-helm-chart-using-flux

I wanted to see for myself whether cert-manager can be installed using Flux and it seems to be quite straight forward, so I documented it here.

I used some of the settings -- such as --crds CreateReplace -- that @slam-wowx had used in: https://github.com/cert-manager/cert-manager/issues/6409.

xref:

• 320

• https://github.com/cert-manager/cert-manager/issues/2197
• https://github.com/cert-manager/cert-manager/issues/2380

[netlify[bot]]

✅ Deploy Preview for cert-manager-website ready!

Name	Link
🔨 Latest commit	c88984a7f1513b6478b1178acf696bff26e1a88a
🔍 Latest deploy log	https://app.netlify.com/sites/cert-manager-website/deploys/6544e7c51bd8b40008082f2e
😎 Deploy Preview	https://deploy-preview-1338--cert-manager-website.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.

[jetstack-bot]

@jsoref: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to [this](https://github.com/cert-manager/website/pull/1338#pullrequestreview-1710620043): >/lgtm Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[jetstack-bot]

@erikgb: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to [this](https://github.com/cert-manager/website/pull/1338#pullrequestreview-1710872281): >Added a couple of suggestions, but LGTM at it stands. > >/lgtm Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[jetstack-bot]

@hawksight: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to [this](https://github.com/cert-manager/website/pull/1338#issuecomment-1793691415): >I just ran through the flux installation and it worked perfectly. Thanks @wallrj - a good little intro to fluxcd for me. > >/lgtm > >Just a question for anyone who knows, did `fluxctl` become `flux` instead at some point? That tripped me up as I thought I had the CLI but turns out I did not. Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[jetstack-bot]

@hawksight: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to [this](https://github.com/cert-manager/website/pull/1338#pullrequestreview-1713952873): >I just ran through the flux installation and it worked perfectly. Thanks @wallrj - a good little intro to fluxcd for me. > >Just a question for anyone who knows, did `fluxctl` become `flux` instead at some point? That tripped me up as I thought I had the CLI but turns out I did not. > >/lgtm Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[erikgb]

Just a question for anyone who knows, did fluxctl become flux instead at some point? That tripped me up as I thought I had the CLI but turns out I did not.

I think fluxctl was the CLI tool for the deprecated Flux v1 - which became flux in the current Flux v2.

[inteon]

/lgtm

[jetstack-bot]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: hawksight

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](https://github.com/cert-manager/website/blob/master/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment