h4. What * The operator should appear Releases were made for the OLM * Allow users install the operator by OLM * We should be able to deploy the operator inr9ly tests without following all steps described in https://operatorhub.io/contribute
h4. Why In order to allow the Operator to work with the "new MDC".
h4. How * See the POC steps: README( https:// issues.jboss.org/browse/AEROGEAR-8901 * CSV: https:// github.com/ operator-framework aerogear / operator mobile - lifecycle security - manager/blob/master/Documentation/design/building service - your operator#tags - csv release) . md * CatalogSource: See https://github.com/ operator-framework aerogear / operator mobile - manifests and https://github.com/operator security - framework/operator service - lifecycle-manager operator / blob/master/Documentation/design/architecture releases
h4 . md#catalog-operator How At this moment we can have 2 approaches to solve it.
* Subscription: https://github 1 . com By remove all tags / operator-framework/operator-lifecycle-manager/blob/master/Documentation/design/architecture.md#subscription-control-loop releases and do a new one 0.1.0 * OperatorGroup PS : Do not forget to update the version.go file.< https://github.com/ operator-framework aerogear / operator mobile - lifecycle security - manager service-operator /blob/master/ Documentation version / design/operatorgroups version . md go> OR
* 2. Update the CHANGELOG and version.go file with the respective info since these are the missing steps. |
|