operator-controller
operator-controller copied to clipboard
operator-framework
Follow-on to #235 Based on #232 **Background** As a user, I want to restrict when upgrades and installations occur. For instance, to off-hours (e.g. after 9pm) or on specific days...
> Follow least privilege principle and reduce confused deputy problems by limiting the scope of OLM v1’s permissions. Instead, have users provide a ServiceAccount with the necessary permissions to manage...
We have been working a lot on fine tuning the logic of the Extension controller recently. The major themes have been: - Make the updates of various status fields more...
**Description**: Enable operator controller to utilize a service account (SA) provided by the user during the creation of the Cluster Extension (CE). This change aims to limit the operator controller's...
# User story As an admin, when I have an installed ClusterExtension, I expect that the upgrade edges defined in the catalog (i.e. replaces, skips, and skipRange) will be honored....
## PRs - [x] #743 ## Docs - [ ] #744
# User story As a maintainer of OLMv1, I want to remove support for the prototype plain+v0 bundle type and other related code so that I can decrease the surface...
The intent is to remove this API and its controllers for the v1.0.0 release. Once we've released 1.0.0, we plan to re-introduce the Extension API and controllers.
There is a proposal for go to receive support for tool dependency management which might land as soon as Go 1.22: https://github.com/golang/go/issues/48429 Once it is available and our codebase is...
We currently have 2 jobs which upload code coverage to codecov: * unit-test * e2e But we also have `operator-developer-e2e` which was added more recently and it does not upload...