-
Notifications
You must be signed in to change notification settings - Fork 542
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
Installation on minikube 1.13.0 does not pull in packages from the default catalog source #1796
Comments
I can reproduce this. The catalog pod is crashlooping on OOM, but I don't know what is choosing these limits (the catalog operator only sets resource requests):
|
On closer inspection... the minikube olm addon is using a fairly old digest. There were resource limits on catalog pods created at that time: operator-lifecycle-manager/pkg/controller/registry/reconciler/reconciler.go Lines 130 to 139 in 12c06cf
|
looks like the workaround is |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
The OLM team is not responsible for maintaining the We had attempt to update the manifests used in this command to a newer version, but broke minikube's e2e tests:
Please submit a bug against the minikube repository. |
Bug Report
What did you do?
I installed OLM on minikube using two different approaches (both with the same result):
minikube addons enable olm
What did you expect to see?
Operators listed when I run
k get packagemanifest -A
What did you see instead? Under which circumstances?
It says "No resources found". I was under the impression that the default catalog source that gets created on installation would pull in operators from operatorhub.io. The spec for the generated catalog source is:
Environment
Possible Solution
Additional context
The logs on the catalog operator repeat the text:
The text was updated successfully, but these errors were encountered: