[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Request for a new generic release image tag on Docker hub

If I may add another request and summarize:

(1) Add an additional v1.2 tag pointing to the latest released 1.2.x
image. Doing the same for 1.3 even in alpha stage would help make it a
supported option to install with openshift-ansible. This will allow
users to specify a version to install with less precision, and a
version/release they might actually know beforehand.

(2) Add a v1.3.0 tag pointing to the latest alpha build. More
generally the rule here is to standardize on whatever is before the
first "-" in the output from "openshift version" as something we can
use to locate image tags, and rpm versions for use throughout the
cluster. I.e. v1.3.0-alpha.1-321-gb095e3a = safe to assume a tag of
v1.3.0 exists.

On Wed, Jun 15, 2016 at 5:04 PM, Scott Dodson <sdodson redhat com> wrote:
> On Wed, Jun 15, 2016 at 1:45 PM, Devan Goodwin <dgoodwin redhat com> wrote:
>> Would it be possible to have a new tag included when we push official
>> release images out to docker hub: i.e. "v1.2" for the latest image in
>> the 1.2 stream.
>> This would allow support for a new way to specify a generic release to
>> install in ansible inventories, rather than having to specify with
>> complete precision as you do today. (i.e. in the OSE case)
>> We've done this for OSE but I'd like to see it work for origin as well.
> +1 to this and it doesn't suffer from having to decide which versions
> are "stable" which seems to have been Clayton's objection when I asked
> for a "stable" tag to achieve the same end goal you're trying to
> achieve.
> Ultimately I'd settle for anything that got me a non ephemeral build,
> but v1.2 and v1.3 would be awesome.
> --
> Scott

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]