namespace/olm created
namespace/operators created
serviceaccount/olm-operator-serviceaccount created
clusterrole.rbac.authorization.k8s.io/system:controller:operator-lifecycle-manager created
clusterrolebinding.rbac.authorization.k8s.io/olm-operator-binding-olm created
deployment.apps/olm-operator created
deployment.apps/catalog-operator created
clusterrole.rbac.authorization.k8s.io/aggregate-olm-edit created
clusterrole.rbac.authorization.k8s.io/aggregate-olm-view created
unable to recognize "https://raw.githubusercontent.com/operator-framework/operator-lifecycle-manager/master/deploy/upstream/quickstart/olm.yaml": no matches for kind "OperatorGroup" in version "operators.coreos.com/v1"
unable to recognize "https://raw.githubusercontent.com/operator-framework/operator-lifecycle-manager/master/deploy/upstream/quickstart/olm.yaml": no matches for kind "OperatorGroup" in version "operators.coreos.com/v1"
unable to recognize "https://raw.githubusercontent.com/operator-framework/operator-lifecycle-manager/master/deploy/upstream/quickstart/olm.yaml": no matches for kind "ClusterServiceVersion" in version "operators.coreos.com/v1alpha1"
unable to recognize "https://raw.githubusercontent.com/operator-framework/operator-lifecycle-manager/master/deploy/upstream/quickstart/olm.yaml": no matches for kind "CatalogSource" in version "operators.coreos.com/v1alpha1"
Furthermore, the thing to consider is that for every operator in its installation guide step for installing OLM is included too e.g.
It explicitly specifies a specific version (the newest one) of it and uses a bash script to execute kubectl commands. Maybe everywhere this method should be recommended even in docs fixed in this PR.
Following step in the below instruction
leads to the below error
Definitions of CRDs are missing in a cluster, they have to be created previously as advised in docs of OLM https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/install/install.md#manual-installation thus I'm updating docs to include this step too.
Furthermore, the thing to consider is that for every operator in its installation guide step for installing OLM is included too e.g.
It explicitly specifies a specific version (the newest one) of it and uses a bash script to execute kubectl commands. Maybe everywhere this method should be recommended even in docs fixed in this PR.