1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00

Correct spec.maturity definition and add spec.capabilities

Correct spec.maturity definition and add spec.capabilities
This commit is contained in:
Matt Dorn
2020-05-19 15:33:26 -05:00
committed by openshift-cherrypick-robot
parent 3dc6ec2a76
commit f0d33f5f52

View File

@@ -22,6 +22,10 @@ generation when a lack of data in any of the required fields is detected.
|A unique name for this CSV. Operator version should be included in the name to
ensure uniqueness, for example `app-operator.v0.1.1`.
|`metadata.capabilities`
|The Operator's capability level according to the Operator maturity model, for
example `Seamless Upgrades`.
|`spec.displayName`
|A public name to identify the Operator.
@@ -75,8 +79,8 @@ application being managed, each with a `name` and `url`.
a `mediatype`.
|`spec.maturity`
|The Operator's capability level according to the Operator maturity model, for
example `Seamless Upgrades`.
|The level of maturity the software has achieved at this version, for
example `alpha`, `beta`, `stable`.
|===
Further details on what data each field above should hold are found in the