From 051500fff1423575a703974af8fdbe3f4997d30d Mon Sep 17 00:00:00 2001 From: Marcelo Moreira de Mello Date: Wed, 21 Apr 2021 17:51:35 -0400 Subject: [PATCH] updated documentation --- README.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 6dc6c6fd..3f6478ab 100644 --- a/README.md +++ b/README.md @@ -258,7 +258,7 @@ There are a few variables that are customizable for awx the image management. | Name | Description | Default | | --------------------------| -------------------------- |------------------------------| | tower_image | Path of the image to pull | quay.io/ansible/awx | -| tower_image_version | Image version to pull | 19 | +| tower_image_version | Image version to pull | 19.0.0 | | tower_image_pull_policy | The pull policy to adopt | IfNotPresent | | tower_image_pull_secret | The pull secret to use | '' | | tower_ee_images | A list of EEs to register | quay.io/ansible/awx-ee:0.1.1 | @@ -280,6 +280,15 @@ spec: image: myorg/my-custom-awx-ee ``` +**Note**: The `tower_image` and `tower_image_version` are intended for local mirroring scenarios. + + +| Operator Version | Suppported AWX version | +| -------------------| -------------------------- | +| 0.0.7 and older | >= 17.0.0 | +| 0.0.8 and later | >= 18.0.0 | + + #### Privileged Tasks Depending on the type of tasks that you'll be running, you may find that you need the task pod to run as `privileged`. This can open yourself up to a variety of security concerns, so you should be aware (and verify that you have the privileges) to do this if necessary. In order to toggle this feature, you can add the following to your custom resource: