Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I am getting error while installing OLM #854

Closed
smiklosovic opened this issue May 9, 2019 · 2 comments
Closed

I am getting error while installing OLM #854

smiklosovic opened this issue May 9, 2019 · 2 comments

Comments

@smiklosovic
Copy link

smiklosovic commented May 9, 2019

I am running on current master

kubectl create -f deploy/upstream/manifests/latest/

I am running k8s 1.14

I am getting

namespace/olm created
namespace/operators created
clusterrole.rbac.authorization.k8s.io/system:controller:operator-lifecycle-manager created
serviceaccount/olm-operator-serviceaccount created
clusterrolebinding.rbac.authorization.k8s.io/olm-operator-binding-olm created
customresourcedefinition.apiextensions.k8s.io/clusterserviceversions.operators.coreos.com created
customresourcedefinition.apiextensions.k8s.io/installplans.operators.coreos.com created
customresourcedefinition.apiextensions.k8s.io/subscriptions.operators.coreos.com created
customresourcedefinition.apiextensions.k8s.io/catalogsources.operators.coreos.com 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
customresourcedefinition.apiextensions.k8s.io/operatorgroups.operators.coreos.com created
configmap/olm-operators created
unable to recognize "deploy/upstream/manifests/latest/0000_50_olm_12-olm-operators.catalogsource.yaml": no matches for kind "CatalogSource" in version "operators.coreos.com/v1alpha1"
unable to recognize "deploy/upstream/manifests/latest/0000_50_olm_13-operatorgroup-default.yaml": no matches for kind "OperatorGroup" in version "operators.coreos.com/v1"
unable to recognize "deploy/upstream/manifests/latest/0000_50_olm_13-operatorgroup-default.yaml": no matches for kind "OperatorGroup" in version "operators.coreos.com/v1"
unable to recognize "deploy/upstream/manifests/latest/0000_50_olm_14-packageserver.subscription.yaml": no matches for kind "Subscription" in version "operators.coreos.com/v1alpha1"
unable to recognize "deploy/upstream/manifests/latest/0000_50_olm_18-upstream-operators.catalogsource.yaml": no matches for kind "CatalogSource" in version "operators.coreos.com/v1alpha1"

I have provisioned my own Kubernetes cluster from scratch

@smiklosovic
Copy link
Author

I did this and it works

kubectl apply -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.9.0/olm.yaml

@jaemyunlee
Copy link

jaemyunlee commented May 9, 2020

I leave a comment for someone who read this with the same issue.

You can check below
https://github.com/operator-framework/operator-lifecycle-manager/issues/746#issuecomment-497474702

It worked fine when I created crds first like below

kubectl apply -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.14.1/crds.yaml
kubectl apply -f https://github.com/operator-framework/operator-lifecycle-manager/releases/download/0.14.1/olm.yaml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants