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

Unable to use OLM to create operator in kubernetes native cluster #1660

Closed
nataraj24 opened this issue Jul 21, 2020 · 2 comments
Closed

Unable to use OLM to create operator in kubernetes native cluster #1660

nataraj24 opened this issue Jul 21, 2020 · 2 comments

Comments

@nataraj24
Copy link

nataraj24 commented Jul 21, 2020

Type of question

  1. How to use OLM to create operator in native kubernetes cluster? i am run OLM being corporate proxy.
  2. can i deploy operator using olm without publishing operator to operatorhubio?

getting below error when i try to deploy operator-group, subscription, csv
E0721 10:14:34.138232 1 queueinformer_operator.go:290] sync "test" failed: {test-operator alpha {operatorhubio-catalog olm}} not found: rpc error: code = Unknown desc = no entry found for test-operator alpha

Question

What did you do?
using operator-sdk generated csv for my operator.

What did you expect to see?
should be able to deploy operator

What did you see instead? Under which circumstances?
E0721 10:14:34.138232 1 queueinformer_operator.go:290] sync "test" failed: {test-operator alpha {operatorhubio-catalog olm}} not found: rpc error: code = Unknown desc = no entry found for test-operator alpha

Environment

  • operator-lifecycle-manager version: 1.15.1
  • Kubernetes version information:v1.16.8-eks-e16311
  • Kubernetes cluster kind: Native Kubernetes cluster

Additional context
Add any other context about the question here.
i am able to run the operator without OLM. trying use OLM to install operator and unable to use it.

@flickerfly
Copy link
Contributor

flickerfly commented Jul 23, 2020

This error is looking in the operatorhubio-catalog's records for an alpha channel of test-operator. It seems like it can't find it. Could you have another catalog?

kubectl get packagemanifest will show you all the packages in your cluster and which catalog they are in. Check that out. Then you can get a specific package manifest to see if you have what you want.

You can also use grpcurl to query the catalog as long as it is a grpc type catalog. A couple other types exist, but if you are using them you'll know.

EDIT: Rereading your question. Yes, you can deploy an operator without a catalog by using the manifests in the deploy directory to create the SA/Role/RoleBinding and Deployment for your operator or by passing the generated CSV directly to the cluster to trigger OLM to do it for you. I forget how that's done exactly, but I have done it. It may have been as simple as kubectl create -f mycsv.yaml.

@nataraj24
Copy link
Author

thank you @flickerfly information.

Finally i was able to host private catalog registry with only my operator and i was able use OLM to install the operators

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