Document how to deprecate an operator

[wallrj]

In #529 the hazelcast-operator has been deprecated by adding a [DEPRECATED] prefix to its name, but is this the recommended process?

On operatorhub.io, this has the effect of showing the deprecated operators first:

• Alphabetical sorting on operatorhub.io is putting deprecated operators first #549
• Alphabetical sorting on operatorhub.io is putting deprecated operators first operatorhub.io#13

Some of the documentation mentions a maturity: deprecated field / value pair, but does not elaborate further:

• https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/building-your-csv.md#operator-metadata
• https://docs.okd.io/4.9/operators/operator_sdk/osdk-generating-csvs.html#osdk-manually-defined-csv-fields_osdk-generating-csvs

(It is confusing that the word "maturity" is used elsewhere in reference to metadata.capabilities and Operator Capabilities)

I'd like some documentation recommending when and how to deprecate an operator.

[camilamacedo86]

@wallrj,

That is something that requires discussion, alignments and some effort.
But we will try to check it out and keep you updated. See my comment: #549 (comment)

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 30 days since being marked as stale.

[camilamacedo86]

The option to add a feature to address this requirement has been discussed into the EP: https://github.com/operator-framework/enhancements/pull/113/files