To deploy in an air-gapped or offline environment, you'll need to mirror the images to your own internal registry, then override the respective image and image_version values via the spec on the AWX CR. There are some other threads about it, I'll try to summarize here:
```
---
apiVersion:
awx.ansible.com/v1beta1kind: AWX
metadata:
name: awx-demo
spec:
image: xxx
image_version: xxx
init_container_image: xxx
init_container_image_version: xxx
redis_image: xxx
redis_image_version: xxx
control_plane_ee_image: xxx
control_plane_ee_image_version: xxx
postgres_image: xxx
postgres_image_version: xxx
image_pull_secrets: <image-pull-secret-for-private-registry>
# ee_images
# ee_pull_credentials_secret: xxx
```
The tricky part though is that you need to specify the awx-operator image as well. Which can be done with kustomize. When you deploy the operator, you can have a kustomization.yaml file that looks like this:
```
```
I think that should do it.
FYI, the downstream AAP offering handles registry mirroring in a smoother way, more transparent to the user with Openshift. That might be something to look into if that is an option for you.
Thanks,
AWX Team