-
Bug
-
Resolution: Obsolete
-
Medium
-
None
-
OSC 1.6.0
-
None
-
None
Description
Most of the downstream images are based on `latest` version of UBI. We decided already we'd only use explicit numerical versions for several reasons :
- avoid issues with modified deps, missing package or other unexpected change that can come with a latest version
- clearer to quickly know what version is being used
Steps to reproduce
1. checkout the midstream operator repo
2. git grep ubi.*:latest
Expected result
Nothing.
Actual result
distgit/containers/osc-cloud-api-adaptor-webhook/Dockerfile.in:FROM registry.redhat.io/ubi9/ubi-minimal:latest
distgit/containers/osc-cloud-api-adaptor/Dockerfile.in:FROM registry.redhat.io/ubi9/ubi-minimal:latest
distgit/containers/osc-monitor/Dockerfile.in:FROM registry.redhat.io/ubi9/ubi-minimal:latest AS builder
distgit/containers/osc-monitor/Dockerfile.in:FROM registry.redhat.io/ubi9/ubi-minimal:latest
distgit/containers/osc-must-gather/Dockerfile.in:#@follow_tag(registry.redhat.io/ubi8/ubi:latest)
distgit/containers/osc-must-gather/Dockerfile.in:FROM registry.redhat.io/ubi8/ubi:latest
distgit/containers/osc-operator/Dockerfile.in:FROM registry.redhat.io/ubi9/ubi-minimal:latest
distgit/containers/osc-podvm-payload/Dockerfile.in:FROM registry.access.redhat.com/ubi9/ubi:latest as builder
distgit/containers/osc-podvm-payload/Dockerfile.in:FROM registry.redhat.io/ubi9/ubi-minimal:latest
Impact
Confusion for the team.
Env
OSC 1.6.0