[OFFICIAL] cert-manager

Hi!

We (the cert-manager team) finally managed to have the “Verified” badge on Artifact Hub. Our next step is to become the “official” chart.

↓
Repository name	cert-manager*
Official packages	cert-manager, cert-manager-istio-csr
Project URL	http://cert-manager.io/
Source code URL	jetstack/cert-manager*, cert-manager/istio-csr

*the cert-manager project is currently hosted under the jetstack org, but we are in our way moving the project to the cert-manager org as part of the CNCF donation process.

Requirements:

• The repository has already obtained the Verified Publisher status.
• The user requesting the status is the publisher of the repository in Artifact Hub, or belongs to the organization publishing it.
• All official packages available in the repository provide a README.md file with some documentation that can be displayed on Artifact Hub.

Related:

• https://github.com/jetstack/cert-manager/issues/3513

FYI @simplyzee

[tegioz]

Hi @maelvls 👋

I’ve just noticed that you have published some alpha versions for your cert-manager chart.

This is fine, but I just wanted to let you know that Artifact Hub will offer users to install the latest version available from the installation modal, even if it’s a beta or alpha version. If that’s what you are intending to do, then everything is all right 🙂

Otherwise, you have two options:

• You can ignore packages matching certain patters from your repository metadata file. This way, alpha or beta packages won’t even be visible in Artifact Hub.

• You can mark the package as pre-release using the artifacthub.io/prerelease annotation. In this case, the alpha or beta version will be available but users will be warned that this is a pre-release version both in the installation modal and in the package view.

Hope this helps.-

[tegioz]

Done!