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

Follow up after merging operator-framework/catalogd#145: This is coming from Docker Hub, which is rate-limited, and can cause flakes. Can we find a registry container in quay (or some other better...

lifecycle/stale

Follow up after merging operator-framework/catalogd#145, context: Have you seen https://github.com/tilt-dev/ctlptl? Since we're already tilt-enabled, perhaps this is a reasonable tool to evaluate for our cluster setup purposes, especially since it...

lifecycle/stale

operator-framework/catalogd#196 Updated the catalog controller's unit tests which resulted in the removal of using `envtest` for unit testing purposes. It was called out as part of that PR that we...

lifecycle/stale

As mentioned in https://github.com/operator-framework/catalogd/pull/225#pullrequestreview-1814498162 we should add some form of CRD schema tests to ensure that the schemas have the proper validations and properly catch cases like operator-framework/catalogd#224

controller-runtime v0.18.x has an exportable http(s) server which we should use in place of the one in catalogd. Reference PR operator-framework/catalogd#263

Out of scope for this PR, but seeing this I don't think we need these permissions on pods anymore. we don't use a pod to unpack the catalog contents anymore...

I am getting this error on a fresh k8 cluster when installing the default catalog I am trying to install the operator-controller and it pulls in the default catalog but...

This might be a simpler approach (alpha in 1.30): https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/3962-mutating-admission-policies#use-case-set-a-label

v1.x
epic/catalog-selection

See [comment](https://github.com/operator-framework/catalogd/pull/379#discussion_r1765464884) >In this particular example, the contentURL is the important piece of information, and now, it's wrong with the service name update (https://github.com/operator-framework/catalogd/pull/402). The values of the status fields...

I created a ClusterCatalog with a private image from redhat.registry.io, but it hung for a while without any signal about what's going on.. ``` NAME LASTUNPACKED SERVING AGE redhat-community-operators 1s...

v1.x