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

update the Outdated catalog in OLM addon #10768

Closed
kadel opened this issue Mar 10, 2021 · 2 comments · Fixed by #10947
Closed

update the Outdated catalog in OLM addon #10768

kadel opened this issue Mar 10, 2021 · 2 comments · Fixed by #10947
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@kadel
Copy link
Member

kadel commented Mar 10, 2021

I was wondering why my minikube instance is installing old operator versions.

Then I found out that the CatalogSource image in the OLM addon points to the SHA of the image that is several months old.

"UpstreamCommunityOperators": "operator-framework/upstream-community-operators:07bbc13@sha256:cc7b3fdaa1ccdea5866fcd171669dc0ed88d3477779d8ed32e3712c827e38cc0",

It might make sense for this one case to be an exception from #9884 and to use latest tag. Otherwise, every user will have to update the image refernce themself to pick up the latest changes in Operator Catalog.

@medyagh medyagh added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Mar 15, 2021
@medyagh medyagh changed the title Outdated catalog in OLM addon update the Outdated catalog in OLM addon Mar 15, 2021
@medyagh
Copy link
Member

medyagh commented Mar 15, 2021

@kadel thanks for this issue, I would be happy to accept a PR that updates the version to latest version,

by the way minikube addon has an option to provide your own image to the addon have u tried that ?
$ minikube addons enable --help

      --images='': Images used by this addon. Separated by commas.

here is the link to how to use this flag on the minikube website https://minikube.sigs.k8s.io/docs/handbook/addons/custom-images/

@kadel
Copy link
Member Author

kadel commented May 4, 2021

@medyagh Can you please reopen these issues?

#10947 updated OLM operators but it did not update the OLM catalog.

Description of the problem with OLM catalog

Problem is that the latest tagged version of OLM catalog image (https://quay.io/repository/operator-framework/upstream-community-operators?tab=tags) is 4 months old.

The latest tag gets frequent rebuilds but for security reasons, minikube can't just use latest

I've tried to pin down the upstream-community-operators image using hash.
But this doesn't work, as the image becomes unavailable after new latest rebuild. It looks like each new image rebuilds deletes the old layers, as they are not used in any tagged version

I'll try to contact OLM team to check what is the recommended way for referencing catalog images. Or if they are willing to start tagging and versioning catalog images.

Meanwhile, the only way to use the newest catalog image is this?

minikube addons enable olm --images "UpstreamCommunityOperators=operator-framework/upstream-community-operators:latest"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
2 participants