-
Notifications
You must be signed in to change notification settings - Fork 596
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
Not possible to specify custom AWX image without a version #1441
Comments
docker / podman images always have a tag associated with it (doesn't have to correspond to a specific AWX release version). for example, image_version could just be "myawx" because tags are required, we put up |
I do not quite see the point of your answers. Of course images always have a tag. I would like the AWX Operator to use the correct tag if I provide a different base image (one from a mirror which has the same tags as the upstream source). If I have to manually specify a tag, I would need to update that all the time in accordance with the operator version, which is not nice. |
@gendergap I found a workaround for using the default AWX version Tag while specifying a custom image/registry: The installer defaults use a lookup to an environment variable AWX:
spec:
image: harbor.example.net/cache.quay.io/ansible/awx
image_version: "{{ lookup('env', 'DEFAULT_AWX_VERSION') }}"
image_pull_policy: Always Confirmation from K8s events:
|
@justsomescripts Yes, I did the same in the end, but with a fallback to image_version: "{{ lookup('env', 'DEFAULT_AWX_VERSION') or 'latest' }}" # see https://github.com/ansible/awx-operator/issues/1441 I still feel this should not be necessary. |
I concur. It was also rather confusing for me, as I'd expect it to behave like that by default :) |
Please confirm the following
Bug Summary
The README gives the hint that one can change the default AWX
image
from quay.io/ansible/awx to one in a local mirror (useful in isolated company environments). After some experiments and code study, I came to the conclusion that this configuration is only pulled in if one at the same time overrides/specifies theimage_version
as well.AWX Operator version
2.2.1
AWX version
22.3.0
Kubernetes platform
kubernetes
Kubernetes/Platform version
1.20.11
Modifications
no
Steps to reproduce
Needing a local image in my mirror, I duly defined something like
Expected results
I would have wanted the Operator to contact my mirror and fetch the image from that (which in turn pulls it from quay.io).
Actual results
My mirror never got asked about this image, instead Kubernetes tried to fetch the default image from quay.io.
Additional information
I traced it to roles/installer/tasks/resources_configuration.yml#L227 where the custom image is only used if there is also a custom
image_version
given.This would work (at the moment)
But I of course don't want to use a static AWX version (nor
latest
, for that matter), but the one bundled with the current Operator version.Operator Logs
No response
The text was updated successfully, but these errors were encountered: