Consider listing operator in Artifact Hub

[tegioz]

Hi! 👋🏻

Have you considered listing the azure-service 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 🙂

[babbageclunk]

Once we have an operator bundle for v2 we'll look into this.

[matthchr]

must be done after #1967 is done

[matthchr]

We'd still like to do this but still need to do #1967 first.

[matthchr]

No change in status from above

[matthchr]

No change in status from above

[matthchr]

From the linked issue #3718:
https://artifacthub.io/packages/search?ts_query_web=azure+service+operator&sort=relevance&page=1 doesn't show us.

Example of how KEDA has it set up: https://artifacthub.io/packages/helm/kedacore/keda

@tomkerkhove expressed interest in this. Have closed the other issue and will use this one to track this ask going forward.

[tomkerkhove]

Feel free to assign to me

[matthchr]

Feel free to assign to me

Done!

[matthchr]

Pulling this into 2.10.0

As part of this, we should consider cleaning this up as well now that ASOv1 is deprecated: https://artifacthub.io/packages/olm/community-operators/azure-service-operator