Consider listing operator in Artifact Hub

[tegioz]

Hi! 👋🏻

Have you considered listing the hpe-csi operator directly in Artifact Hub?

At the moment it is already listed there, because the Artifact Hub team has added the community-operators repository. However, listing it yourself directly has some benefits:

• You add your repository once, and new versions (or even new operators) committed to your git repository will be indexed automatically and listed in Artifact Hub, with no extra PRs needed.
• You can display the Verified Publisher label in your operators, increasing their visibility and potentially the users' trust in your content.
• Increased visibility of your organization in urls and search results. Users will be able to see your organization's description, a link to the home page and search for other content published by you.
• If something goes wrong indexing your repository, you will be notified and you can even inspect the logs to check what went wrong.

If you decide to go ahead, you just need to sign in and add your repository from the control panel. You can add it using a single user or create an organization for it, whatever suits your needs best.

You can find some notes about the expected repository url format and repository structure in the repositories guide. There is also available an example of an operator repository already listed in Artifact Hub in the documentation. Operators are expected to be packaged using the format defined in the Operator Framework documentation to facilitate the process.

Please let me know if you have any questions or if you encounter any issue during the process 🙂

[datamattsson]

@tegioz thank you for letting us consider hosting the HPE CSI Operator directly on AH. We see a broader adoption of our Helm chart today and put emphasis on that deployment method. If we see broader adoption of OLM outside of OpenShift we will certainly reconsider.

On that note. On AH today, our operator is listed as "Community Operator", derived from operatorhub.io. Is there any plans on including the OpenShift status of an Operator? The HPE CSI Operator for Kubernetes is a Certified Operator for OpenShift.

[tegioz]

@tegioz thank you for letting us consider hosting the HPE CSI Operator directly on AH. We see a broader adoption of our Helm chart today and put emphasis on that deployment method. If we see broader adoption of OLM outside of OpenShift we will certainly reconsider.

Makes sense, thanks 👍

On that note. On AH today, our operator is listed as "Community Operator", derived from operatorhub.io. Is there any plans on including the OpenShift status of an Operator? The HPE CSI Operator for Kubernetes is a Certified Operator for OpenShift.

Adding an OpenShift Certified badge for operators sounds like a nice feature to me, we should do that 🙂. That'd be based on the certified annotation in the CSV, right?

[datamattsson]

Adding an OpenShift Certified badge for operators sounds like a nice feature to me, we should do that 🙂. That'd be based on the certified annotation in the CSV, right?

I believe so, I examined some lower standing operators and they have certified set to false.