Bug 1652571
| Summary: | [RFE][kuryr] Default kuryr images are hosted in docker.io instead redhat's registry (and using latest) | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Eduardo Minguez <eminguez> |
| Component: | Installer | Assignee: | Luis Tomas Bolivar <ltomasbo> |
| Installer sub component: | openshift-ansible | QA Contact: | Jon Uriarte <juriarte> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | juriarte, ltomasbo, rbost |
| Version: | 3.11.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 3.11.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-01-14 05:31:27 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Eduardo Minguez
2018-11-22 11:56:05 UTC
I'm thinking about doing something similar to https://github.com/openshift/openshift-ansible/blob/master/roles/olm/defaults/main.yaml so depending on the openshift_deployment_type variable, it will pull the image from redhat's registry or upstream. *** Bug 1745195 has been marked as a duplicate of this bug. *** Verified in v3.11.156-1_2019-11-25.1 OCP puddle on OSP 13 2019-11-04.1 puddle. Kuryr images are now stored in red hat registry and tagged with 3.11: registry.redhat.io/openshift3/kuryr-controller:v3.11 registry.redhat.io/openshift3/kuryr-cni:v3.11 In dev phase we use registry.reg-aws.openshift.com registry: registry.reg-aws.openshift.com:443/openshift3/ose-kuryr-controller:v3.11 registry.reg-aws.openshift.com:443/openshift3/ose-kuryr-cni:v3.11 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0017 |