operator-controller
operator-controller copied to clipboard
operator-framework
In order to reduce the scope of what we are forced to support until a v2 release of OLM, should we proactively reject helm charts that ultimately include chart hooks...
Not few of us are struggling with the fact that sometimes one needs an operator in a given version despite all other versions in the catalog/channel. There are very low...
In the [clusterextension_controller.go](https://github.com/operator-framework/operator-controller/blob/208e584ab6be82d11eb0955b0553adbd2244a9fc/internal/controllers/clusterextension_controller.go#L325) we ask the underlying Helm client to upgrade a bundle. This may fail. Unfortunately, there are no error types for Helm upgrade [errors](https://www.google.com/url?q=https://github.com/helm/helm/issues/11156&sa=D&source=docs&ust=1719497497220368&usg=AOvVaw3cT5KcAMOUJyQNUqYBfVlS). Error messages could be...
In `internal/controllers/suite_test.go`: Nit: move the mocks to a separate package and/or file to make them easier to find? _Originally posted by @joelanford in https://github.com/operator-framework/operator-controller/pull/874#discussion_r1608877404_
The label selector used for both catalogd and operator-controller metrics services is: `control-plane: controller-manager`. Now that both catalogd and operator controller are running in the same namespace, that means both...
See: https://github.com/operator-framework/operator-controller/blob/f301f552978ed4997a09e04fbfccc586237461ee/cmd/manager/main.go#L180 This likely means a slight refactoring of the ImageRegistry implementation. Related: it probably makes sense to stop using the composite unpacker and instead just use `ImageRegistry` directly.
Now that catalogd and operator-controller share the same namespace, deployment of operator-controller should properly handle this redundancy and ensure that the version of the olmv1-system namespace from operator-controller is the...
The direct registry client during unpacking exits only when it is successful or when it encounters an error: https://github.com/operator-framework/rukpak/blob/352d42f1e390177aed8fedf0cfb0212d5e71bc71/pkg/source/image_registry.go#L34. Which means the `Unpacking` and `UnpackPending` statuses would never be reached....
Follow on to #205 Background: When reconciling operator CRs, the operator-controller builds a list of constraints based on operator CRs and attempts to solve those constraints by considering content available...
Follow-up to https://github.com/operator-framework/operator-controller/issues/747 Make room in the ClusterExtension API for other techniques for sourcing bundles (i.e. enable a future where bundles don't have to be sourced from a catalog)
