operator-controller icon indicating copy to clipboard operation
operator-controller copied to clipboard

Results 337 operator-controller issues
Sort by recently updated
recently updated
newest added

# Description Adds annotation driven internal bundle install for internal purposes (at least for now) to aid in the testing / validation of extension and revision status development P.S. this...

# Description The current BundleValidator is implemented almost as a framework, its a singleton that always exists in memory, and it feels a bit awkward to me. I was thinking...

do-not-merge/work-in-progress

**Description** The .spec.serviceAccount field in the ClusterExtension API is being deprecated. This field was originally introduced to enforce least privilege by requiring a user-provided ServiceAccount for managing extension content. However,...

A/C: - Detail minimal search API to list contents of all catalogs in cluster. - Evaluate methods of exposing the catalogd search API off cluster. (port-forwarding, nodeport, gateway) Background: The...

kind/design

Some E2E tests might still rely on external catalogs like **Community**, which we don't control. We should create a **mock Operator and Catalog** for testing and update the tests to...

In cases where the extension cannot be installed, the error message is getting added to most conditions. We should probably not propagate the error message to the deprecation conditions. For...

kind/bug

https://docs.google.com/document/d/1tX0fXYuflTpTal6z0TbNkrQ7SAkYIKxQj4cPjlFAh4Q/

### User story As a cluster administrator, I want to ensure that OLMv1 works seamlessly with existing cluster configurations, especially when cert-manager is installed. This includes ensuring that cert-manager dependencies...

kind/feature
lifecycle/frozen
epic
v1.x

### Discussed in https://github.com/operator-framework/operator-controller/discussions/168 Originally posted by **perdasilva** April 14, 2023 A [recent discussion](https://github.com/operator-framework/operator-controller/pull/142#discussion_r1165747298) in #142 raised a couple of questions around what our unit testing conventions ought to be:...

documentation
help wanted
good first issue
kind/documentation
size/M
priority/important-soon

As of #217, we have removed the `Ready` condition, and we added the `Installed` condition in #218 and `Resolved` condition in #213. We may want to consider another condition type...

good first issue