operator-controller
operator-controller copied to clipboard
operator-framework
https://github.com/operator-framework/operator-controller/actions/runs/5871742974/job/15921834994?pr=336#step:4:484 Looks like the culprit is that we're trying to `curl | sh` for a kustomize binary install and we're getting rate-limited by GitHub { curl -Ss \"[https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh\](https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh/)" | bash...
There are several places where we rely on bundle being an image. With the plan to support more types (such as git repos) we need to refactor operator controller to...
**Motivation**: Operator Catalog content from index images are converted into Entities (and variables) for deppy. However, right now the information needed for creation of Entities is fetched from a single,...
Now that we have this feature gate: https://github.com/operator-framework/operator-controller/blob/b8f36268517dc39280fe964d131a6e3ff7ac9335/pkg/features/features.go#L19 We should find a way to run E2E in CI with different states of feature gates. --- One option is to use...
It seems like we remove `installedBundleResource` and `resolvedBundleResource` from `Operator`'s status in case of errors. ## Steps to reproduce 1. Run the operators from master: ```bash make run ``` 1....
Example build [here](https://github.com/operator-framework/operator-controller/actions/runs/6408695345/job/17398260693?pr=433): ``` • [FAILED] [5.109 seconds] Operator Install when An operator is installed from an operator catalog [It] handles upgrade edges correctly /home/runner/work/operator-controller/operator-controller/test/e2e/install_test.go:177 Timeline >> STEP: creating a...
Mentioned in https://github.com/operator-framework/operator-controller/pull/411#discussion_r1332190866 by @joelanford: > > Follow-up: we probably should not ignore unavailable catalogs. If we do, we introduce non-determinism to resolution. > > If a Catalog that is...
What I did: 1. Created the operatorhubio `Catalog` 2. Created an `Operator` with `spec.packageName: prometheus` and `spec.version: 0.37.0` 3. Waited for an installation failure (due to 0.37.0 using non-v1 CRD)...
We have a soft commitment to time-based releases, but our [documented release process](https://github.com/operator-framework/operator-controller/blob/main/RELEASE.md) doesn't mention the cadence nor what we do if some items don't make the cut.
I was speaking with @joelanford, @ncdc and @oceanc80 and we got on the topic of Issue Triaging. The weekly meeting is called `OLM WG and Issue Triage Meeting` and we...