Looking at operatorhub.io, the top looks like this:
![image](https://user-images.githubusercontent.com/138397/148350284-a452184e-f691-4dd3-942c-91d941eecbe1.png)
My first-blush reaction was that operatorhub.io itself had been deprecated, which is an unfair reaction driven by my having lived through the github.com/helm/charts deprecation...
Anyway, I assume the underlying cause is that alphabetically, [
sorts before A
, and there's no rule preventing naming your operator to (intentionally or unintentionally) take advantage of that.
Putting [Deprecated]
at the start of the name of a deprecated operator's entry isn't ideal, but there isn't a "deprecated" field or similar in ClusterServiceVersion
v1alpha1 that could be used specifically for this.
Perhaps recognising a deprecated
value for the maturity
free-string field would work? Or perhaps this is something that should be at the channel level instead, to deprecate a whole operator, rather than a specific version?
Anyway, with that metadata being distinguished, then deprecated operators could be hidden by default, and searched as a separate axis, and the deprecation status could be made visible via something other than the name field.