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

[epic] ClusterExtension supports selecting from specific catalogs #968

Open
joelanford opened this issue Jun 24, 2024 · 0 comments
Open
Labels
epic v1.x Issues related to OLMv1 features that come after 1.0

Comments

@joelanford
Copy link
Member

joelanford commented Jun 24, 2024

We intentionally emit resolution errors when a ClusterCatalog is not unpacked and usable. The reason is to give cluster admins a way to reason about what resolution will give them without having to worry about the state of a particular catalog when a reconcile happens, which is not really something they can easily control.

These semantics are similar to the behavior in OLMv0, and there have been some complaints about it. For example, "I want to install CNV, I don't care if the community catalog is having issues".

In order to solve this problem, I think we need to have a knob on the ClusterExtension API to allow users to select which ClusterCatalogs to resolve from (likely using a label selector)

Originally posted by @joelanford in #965 (comment)

@joelanford joelanford added epic v1.x Issues related to OLMv1 features that come after 1.0 labels Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic v1.x Issues related to OLMv1 features that come after 1.0
Projects
Status: No status
Development

No branches or pull requests

1 participant