search

operator-framework / operator-controller

Apache License 2.0
29 stars 47 forks source link

[Helm Integration] Include Catalog information with helm labels and introduce catalog filtering during Resolution #873

Open dtfranz opened 1 month ago

dtfranz commented 1 month ago

We should include the catalog in which the bundle was resolved from as well (and support catalog filtering during resolution). There are no guarantees that a bundle is only present/served from a single catalog on the cluster. For example, on OpenShift the Red Hat Operator Catalog and Community Operator Catalog both have some of the same entries (loki-operator is one that I found relatively quickly).

I'm fine with this being done as a follow up if we don't already have support for filtering bundles by catalog name during resolution, but if we do we should ensure we track that information as part of the labels as added by this postrenderer as well IMO.

_Originally posted by @everettraven in https://github.com/operator-framework/operator-controller/pull/846#discussion_r1607133273_

m1kola commented 1 month ago

Not sure if it has been documented somewhere, but I believe it was a deliberate UX decision. User specifies a package name and we install a package with that name which is available on the cluster. So it doesn't matter from which catalog the content is coming from. If we want to stick with this UX - then we do not need filtering by catalog name.

@joelanford might be able to add more context for this.