Bug 1391971 - Don't expose 'latest' metric images on registry.access.redhat.com
Summary: Don't expose 'latest' metric images on registry.access.redhat.com
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Hawkular
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Troy Dawson
QA Contact: Peng Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-04 14:13 UTC by Matt Wringe
Modified: 2016-11-04 15:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 15:44:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Matt Wringe 2016-11-04 14:13:52 UTC
Description of problem:

We currently have metric images tagged with 'latest' in registry.access.redhat.com.

What is happening is that some users are specifically changing the image version from the one meant for their version of OpenShift to 'latest', which causes a bunch of problems.

If someone is running OCP 3.3 and they are using the 'latest' images, when OCP 3.4 is released they will automatically bring in the version meant for 3.4.

This can cause problems if we are using new functionality in 3.4 which is not available in 3.3.

It also causes problems if we need to update the templates for the new version, but the configurations they are using are meant for the older version.

Running the 'latest' images is not supported, but because they are there some users do end up changing their configuration to this. If we could remove this option by not exposing the 'lastest' images in the registry, then users cannot get into the problems associated with it.

Comment 1 Troy Dawson 2016-11-04 15:44:27 UTC
This is not a tagging issue but a user configuration issue.
If we removed "latest" then more things would break, including those customers because their pulls would fail.

We are encouraging customers to set their version to v<release>, such as v3.2, v3.3 or v3.4.

I'm marking this as closed, not a bug, but my recommendation is documentation.


Note You need to log in before you can comment on or make changes to this bug.