Skip to content
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.

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

tag awx-ee images with corresponding awx image tags #125

Closed
fosterseth opened this issue Jun 29, 2022 · 11 comments
Closed

tag awx-ee images with corresponding awx image tags #125

fosterseth opened this issue Jun 29, 2022 · 11 comments
Assignees

Comments

@fosterseth
Copy link
Member

fosterseth commented Jun 29, 2022

Right now we just have latest but seems the community would appreciate having distinct tags for awx-ee to rely on. see ansible/awx-operator#965

@shanemcd had the idea of just tagging images with whatever the current awx image tag is each time we build awx-ee

@gundalow
Copy link

gundalow commented Jul 6, 2022

Seems like a useful thing

Need to work out where this should be documented (so folks know they can take advantage of it)

I think this would be a great item for The Bullhorn, I can walk you through that process.

@john-westcott-iv
Copy link
Member

Possibly related: #117

@sjpb
Copy link

sjpb commented Oct 6, 2022

This is critical - currently we can't even pin using the sha256 hash as apparently that changes if latest gets updated. E.g. yesterday latest could be referenced as quay.io/ansible/awx-ee@sha256:1b9564e397a5059b53d304a697fcc48250fb805caf828a8006ef799d69a8dd21, today it can't be as the hash is now 8c40540b25a8....

Surely:

  • latest should also be tagged with a version number e.g. 0.6.1 or whatever
  • released images should not be removed?

@Cl0udius
Copy link

We would also highly appreciate this.
As there were some problems in the last weeks with latest state a version tag for the 21.x compatible versions would be very useful.

@r0b1ndot
Copy link

We would also highly appreciate this.
Since we want to better control the lifecycle of our deployments, so this would be very useful.

@texasbobs
Copy link

Just wanted to add to this... we have a requirement to not use latest so if other tags could be created, that would help.

@codepoke-kk
Copy link

Add me to the list on this one. I'm not allergic to the word "latest", but I am allergic to a situation where the stack breaks against a numbered version. Whenever a working stack is broken such that a new EE is needed, someone should drive a stake in the ground with a tagged version so we can be sure it won't change under us. I cannot verify, but I have to assume there was a moment in time when the "latest" EE just suddenly stopped working on a simple restart, and that's a show-stopper.

@relrod
Copy link
Member

relrod commented Feb 2, 2023

This has been implemented as of this past AWX release. Closing this now.

@relrod relrod closed this as completed Feb 2, 2023
@gannaramu
Copy link

gannaramu commented Apr 5, 2023

@relrod container images are tagged but the corresponding tags are not present on this git repo.

@AndrewSav
Copy link

AndrewSav commented Apr 5, 2023

Yeah, was also surprised by this. Should we open a new issue to track that, or just re-open that one? Obviously the image tag needs to correspond to source control tag so we know which version of the source the image is built from.

@gannaramu
Copy link

@relrod any update on this request?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests