docs: add infomaniak third party provider

[M0NsTeRRR]

Hello,

Differences between mine and the official one :

• Distroless image: Only the binary, running rootless for enhanced security.
• Updated dependencies: Regularly maintained for reliability and security.
• Open collaboration: Issues enabled for community feedback and contributions.
• OCI-compatible artifacts: Helm chart and container images are published in OCI format and signed, making them easy to integrate with GitOps tools like Flux and ArgoCD.

Fix issue #1935

[cert-manager-prow]

[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 sgtcodfish for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

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

[netlify]

✅ Deploy Preview for cert-manager ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	ea84803
🔍 Latest deploy log	https://app.netlify.com/projects/cert-manager/deploys/6a313643b1f31100086b6974
😎 Deploy Preview	https://deploy-preview-2092--cert-manager.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.

[Copilot]

Pull request overview

Adds a third-party alternative Infomaniak DNS01 webhook link to the cert-manager DNS01 provider documentation (addressing issue #1935) so users can discover an externally maintained option alongside the existing official provider.

Changes:

• Add a new “third-party alternative” documentation link for an Infomaniak webhook implementation.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[wallrj-cyberark]

Thank you for the contribution. Rather than listing a second webhook with the same name, I would suggest contributing your improvements to the original Infomaniak webhook instead.

The improvements you describe (distroless image, rootless security context, updated dependencies, OCI artifacts) would benefit all existing users of that webhook. The original repository accepts external contributions — it has 14 merged PRs from community contributors. In fact, some of your stated improvements align with work already requested there:

• #5: "feat: add default security context" — directly related to your rootless/distroless changes
• There are also 5 open dependabot PRs for dependency updates that could use a reviewer

Listing two entries with the identical display name cert-manager-webhook-infomaniak would be confusing for readers, and the "(third-party alternative)" annotation does not resolve this — every entry in this list is third-party.

I would encourage you to open PRs upstream and, if the maintainers are unresponsive after a reasonable period, revisit the question of a separate listing at that point.

[M0NsTeRRR]

Hello,

Thank you for your input. However, I don’t agree with some parts of your conclusion. I thought about this before creating an alternative project and upstreaming the issue I addressed. The problem is the lack of dependency updates, which is on the maintainer’s side. Even if I reviewed it, the maintainer would still need to review it as well, especially regarding trustworthiness. I’ve already contacted Infomaniak support, provided them with what I did, and they said they would forward it to their appropriate team and I got no answer for now.

Also, like many users (and I assume you as well), before creating a PR for any project I contribute to, I first reach out to the maintainers to see if they’re interested in this kind of evolution. This way, I avoid wasting my time if they don’t agree. Since the issues are closed, I can’t do that.

Listing two entries with the identical display name cert-manager-webhook-infomaniak would be confusing for readers, and the "(third-party alternative)" annotation does not resolve this — every entry in this list is third-party.

Exactly, that’s why I also opened the issue first and created the PR in the meantime, it didn’t take much time.