Please confirm the following

• I agree to follow this project's code of conduct.
• I have checked the current issues for duplicates.
• I understand that the AWX Operator is open source software provided for free and that I might not receive a timely response.

Bug Summary

While image_version is based on DEFAULT_AWX_VERSION environment variable that gets injected during staging process, I have found out, that control_plane_ee_image via _control_plane_ee_image is still hardcoded to awx-ee:latest.
This can cause unexpected behaviour, when used with default EE (which is also awx-ee:latest), as the default EE seems to be pulled with each job run when there is an update to that tag.
After such unaware change of awx-ee:latest image, when the awx-task pod terminates for whatever reason, it will start with never code as intended.

As now finally awx-ee images are tagged with tags matching awx, I would recommend to use the same tag on ee as well.

For me, as a workaround, i use following:

spec:
...
  init_container_image: "{{ _image }}-ee"
  init_container_image_version: "{{ _image_version }}"
  control_plane_ee_image: "{{ _image }}-ee:{{ _image_version }}"
...

but this should not be needed if implemented properly.

AWX Operator version

2.3.0

AWX version

22.4.0

Kubernetes platform

other (please specify in additional information)

Kubernetes/Platform version

k3d 5.4.3, kubernetes version v1.23.6+k3s1

Modifications

no

Steps to reproduce

• install default k3d
• wait for awx-ee:latest tag to move
• run any job, that will fetch updated awx-ee:latest
• delete awx-task pod
• new awx-task will have changed controlplane image

Expected results

After installation of AWX via awx-operator, no image should change automatically until deployment of new awx-operator version

Actual results

awx-ee and control_plane images might get changed when latest tag moves

Additional information

No response

Operator Logs

No response