operator-controller
operator-controller copied to clipboard
operator-framework
When you create a `ClusterExtension` referencing a `ServiceAccount` with insufficient permissions to list and watch managed resources, we loop forever while waiting for the watches to successfully become established. In...
Currently, there is no support for creating a `ClusterExtension` that can install a bundle that is in a private registry and requires authentication. This epic is scoped for enabling that...
# User story Describe the user story or stories for this epic: - As a user, I expect to be able to define a ServiceAccount that OLM v1 uses to...
> [!WARNING] > This still needs some discussion with folks with deeper knowledge into what changes between served and stored versions are necessary. I will be facilitating some conversations around...
# Description This is an update to error messages received when trying to upgrade an operator, per #1022 ## Reviewer Checklist - [ ] API Go Documentation - [ ]...
In OLMv1, we plan to support the `registry+v1` bundle format in order to provide a means for migration from OLMv0. However, we recognize the many pain points and limitations of...
Today the install is done from `yamls` from the the release pages, which is less the ideal for end users. We should mimic the install process of OLMv0 (as far...
@joelanford and I have noticed that a few operators from the operatorhub.io catalog fail the CRD preflight checks on upgrades due to "unknown changes" having occurred. We should do some...
# Description WIP, because: - I'd like feedback on whether the reconciler() loop modularization seems good and whether the proposed logic flow changes match up with https://github.com/operator-framework/operator-controller/issues/1027 , which is...
Seems like a unit test on this with Bundle in/Chart out would be good. Just in case Helm bumps, etc, shift something on us _Originally posted by @bentito in https://github.com/operator-framework/operator-controller/pull/1032#discussion_r1673683851_
