New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Upstream quickstart and latest manifests should deploy same OLM image #747

Closed

ron1 opened this issue Mar 11, 2019 · 1 comment

Contributor

ron1 commented Mar 11, 2019

Upstream quickstart (https://github.com/operator-framework/operator-lifecycle-manager/blob/master/deploy/upstream/quickstart/olm.yaml) deploys OLM image quay.io/openshift/origin-operator-lifecycle-manager:latest while Upstream manifests (https://github.com/operator-framework/operator-lifecycle-manager/blob/master/deploy/upstream/manifests/0.8.1/0000_50_olm_06-olm-operator.deployment.yaml) deploys OLM image quay.io/coreos/olm@sha256:995a181839f301585a0e115c083619b6d73812c58a8444d7b13b8e407010325f.

These two installation methods should be consistent and deploy the same images.

njhale mentioned this issue

refactor(images): use operator-framework namespace for all olm images #752

Merged

Member

njhale commented Mar 21, 2019

@ron1 Thanks for reporting! #752 and #771 resolve this issue. Closing this out.

njhale closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment