-
Notifications
You must be signed in to change notification settings - Fork 109
Update the OLM section to use CatalogSource and Operator Registry #37
Comments
@SamiSousa I've pushed the latest image for the samples memcached-operator at quay.io/operator-framework/sample-memcached-operator so we can use that if needed. |
Agree, the docs are mixing concepts of deploying the Operator using its manifests manually as well as using OLM to give it as CSV. While we plan to re-introduce CSV handling outside of a catalog the getting started guide should also show how to build a catalog. Referenced doc bug: openshift/openshift-docs#15158 |
Hi folks IMHO: The image Also, the steps to do it show be doc here; https://github.com/operator-framework/community-operators/blob/master/docs/testing-operators.md |
Hi @hasbro17, The OLM steps as its example are updated now. In this way, I think that we can close safely this one. However, please feel free to re-open and add here what we should be done to close it if you believe that any further action related to this issue still required. Also, I really think that would be a great idea we provide the docker images for the samples. So, I tracked this idea here operator-framework/operator-sdk-samples#88. Please, feel free to contribute with too. |
The getting-started guide currently has instructions for applying a CSV directly to a namespace. This isn't the expected user experience for installing an operator with OLM today.
As a follow up to #36 the instructions should be updated to:
quay.io/operator-framework/memcached-operator
based on the samples memcached-operator./cc @SamiSousa
The text was updated successfully, but these errors were encountered: