operator-registry
operator-registry copied to clipboard
Operator Registry runs in a Kubernetes or OpenShift cluster to provide operator catalog data to Operator Lifecycle Manager.
**Description of the change:** This PR is a port of https://github.com/joelanford/olm-index-graph as a new `opm index graph` subcommand. **Motivation for the change:** As an operator author, I need tooling for...
I have a kind cluster run and up and then, when I execute make e2e the following error is faced: ``` • Failure [0.002 seconds] Launch bundle /Users/camilamacedo/go/src/github.com/operator-framework/operator-registry/test/e2e/bundle_image_test.go:691 Deploy bundle...
The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for...
## Issue The `index database` pushed within the following image which is currently packaged as `CatalogSource` from olm release 0.14.1 cannot be read `quay.io/operator-framework/upstream-community-operators` The following command returns this error...
Issue summary: I downloaded a release of `opm` from the following location https://github.com/operator-framework/operator-registry/releases/tag/v1.13.0 for MacOS. I ran the following ``` $ opm version Version: version.Version{OpmVersion:"1.12.7", GitCommit:"bcf85b7", BuildDate:"2020-07-11T12:12:00Z", GoOs:"darwin", GoArch:"amd64"} ```...
There are several Dockerfiles in this repo. It would be helpful to have a comment at the top of each Dockerfile that gave some indication of the purpose for each...
It wasn't an error before but after operator-registry merged https://github.com/operator-framework/operator-registry/commit/065e51f2d66d4f44d9c32c158c1738c2fa765a05 it's an error. error: ``` time="2019-08-08T10:42:49Z" level=info msg="could not decode contents of file /registry/bundles.db into package: error converting YAML to...
Creating index image from scratch ``` $ /tmp/operator-test/bin/opm index add -u docker --bundles quay.io/operator_testing/aqua-operator:v1.0.1,quay.io/operator_testing/aqua-operator:v1.0.2 --tag quay.io/operator_testing/upstream-community-operators-index:latest --skip-tls INFO[0000] building the index bundles="[quay.io/operator_testing/aqua-operator:v1.0.1 quay.io/operator_testing/aqua-operator:v1.0.2]" INFO[0000] resolved name: quay.io/operator_testing/aqua-operator:v1.0.1 INFO[0000] fetched digest="sha256:10f7ada4950f9f74ec90ff957caa35812262c9e975aacc9dbca7e628539fd790"...
Trying to use the locally configured openshift image-registry route with 'opm registry add' commands today and the --skip-tls option doesn't seem to work. opm registry add -b default-route-openshift-image-registry.apps.test.dprince/openstack/openstack-cluster-bundle:v0.0.5 --skip-tls --container-tool...
Using quay.io/openshift/origin-operator-registry:latest when I have a chain of CSVs, for example `0.0.2, 0.0.3, 0.0.4, .... 1.0.0` where `0.0.2` is the first version and `1.0.0` is the latest and each version...