Document the need for quotes on pg secret port value

.github/dependabot.yml

@@ -1,23 +0,0 @@
-version: 2
-updates:
-  - package-ecosystem: "pip"
-    directory: "/docs"
-    groups:
-      dependencies:
-        patterns:
-          - "*"
-    schedule:
-      interval: "weekly"
-    labels:
-      - "component:docs"
-      - "dependencies"
-  - package-ecosystem: "github-actions"
-    directory: "/"
-    groups:
-      dependencies:
-        patterns:
-          - "*"
-    schedule:
-      interval: "weekly"
-    labels:
-      - "dependencies"

.github/workflows/ci.yaml

@@ -4,24 +4,21 @@ name: CI
 
 on:
   pull_request:
+    branches: [devel]
+
   push:
+    branches: [devel]
 
 jobs:
   molecule:
     runs-on: ubuntu-latest
     name: molecule
-    strategy:
-      matrix:
-        ansible_args:
-          - --skip-tags=replicas
-          - -t replicas
     env:
-      DOCKER_API_VERSION: "1.41"
-      DEBUG_OUTPUT_DIR: /tmp/awx_operator_molecule_test
+      DOCKER_API_VERSION: "1.38"
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v2
 
-      - uses: actions/setup-python@v5
+      - uses: actions/setup-python@v2
         with:
           python-version: "3.8"
 
@@ -38,23 +35,58 @@ jobs:
           MOLECULE_VERBOSITY: 3
           PY_COLORS: '1'
           ANSIBLE_FORCE_COLOR: '1'
-          STORE_DEBUG_OUTPUT: true
         run: |
           sudo rm -f $(which kustomize)
           make kustomize
-          KUSTOMIZE_PATH=$(readlink -f bin/kustomize) molecule test -s kind -- ${{ matrix.ansible_args }}
-
-      - name: Upload artifacts for failed tests if Run Molecule fails
-        if: failure()
-        uses: actions/upload-artifact@v4
+          KUSTOMIZE_PATH=$(readlink -f bin/kustomize) molecule test -s kind
+  helm:
+    runs-on: ubuntu-latest
+    name: helm
+    steps:
+      - uses: actions/checkout@v2
         with:
-          name: awx_operator_molecule_test
-          path: ${{ env.DEBUG_OUTPUT_DIR }}
+          fetch-depth: 0
+
+      - name: Create k8s Kind Cluster
+        uses: helm/kind-action@v1.2.0
+
+      - name: Build operator image and load into kind
+        run: |
+          IMG=awx-operator-ci make docker-build
+          kind load docker-image --name chart-testing awx-operator-ci
+
+      - name: Patch pull policy for tests
+        run: |
+          kustomize edit add patch --path ../testing/pull_policy/Never.yaml
+        working-directory: config/default
+
+      - name: Build and lint helm chart
+        run: |
+          IMG=awx-operator-ci make helm-chart
+          helm lint ./charts/awx-operator
+
+      - name: Install kubeval
+        run: |
+          mkdir tmp && cd tmp
+          wget https://github.com/instrumenta/kubeval/releases/latest/download/kubeval-linux-amd64.tar.gz
+          tar xf kubeval-linux-amd64.tar.gz
+          sudo cp kubeval /usr/local/bin
+        working-directory: ./charts
+
+      - name: Run kubeval
+        run: |
+          helm template -n awx awx-operator > tmp/test.yaml
+          kubeval --strict --force-color --ignore-missing-schemas tmp/test.yaml
+        working-directory: ./charts
+
+      - name: Install helm chart
+        run: |
+          helm install --wait my-awx-operator --namespace awx --create-namespace ./charts/awx-operator
   no-log:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout sources
-        uses: actions/checkout@v4
+        uses: actions/checkout@v2
 
       - name: Check no_log statements
         run: |
@@ -65,5 +97,3 @@ jobs:
             echo "${no_log}"
             exit 1
           fi
-  nox-sessions:
-    uses: ./.github/workflows/reusable-nox.yml

.github/workflows/devel.yaml

@@ -11,38 +11,17 @@ jobs:
     runs-on: ubuntu-latest
     name: Push devel image
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v2
 
-      - name: Fail if QUAY_REGISTRY not set
+      - name: Build Image
         run: |
-          if [[ -z "${{ vars.QUAY_REGISTRY }}" ]]; then
-            echo "QUAY_REGISTRY not set. Please set QUAY_REGISTRY in variable GitHub Actions variables."
-            exit 1
-          fi
+          IMG=awx-operator:devel make docker-build
 
-      - name: Log into registry ghcr.io
-        uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567    # v3.3.0
+      - name: Push To Quay
+        uses: redhat-actions/push-to-registry@v2.1.1
         with:
-          registry: ghcr.io
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-
-
-      - name: Log into registry quay.io
-        uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567    # v3.3.0
-        with:
-          registry: ${{ vars.QUAY_REGISTRY }}
+          image: awx-operator
+          tags: devel
+          registry: quay.io/ansible/
           username: ${{ secrets.QUAY_USER }}
           password: ${{ secrets.QUAY_TOKEN }}
-
-
-      - name: Build and Store Image @ghcr
-        run: |
-          IMG=ghcr.io/${{ github.repository }}:${{ github.sha }} make docker-buildx
-
-
-      - name: Publish Image to quay.io
-        run: |
-          docker buildx imagetools create \
-            ghcr.io/${{ github.repository }}:${{ github.sha }} \
-            --tag ${{ vars.QUAY_REGISTRY }}/awx-operator:devel

.github/workflows/feature.yml

@@ -8,10 +8,10 @@ on:
 
 jobs:
   release:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-18.04
     name: Push devel image
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3
         with:
           fetch-depth: 0  # needed so that git describe --tag works
 
@@ -29,6 +29,25 @@ jobs:
         run: |
           echo "IMAGE_TAG_BASE=ghcr.io/${OWNER_LC}/awx-operator" >>${GITHUB_ENV}
 
+      - name: Set ARCH environment variable
+        run: |
+          echo "ARCH=$(case $(uname -m) in x86_64) echo -n amd64 ;; aarch64) echo -n arm64 ;; *) echo -n $(uname -m) ;; esac)" >>${GITHUB_ENV}
+
+      - name: Set OS environment variable
+        run: |
+          echo "OS=$(uname | awk '{print tolower($0)}')" >>${GITHUB_ENV}
+
+      - name: Install operator-sdk
+        run: |
+          echo "Installing operator-sdk ${OPERATOR_SDK_DL_URL}" && \
+          curl -LO ${OPERATOR_SDK_DL_URL}/operator-sdk_${OS}_${ARCH} && \
+          chmod +x operator-sdk_${OS}_${ARCH} && \
+          sudo mkdir -p /usr/local/bin/ && \
+          sudo mv operator-sdk_${OS}_${ARCH} /usr/local/bin/operator-sdk && \
+          operator-sdk version
+        env:
+          OPERATOR_SDK_DL_URL: https://github.com/operator-framework/operator-sdk/releases/download/v1.26.0
+
       - name: Log in to registry
         run: |
           echo "${{ secrets.GITHUB_TOKEN }}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin

.github/workflows/label_issue.yml

@@ -14,7 +14,7 @@ jobs:
 
     steps:
       - name: Label Issue - Needs Triage
-        uses: github/issue-labeler@v3.4
+        uses: github/issue-labeler@v2.4.1
         with:
           repo-token: "${{ secrets.GITHUB_TOKEN }}"
           not-before: 2021-12-07T07:00:00Z
@@ -26,8 +26,8 @@ jobs:
     runs-on: ubuntu-latest
     name: Label Issue - Community
     steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-python@v5
+      - uses: actions/checkout@v2
+      - uses: actions/setup-python@v4
       - name: Install python requests
         run: pip install requests
       - name: Check if user is a member of Ansible org

.github/workflows/label_pr.yml

@@ -12,18 +12,10 @@ jobs:
     runs-on: ubuntu-latest
     name: Label PR - Community
     steps:
-      - uses: actions/checkout@v4
-
-      - uses: actions/setup-python@v5
-
-      - name: Create a virtual environment
-        run: python3 -m venv venv
-
-      - name: Activate virtual environment and install dependencies
-        run: |
-          source venv/bin/activate
-          pip3 install requests
-
+      - uses: actions/checkout@v2
+      - uses: actions/setup-python@v4
+      - name: Install python requests
+        run: pip install requests
       - name: Check if user is a member of Ansible org
         uses: jannekem/run-python-script-action@v1
         id: check_user
@@ -40,7 +32,6 @@ jobs:
                 print("User is member")
             else:
                 print("User is community")
-
       - name: Add community label if not a member
         if: contains(steps.check_user.outputs.stdout, 'community')
         uses: andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90

.github/workflows/promote.yaml

@@ -3,70 +3,41 @@ name: Promote AWX Operator image
 on:
   release:
     types: [published]
-  workflow_dispatch:
-    inputs:
-      tag_name:
-        description: 'Name for the tag of the release.'
-        required: true
-      quay_registry:
-        description: 'Quay registry to push to.'
-        default: 'quay.io/ansible'
-
-env:
-  QUAY_REGISTRY: ${{ vars.QUAY_REGISTRY }}
 
 jobs:
   promote:
     runs-on: ubuntu-latest
     steps:
-      - name: Set GitHub Env vars for workflow_dispatch event
-        if: ${{ github.event_name == 'workflow_dispatch' }}
-        run: |
-          echo "TAG_NAME=${{ github.event.inputs.tag_name }}" >> $GITHUB_ENV
-          echo "QUAY_REGISTRY=${{ github.event.inputs.quay_registry }}" >> $GITHUB_ENV
-
-      - name: Set GitHub Env vars if release event
-        if: ${{ github.event_name == 'release' }}
-        run: |
-          echo "TAG_NAME=${{ github.event.release.tag_name }}" >> $GITHUB_ENV
-
-      - name: Fail if QUAY_REGISTRY not set
-        run: |
-          if [[ -z "${{ env.QUAY_REGISTRY }}" ]]; then
-            echo "QUAY_REGISTRY not set. Please set QUAY_REGISTRY in variable GitHub Actions variables."
-            exit 1
-          fi
-
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3
         with:
           depth: 0
 
-
-      - name: Log into registry ghcr.io
-        uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567    # v3.3.0
+      - uses: actions/checkout@v3
         with:
-          registry: ghcr.io
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          ref: gh-pages
+          path: gh-pages
 
-
-      - name: Log into registry quay.io
-        uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567    # v3.3.0
-        with:
-          registry: ${{ env.QUAY_REGISTRY }}
-          username: ${{ secrets.QUAY_USER }}
-          password: ${{ secrets.QUAY_TOKEN }}
-
-
-      - name: Pull Tagged Staged Image and Publish to quay.io
+      - name: Log in to GHCR
         run: |
-          docker buildx imagetools create \
-            ghcr.io/${{ github.repository }}:${{ env.TAG_NAME }} \
-            --tag ${{ env.QUAY_REGISTRY }}/awx-operator:${{ env.TAG_NAME }}
+          echo ${{ secrets.GITHUB_TOKEN }} | docker login ghcr.io -u ${{ github.actor }} --password-stdin
 
-
-      - name: Pull Staged Image and Publish to quay.io/${{ github.repository }}:latest
+      - name: Log in to Quay
         run: |
-          docker buildx imagetools create \
-            ghcr.io/${{ github.repository }}:${{ env.TAG_NAME }} \
-            --tag ${{ env.QUAY_REGISTRY }}/awx-operator:latest
+          echo ${{ secrets.QUAY_TOKEN }} | docker login quay.io -u ${{ secrets.QUAY_USER }} --password-stdin
+
+      - name: Re-tag and promote awx-operator image
+        run: |
+          docker pull ghcr.io/${{ github.repository }}:${{ github.event.release.tag_name }}
+          docker tag ghcr.io/${{ github.repository }}:${{ github.event.release.tag_name }} quay.io/${{ github.repository }}:${{ github.event.release.tag_name }}
+          docker tag ghcr.io/${{ github.repository }}:${{ github.event.release.tag_name }} quay.io/${{ github.repository }}:latest
+          docker push quay.io/${{ github.repository }}:${{ github.event.release.tag_name }}
+          docker push quay.io/${{ github.repository }}:latest
+
+      - name: Release Helm chart
+        run: |
+          ansible-playbook ansible/helm-release.yml -v \
+            -e operator_image=quay.io/${{ github.repository }} \
+            -e chart_owner=${{ github.repository_owner }} \
+            -e tag=${{ github.event.release.tag_name }} \
+            -e gh_token=${{ secrets.GITHUB_TOKEN }}
+            -e gh_user=${{ github.actor }}

.github/workflows/publish-operator-hub.yaml

@@ -1,86 +0,0 @@
-name: Publish AWX Operator on operator-hub
-on:
-  release:
-    types: [published]
-  workflow_dispatch:
-    inputs:
-      tag_name:
-        description: 'Name for the tag of the release.'
-        required: true
-      operator_hub_fork:
-        description: 'Fork of operator-hub where the PR will be created from. default: awx-auto'
-        required: true
-        default: 'awx-auto'
-      image_registry:
-        description: 'Image registry where the image is published to. default: quay.io'
-        required: true
-        default: 'quay.io'
-      image_registry_organization:
-        description: 'Image registry organization where the image is published to. default: ansible'
-        required: true
-        default: 'ansible'
-      community_operator_github_org:
-        description: 'Github organization for community-opeartor project. default: k8s-operatorhub'
-        required: true
-        default: 'k8s-operatorhub'
-      community_operator_prod_github_org:
-        description: 'GitHub organization for community-operator-prod project. default: redhat-openshift-ecosystem'
-        required: true
-        default: 'redhat-openshift-ecosystem'
-jobs:
-  promote:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Set GITHUB_ENV from workflow_dispatch event
-        if: ${{ github.event_name == 'workflow_dispatch' }}
-        run: |
-          echo "VERSION=${{ github.event.inputs.tag_name }}" >> $GITHUB_ENV
-          echo "IMAGE_REGISTRY=${{ github.event.inputs.image_registry }}" >> $GITHUB_ENV
-          echo "IMAGE_REGISTRY_ORGANIZATION=${{ github.event.inputs.image_registry_organization }}" >> $GITHUB_ENV
-          echo "COMMUNITY_OPERATOR_GITHUB_ORG=${{ github.event.inputs.community_operator_github_org }}" >> $GITHUB_ENV
-          echo "COMMUNITY_OPERATOR_PROD_GITHUB_ORG=${{ github.event.inputs.community_operator_prod_github_org }}" >> $GITHUB_ENV
-
-      - name: Set GITHUB_ENV for release event
-        if: ${{ github.event_name == 'release' }}
-        run: |
-          echo "VERSION=${{ github.event.release.tag_name }}" >> $GITHUB_ENV
-          echo "IMAGE_REGISTRY=quay.io" >> $GITHUB_ENV
-          echo "IMAGE_REGISTRY_ORGANIZATION=ansible" >> $GITHUB_ENV
-          echo "COMMUNITY_OPERATOR_GITHUB_ORG=k8s-operatorhub" >> $GITHUB_ENV
-          echo "COMMUNITY_OPERATOR_PROD_GITHUB_ORG=redhat-openshift-ecosystem" >> $GITHUB_ENV
-
-      - name: Log in to image registry
-        run: |
-          echo ${{ secrets.QUAY_TOKEN }} | docker login ${{ env.IMAGE_REGISTRY }} -u ${{ secrets.QUAY_USER }} --password-stdin
-
-      - name: Checkout awx-operator at workflow branch
-        uses: actions/checkout@v4
-        with:
-          path: awx-operator
-
-      - name: Checkout awx-opearator at ${{ env.VERSION }}
-        uses: actions/checkout@v4
-        with:
-          fetch-tags: true
-          ref: ${{ env.VERSION }}
-          path: awx-operator-${{ env.VERSION }}
-          fetch-depth: 0  # fetch all history so that git describe works
-
-      - name: Copy scripts to awx-operator-${{ env.VERSION }}
-        run: |
-          cp -f \
-            awx-operator/hack/publish-to-operator-hub.sh \
-            awx-operator-${{ env.VERSION }}/hack/publish-to-operator-hub.sh
-          cp -f \
-            awx-operator/Makefile \
-            awx-operator-${{ env.VERSION }}/Makefile
-
-      - name: Build and publish bundle to operator-hub
-        working-directory: awx-operator-${{ env.VERSION }}
-        env:
-          IMG_REPOSITORY: ${{ env.IMAGE_REGISTRY }}/${{ env.IMAGE_REGISTRY_ORGANIZATION }}
-          GITHUB_TOKEN: ${{ secrets.AWX_AUTO_GITHUB_TOKEN }}
-        run: |
-          git config --global user.email "awx-automation@redhat.com"
-          git config --global user.name "AWX Automation"
-          ./hack/publish-to-operator-hub.sh

.github/workflows/reusable-nox.yml

@@ -1,26 +0,0 @@
----
-name: nox
-
-"on":
-    workflow_call:
-
-jobs:
-    nox:
-        runs-on: ubuntu-latest
-        strategy:
-            fail-fast: false
-            matrix:
-                include:
-                - session: build
-                  python-versions: "3.11"
-        name: "Run nox ${{ matrix.session }} session"
-        steps:
-        - name: Check out repo
-          uses: actions/checkout@v4
-        - name: Setup nox
-          uses: wntrblm/nox@2024.04.15
-          with:
-              python-versions: "${{ matrix.python-versions }}"
-        - name: "Run nox -s ${{ matrix.session }}"
-          run: |
-            nox -s "${{ matrix.session }}"

.github/workflows/stage.yml

@@ -37,8 +37,14 @@ jobs:
 
           exit 0
 
+      - name: Checkout awx
+        uses: actions/checkout@v2
+        with:
+          repository: ${{ github.repository_owner }}/awx
+          path: awx
+
       - name: Checkout awx-operator
-        uses: actions/checkout@v4
+        uses: actions/checkout@v2
         with:
           repository: ${{ github.repository_owner }}/awx-operator
           path: awx-operator
@@ -47,20 +53,17 @@ jobs:
         run: |
           python3 -m pip install docker
 
-      - name: Log into registry ghcr.io
-        uses: docker/login-action@9780b0c442fbb1117ed29e0efdff1e18412f7567    # v3.3.0
-        with:
-          registry: ghcr.io
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+      - name: Log in to GHCR
+        run: |
+          echo ${{ secrets.GITHUB_TOKEN }} | docker login ghcr.io -u ${{ github.actor }} --password-stdin
 
-      - name: Stage awx-operator
+      - name: Build and stage awx-operator
         working-directory: awx-operator
         run: |
           BUILD_ARGS="--build-arg DEFAULT_AWX_VERSION=${{ github.event.inputs.default_awx_version }} \
-              --build-arg OPERATOR_VERSION=${{ github.event.inputs.version }}" \
-          IMG=ghcr.io/${{ github.repository }}:${{ github.event.inputs.version }} \
-          make docker-buildx
+                      --build-arg OPERATOR_VERSION=${{ github.event.inputs.version }}" \
+          IMAGE_TAG_BASE=ghcr.io/${{ github.repository_owner }}/awx-operator \
+          VERSION=${{ github.event.inputs.version }} make docker-build docker-push
 
       - name: Run test deployment
         working-directory: awx-operator
@@ -73,12 +76,10 @@ jobs:
         env:
           AWX_TEST_VERSION: ${{ github.event.inputs.default_awx_version }}
 
-      - name: Create Draft Release
-        id: create_release
-        uses: actions/create-release@v1
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        with:
-          tag_name: ${{ github.event.inputs.version }}
-          release_name: Release ${{ github.event.inputs.version }}
-          draft: true
+      - name: Create draft release
+        working-directory: awx
+        run: |
+          ansible-playbook tools/ansible/stage.yml \
+            -e version=${{ github.event.inputs.version }} \
+            -e repo=${{ github.repository_owner }}/awx-operator \
+            -e github_token=${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -9,5 +9,3 @@ gh-pages/
 /.cr-release-packages
 .vscode/
 __pycache__
-/site
-venv/*

.helm/starter/.helmignore

@@ -0,0 +1,23 @@
+# Patterns to ignore when building packages.
+# This supports shell glob matching, relative path matching, and
+# negation (prefixed with !). Only one pattern per line.
+.DS_Store
+# Common VCS dirs
+.git/
+.gitignore
+.bzr/
+.bzrignore
+.hg/
+.hgignore
+.svn/
+# Common backup files
+*.swp
+*.bak
+*.tmp
+*.orig
+*~
+# Various IDEs
+.project
+.idea/
+*.tmproj
+.vscode/

.helm/starter/Chart.yaml

@@ -0,0 +1,7 @@
+---
+apiVersion: v2
+appVersion: 0.1.0
+description: A Helm chart for Kubernetes
+name: starter
+type: application
+version: 0.1.0

.helm/starter/README.md

@@ -0,0 +1,67 @@
+# AWX Operator Helm Chart
+
+This chart installs the AWX Operator resources configured in [this](https://github.com/ansible/awx-operator) repository.
+
+## Getting Started
+To configure your AWX resource using this chart, create your own `yaml` values file. The name is up to personal preference since it will explicitly be passed into the helm chart. Helm will merge whatever values you specify in your file with the default `values.yaml`, overriding any settings you've changed while allowing you to fall back on defaults. Because of this functionality, `values.yaml` should not be edited directly.
+
+In your values config, enable `AWX.enabled` and add `AWX.spec` values based on the awx operator's [documentation](https://github.com/ansible/awx-operator/blob/devel/README.md). Consult the docs below for additional functionality.
+
+### Installing
+The operator's [helm install](https://github.com/ansible/awx-operator/blob/devel/README.md#helm-install-on-existing-cluster) guide provides key installation instructions.
+
+Example:
+```
+helm install my-awx-operator awx-operator/awx-operator -n awx --create-namespace -f myvalues.yaml
+```
+
+Argument breakdown:
+* `-f` passes in the file with your custom values
+* `-n` sets the namespace to be installed in
+  * This value is accessed by `{{ $.Release.Namespace }}` in the templates
+  * Acts as the default namespace for all unspecified resources
+* `--create-namespace` specifies that helm should create the namespace before installing
+
+To update an existing installation, use `helm upgrade` instead of `install`. The rest of the syntax remains the same.
+
+## Configuration
+The goal of adding helm configurations is to abstract out and simplify the creation of multi-resource configs. The `AWX.spec` field maps directly to the spec configs of the `AWX` resource that the operator provides, which are detailed in the [main README](https://github.com/ansible/awx-operator/blob/devel/README.md). Other sub-config can be added with the goal of simplifying more involved setups that require additional resources to be specified.
+
+These sub-headers aim to be a more intuitive entrypoint into customizing your deployment, and are easier to manage in the long-term. By design, the helm templates will defer to the manually defined specs to avoid configuration conflicts. For example, if `AWX.spec.postgres_configuration_secret` is being used, the `AWX.postgres` settings will not be applied, even if enabled.
+
+### External Postgres
+The `AWX.postgres` section simplifies the creation of the external postgres secret. If enabled, the configs provided will automatically be placed in a `postgres-config` secret and linked to the `AWX` resource. For proper secret management, the `AWX.postgres.password` value, and any other sensitive values, can be passed in at the command line rather than specified in code. Use the `--set` argument with `helm install`. Supplying the password this way is not recommended for production use, but may be helpful for initial PoC.
+
+
+## Values Summary
+
+### AWX
+| Value | Description | Default |
+|---|---|---|
+| `AWX.enabled` | Enable this AWX resource configuration | `false` |
+| `AWX.name` | The name of the AWX resource and default prefix for other resources | `"awx"` |
+| `AWX.spec` | specs to directly configure the AWX resource | `{}` |
+| `AWX.postgres` | configurations for the external postgres secret | - |
+
+
+# Contributing
+
+## Adding abstracted sections
+Where possible, defer to `AWX.spec` configs before applying the abstracted configs to avoid collision. This can be facilitated by the `(hasKey .spec what_i_will_abstract)` check.
+
+## Building and Testing
+This chart is built using the Makefile in the [awx-operator repo](https://github.com/ansible/awx-operator). Clone the repo and run `make helm-chart`. This will create the awx-operator chart in the `charts/awx-operator` directory. In this process, the contents of the `.helm/starter` directory will be added to the chart.
+
+## Future Goals
+All values under the `AWX` header are focused on configurations that use the operator. Configurations that relate to the Operator itself could be placed under an `Operator` heading, but that may add a layer of complication over current development.
+
+
+# Chart Publishing
+
+The chart is currently hosted on the gh-pages branch of the repo. During the release pipeline, the `index.yaml` stored in that branch is generated with helm chart entries from all valid tags. We are currently unable to use the `chart-releaser` pipeline due to the fact that the complete helm chart is not committed to the repo and is instead built during the release process. Therefore, the cr action is unable to compare against previous versions.
+
+Instead of CR, we use `helm repo index` to generate an index from all locally pulled chart versions. Since we build from scratch every time, the timestamps of all entries will be updated. This could be improved by using yq or something similar to detect which tags are already in the index.yaml file, and only merge in tags that are not present.
+
+Not using CR could be addressed in the future by keeping the chart built as a part of releases, as long as CR compares the chart to previous release packages rather than previous commits. If the latter is the case, then we would not have the necessary history for comparison.
+
+

.helm/starter/templates/_helpers.tpl

@@ -0,0 +1,6 @@
+{{/*
+Generate the name of the postgres secret, expects AWX context passed in
+*/}}
+{{- define "postgres.secretName" -}}
+{{ default (printf "%s-postgres-configuration" .Values.AWX.name) .Values.AWX.postgres.secretName }}
+{{- end }}

.helm/starter/templates/awx-deploy.yaml

@@ -0,0 +1,24 @@
+{{- if $.Values.AWX.enabled }}
+{{- with .Values.AWX }}
+apiVersion: awx.ansible.com/v1beta1
+kind: AWX
+metadata:
+  name: {{ .name }}
+  namespace: {{ $.Release.Namespace }}
+spec:
+{{- /* Include raw map from the values file spec */}}
+{{ .spec | toYaml | indent 2 }}
+{{- /* Provide security context defaults */}}
+  {{- if not (hasKey .spec "security_context_settings") }}
+  security_context_settings:
+    runAsGroup: 0
+    runAsUser: 0
+    fsGroup: 0
+    fsGroupChangePolicy: OnRootMismatch
+  {{- end }}
+{{- /* Postgres configs if enabled and not already present */}}
+  {{- if and .postgres.enabled (not (hasKey .spec "postgres_configuration_secret")) }}
+  postgres_configuration_secret: {{ include "postgres.secretName" $ }}
+  {{- end }}
+{{- end }}
+{{- end }}

.helm/starter/templates/postgres-config.yaml

@@ -0,0 +1,18 @@
+{{- if and $.Values.AWX.enabled $.Values.AWX.postgres.enabled }}
+apiVersion: v1
+kind: Secret
+metadata:
+  name: {{ include "postgres.secretName" . }}
+  namespace: {{ $.Release.Namespace }}
+{{- with $.Values.AWX.postgres }}
+stringData:
+  host: {{ .host }}
+  port: {{ .port | quote }}
+  database: {{ .dbName }}
+  username: {{ .username }}
+  password: {{ .password }}
+  sslmode: {{ .sslmode }}
+  type: {{ .type }}
+type: Opaque
+{{- end }}
+{{- end }}

.helm/starter/values.yaml

@@ -0,0 +1,19 @@
+AWX: 
+  # enable use of awx-deploy template
+  enabled: false
+  name: awx
+  spec:
+    admin_user: admin
+
+  # configurations for external postgres instance
+  postgres:
+    enabled: false
+    host: Unset
+    port: 5678
+    dbName: Unset
+    username: admin
+    # for secret management, pass in the password independently of this file
+    # at the command line, use --set AWX.postgres.password
+    password: Unset
+    sslmode: prefer
+    type: unmanaged

.readthedocs.yml

@@ -1,17 +0,0 @@
-# Read the Docs configuration file
-# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
-
-# RTD API version
-version: 2
-
-build:
-  os: ubuntu-22.04
-  tools:
-    python: "3.11"
-
-mkdocs:
-  configuration: mkdocs.yml
-
-python:
-  install:
-  - requirements: ./docs/requirements.txt

.yamllint

@@ -6,7 +6,7 @@ ignore: |
   kustomization.yaml
   awx-operator.clusterserviceversion.yaml
   bundle
-  hacking/
+  .helm/starter
 
 rules:
   truthy: disable

CONTRIBUTING.md

@@ -6,16 +6,13 @@ Have questions about this document or anything not covered here? Please file a n
 
 ## Table of contents
 
-- [AWX-Operator Contributing Guidelines](#awx-operator-contributing-guidelines)
-  - [Table of contents](#table-of-contents)
-  - [Things to know prior to submitting code](#things-to-know-prior-to-submitting-code)
-  - [Submmiting your work](#submmiting-your-work)
-  - [Development](#development)
-  - [Testing](#testing)
-      - [Testing in Kind](#testing-in-kind)
-      - [Testing in Minikube](#testing-in-minikube)
-  - [Generating a bundle](#generating-a-bundle)
-  - [Reporting Issues](#reporting-issues)
+* [Things to know prior to submitting code](#things-to-know-prior-to-submitting-code)
+* [Submmiting your Work](#submitting-your-work)
+* [Testing](#testing)
+    * [Testing in Docker](#testing-in-docker)
+    * [Testing in Minikube](#testing-in-minikube)
+* [Generating a bundle](#generating-a-bundle)
+* [Reporting Issues](#reporting-issues)
 
 
 ## Things to know prior to submitting code
@@ -28,13 +25,13 @@ Have questions about this document or anything not covered here? Please file a n
 
 
 ## Submmiting your work
-1. From your fork `devel` branch, create a new branch to stage your changes.
+1. From your fork `devel` branch, create a new brach to stage your changes.
 ```sh
 #> git checkout -b <branch-name>
 ```
 2. Make your changes.
 3. Test your changes according described on the Testing section.
-4. If everything looks correct, commit your changes.
+4. If everylooks looks correct, commit your changes.
 ```sh
 #> git add <FILES>
 #> git commit -m "My message here"
@@ -43,34 +40,30 @@ Have questions about this document or anything not covered here? Please file a n
 
 **Note**: If you have multiple commits, make sure to `squash` your commits into a single commit which will facilitate our release process.
 
-## Development
-The development environment consists of running an [`up.sh`](./up.sh) and a [`down.sh`](./down.sh) script, which applies or deletes yaml on the Openshift or K8s cluster you are connected to. See the [development.md](docs/development.md) for information on how to deploy and test changes from your branch.
+
 
 ## Testing
 
-This Operator includes a [Molecule](https://ansible.readthedocs.io/projects/molecule/)-based test environment, which can be executed standalone in Docker (e.g. in CI or in a single Docker container anywhere), or inside any kind of Kubernetes cluster (e.g. Minikube).
+This Operator includes a [Molecule](https://molecule.readthedocs.io/en/stable/)-based test environment, which can be executed standalone in Docker (e.g. in CI or in a single Docker container anywhere), or inside any kind of Kubernetes cluster (e.g. Minikube).
 
 You need to make sure you have Molecule installed before running the following commands. You can install Molecule with:
 
 ```sh
-#> python -m pip install molecule-plugins[docker]
+#> pip install 'molecule[docker]'
 ```
 
 Running `molecule test` sets up a clean environment, builds the operator, runs all configured tests on an example operator instance, then tears down the environment (at least in the case of Docker).
 
 If you want to actively develop the operator, use `molecule converge`, which does everything but tear down the environment at the end.
 
-#### Testing in Kind
-
-Testing with a kind cluster is the recommended way to test the awx-operator locally. First, you need to install kind if you haven't already. Please see these docs for setting that up:
-* https://kind.sigs.k8s.io/docs/user/quick-start/
-
-To run the tests, from the root of your checkout, run the following command:
+#### Testing in Docker
 
 ```sh
-#> molecule test -s kind
+#> molecule test -s test-local
 ```
 
+This environment is meant for headless testing (e.g. in a CI environment, or when making smaller changes which don't need to be verified through a web interface). It is difficult to test things like AWX's web UI or to connect other applications on your local machine to the services running inside the cluster, since it is inside a Docker container with no static IP address.
+
 #### Testing in Minikube
 
 ```sh
@@ -144,4 +137,4 @@ Applying this template will do it. Once the CatalogSource is in a READY state, t
 
 ## Reporting Issues
 
-We welcome your feedback, and encourage you to file an issue when you run into a problem.
+We welcome your feedback, and encourage you to file an issue when you run into a problem.

Dockerfile

@@ -1,8 +1,8 @@
-FROM quay.io/operator-framework/ansible-operator:v1.34.2
+FROM quay.io/operator-framework/ansible-operator:v1.26.0
 
-USER root
-RUN dnf update --security --bugfix -y && \
-    dnf install -y openssl
+USER 0
+
+RUN dnf install -y openssl
 
 USER 1001
 

Makefile

@@ -4,10 +4,16 @@
 # - use the VERSION as arg of the bundle target (e.g make bundle VERSION=0.0.2)
 # - use environment variables to overwrite this value (e.g export VERSION=0.0.2)
 VERSION ?= $(shell git describe --tags)
-PREV_VERSION ?= $(shell git describe --abbrev=0 --tags $(shell git rev-list --tags --skip=1 --max-count=1))
 
 CONTAINER_CMD ?= docker
 
+# GNU vs BSD in-place sed
+ifeq ($(shell sed --version 2>/dev/null | grep -q GNU && echo gnu),gnu)
+	SED_I := sed -i
+else
+	SED_I := sed -i ''
+endif
+
 # CHANNELS define the bundle channels used in the bundle.
 # Add a new line here if you would like to change its default config. (E.g CHANNELS = "candidate,fast,stable")
 # To re-generate a bundle for other specific channels without changing the standard setup, you can:
@@ -53,6 +59,14 @@ endif
 IMG ?= $(IMAGE_TAG_BASE):$(VERSION)
 NAMESPACE ?= awx
 
+# Helm variables
+CHART_NAME ?= awx-operator
+CHART_DESCRIPTION ?= A Helm chart for the AWX Operator
+CHART_OWNER ?= $(GH_REPO_OWNER)
+CHART_REPO ?= awx-operator
+CHART_BRANCH ?= gh-pages
+CHART_INDEX ?= index.yaml
+
 .PHONY: all
 all: docker-build
 
@@ -73,10 +87,6 @@ all: docker-build
 help: ## Display this help.
 	@awk 'BEGIN {FS = ":.*##"; printf "\nUsage:\n  make \033[36m<target>\033[0m\n"} /^[a-zA-Z_0-9-]+:.*?##/ { printf "  \033[36m%-15s\033[0m %s\n", $$1, $$2 } /^##@/ { printf "\n\033[1m%s\033[0m\n", substr($$0, 5) } ' $(MAKEFILE_LIST)
 
-.PHONY: print-%
-print-%: ## Print any variable from the Makefile. Use as `make print-VARIABLE`
-	@echo $($*)
-
 ##@ Build
 
 .PHONY: run
@@ -91,21 +101,6 @@ docker-build: ## Build docker image with the manager.
 docker-push: ## Push docker image with the manager.
 	${CONTAINER_CMD} push ${IMG}
 
-# PLATFORMS defines the target platforms for  the manager image be build to provide support to multiple
-# architectures. (i.e. make docker-buildx IMG=myregistry/mypoperator:0.0.1). To use this option you need to:
-# - able to use docker buildx . More info: https://docs.docker.com/build/buildx/
-# - have enable BuildKit, More info: https://docs.docker.com/develop/develop-images/build_enhancements/
-# - be able to push the image for your registry (i.e. if you do not inform a valid value via IMG=<myregistry/image:<tag>> than the export will fail)
-# To properly provided solutions that supports more than one platform you should use this option.
-PLATFORMS ?= linux/arm64,linux/amd64,linux/s390x,linux/ppc64le
-.PHONY: docker-buildx
-docker-buildx: ## Build and push docker image for the manager for cross-platform support
-	- docker buildx create --name project-v3-builder
-	docker buildx use project-v3-builder
-	- docker buildx build --push $(BUILD_ARGS) --platform=$(PLATFORMS) --tag ${IMG} -f Dockerfile .
-	- docker buildx rm project-v3-builder
-
-
 ##@ Deployment
 
 .PHONY: install
@@ -145,7 +140,7 @@ ifeq (,$(shell which kustomize 2>/dev/null))
 	@{ \
 	set -e ;\
 	mkdir -p $(dir $(KUSTOMIZE)) ;\
-	curl -sSLo - https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize/v5.0.1/kustomize_v5.0.1_$(OS)_$(ARCHA).tar.gz | \
+	curl -sSLo - https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize/v4.5.7/kustomize_v4.5.7_$(OS)_$(ARCHA).tar.gz | \
 	tar xzf - -C bin/ ;\
 	}
 else
@@ -153,22 +148,6 @@ KUSTOMIZE = $(shell which kustomize)
 endif
 endif
 
-.PHONY: operator-sdk
-OPERATOR_SDK = $(shell pwd)/bin/operator-sdk
-operator-sdk: ## Download operator-sdk locally if necessary, preferring the $(pwd)/bin path over global if both exist.
-ifeq (,$(wildcard $(OPERATOR_SDK)))
-ifeq (,$(shell which operator-sdk 2>/dev/null))
-	@{ \
-	set -e ;\
-	mkdir -p $(dir $(OPERATOR_SDK)) ;\
-	curl -sSLo $(OPERATOR_SDK) https://github.com/operator-framework/operator-sdk/releases/download/v1.34.2/operator-sdk_$(OS)_$(ARCHA) ;\
-	chmod +x $(OPERATOR_SDK) ;\
-	}
-else
-OPERATOR_SDK = $(shell which operator-sdk)
-endif
-endif
-
 .PHONY: ansible-operator
 ANSIBLE_OPERATOR = $(shell pwd)/bin/ansible-operator
 ansible-operator: ## Download ansible-operator locally if necessary, preferring the $(pwd)/bin path over global if both exist.
@@ -177,7 +156,7 @@ ifeq (,$(shell which ansible-operator 2>/dev/null))
 	@{ \
 	set -e ;\
 	mkdir -p $(dir $(ANSIBLE_OPERATOR)) ;\
-	curl -sSLo $(ANSIBLE_OPERATOR) https://github.com/operator-framework/ansible-operator-plugins/releases/download/v1.34.0/ansible-operator_$(OS)_$(ARCHA) ;\
+	curl -sSLo $(ANSIBLE_OPERATOR) https://github.com/operator-framework/operator-sdk/releases/download/v1.26.0/ansible-operator_$(OS)_$(ARCHA) ;\
 	chmod +x $(ANSIBLE_OPERATOR) ;\
 	}
 else
@@ -186,11 +165,11 @@ endif
 endif
 
 .PHONY: bundle
-bundle: kustomize operator-sdk ## Generate bundle manifests and metadata, then validate generated files.
-	$(OPERATOR_SDK) generate kustomize manifests -q
+bundle: kustomize ## Generate bundle manifests and metadata, then validate generated files.
+	operator-sdk generate kustomize manifests -q
 	cd config/manager && $(KUSTOMIZE) edit set image controller=$(IMG)
-	$(KUSTOMIZE) build config/manifests | $(OPERATOR_SDK) generate bundle -q --overwrite --version $(VERSION) $(BUNDLE_METADATA_OPTS)
-	$(OPERATOR_SDK) bundle validate ./bundle
+	$(KUSTOMIZE) build config/manifests | operator-sdk generate bundle -q --overwrite --version $(VERSION) $(BUNDLE_METADATA_OPTS)
+	operator-sdk bundle validate ./bundle
 
 .PHONY: bundle-build
 bundle-build: ## Build the bundle image.
@@ -239,3 +218,180 @@ catalog-build: opm ## Build a catalog image.
 .PHONY: catalog-push
 catalog-push: ## Push a catalog image.
 	$(MAKE) docker-push IMG=$(CATALOG_IMG)
+
+.PHONY: kubectl-slice
+KUBECTL_SLICE = $(shell pwd)/bin/kubectl-slice
+kubectl-slice: ## Download kubectl-slice locally if necessary.
+ifeq (,$(wildcard $(KUBECTL_SLICE)))
+ifeq (,$(shell which kubectl-slice 2>/dev/null))
+	@{ \
+	set -e ;\
+	mkdir -p $(dir $(KUBECTL_SLICE)) ;\
+	curl -sSLo - https://github.com/patrickdappollonio/kubectl-slice/releases/download/v1.1.0/kubectl-slice_1.1.0_$(OS)_$(ARCHX).tar.gz | \
+	tar xzf - -C bin/ kubectl-slice ;\
+	}
+else
+KUBECTL_SLICE = $(shell which kubectl-slice)
+endif
+endif
+
+.PHONY: helm
+HELM = $(shell pwd)/bin/helm
+helm: ## Download helm locally if necessary.
+ifeq (,$(wildcard $(HELM)))
+ifeq (,$(shell which helm 2>/dev/null))
+	@{ \
+	set -e ;\
+	mkdir -p $(dir $(HELM)) ;\
+	curl -sSLo - https://get.helm.sh/helm-v3.8.0-$(OS)-$(ARCHA).tar.gz | \
+	tar xzf - -C bin/ $(OS)-$(ARCHA)/helm ;\
+	mv bin/$(OS)-$(ARCHA)/helm bin/helm ;\
+	rmdir bin/$(OS)-$(ARCHA) ;\
+	}
+else
+HELM = $(shell which helm)
+endif
+endif
+
+.PHONY: yq
+YQ = $(shell pwd)/bin/yq
+yq: ## Download yq locally if necessary.
+ifeq (,$(wildcard $(YQ)))
+ifeq (,$(shell which yq 2>/dev/null))
+	@{ \
+	set -e ;\
+	mkdir -p $(dir $(HELM)) ;\
+	curl -sSLo - https://github.com/mikefarah/yq/releases/download/v4.20.2/yq_$(OS)_$(ARCHA).tar.gz | \
+	tar xzf - -C bin/ ;\
+	mv bin/yq_$(OS)_$(ARCHA) bin/yq ;\
+	}
+else
+YQ = $(shell which yq)
+endif
+endif
+
+PHONY: cr
+CR = $(shell pwd)/bin/cr
+cr: ## Download cr locally if necessary.
+ifeq (,$(wildcard $(CR)))
+ifeq (,$(shell which cr 2>/dev/null))
+	@{ \
+	set -e ;\
+	mkdir -p $(dir $(CR)) ;\
+	curl -sSLo - https://github.com/helm/chart-releaser/releases/download/v1.3.0/chart-releaser_1.3.0_$(OS)_$(ARCHA).tar.gz | \
+	tar xzf - -C bin/ cr ;\
+	}
+else
+CR = $(shell which cr)
+endif
+endif
+
+charts:
+	mkdir -p $@
+
+.PHONY: helm-chart
+helm-chart: helm-chart-generate
+
+.PHONY: helm-chart-generate
+helm-chart-generate: kustomize helm kubectl-slice yq charts
+	@echo "== KUSTOMIZE: Set image and chart label =="
+	cd config/manager && $(KUSTOMIZE) edit set image controller=${IMG}
+	cd config/manager && $(KUSTOMIZE) edit set label helm.sh/chart:$(CHART_NAME)
+	cd config/default && $(KUSTOMIZE) edit set label helm.sh/chart:$(CHART_NAME)
+
+	@echo "== Gather Helm Chart Metadata =="
+	# remove the existing chart if it exists
+	rm -rf charts/$(CHART_NAME)
+	# create new chart metadata in Chart.yaml
+	cd charts && \
+		$(HELM) create awx-operator --starter $(shell pwd)/.helm/starter ;\
+		$(YQ) -i '.version = "$(VERSION)"' $(CHART_NAME)/Chart.yaml ;\
+		$(YQ) -i '.appVersion = "$(VERSION)" | .appVersion style="double"' $(CHART_NAME)/Chart.yaml ;\
+		$(YQ) -i '.description = "$(CHART_DESCRIPTION)"' $(CHART_NAME)/Chart.yaml ;\
+
+	@echo "Generated chart metadata:"
+	@cat charts/$(CHART_NAME)/Chart.yaml
+
+	@echo "== KUSTOMIZE: Generate resources and slice into templates =="
+	# place in raw-files directory so they can be modified while they are valid yaml - as soon as they are in templates/,
+	# wild cards pick up the actual templates, which are not real yaml and can't have yq run on them.
+	$(KUSTOMIZE) build --load-restrictor LoadRestrictionsNone config/default | \
+		$(KUBECTL_SLICE) --input-file=- \
+			--output-dir=charts/$(CHART_NAME)/raw-files \
+			--sort-by-kind
+
+	@echo "== GIT: Reset kustomize configs =="
+	# reset kustomize configs following kustomize build
+	git checkout -f config/.
+
+	@echo "== Build Templates and CRDS =="
+	# Delete metadata.namespace, release namespace will be automatically inserted by helm
+	for file in charts/$(CHART_NAME)/raw-files/*; do\
+		$(YQ) -i 'del(.metadata.namespace)' $${file};\
+	done
+	# Correct namespace for rolebinding to be release namespace, this must be explicit
+	for file in charts/$(CHART_NAME)/raw-files/*rolebinding*; do\
+		$(YQ) -i '.subjects[0].namespace = "{{ .Release.Namespace }}"' $${file};\
+	done
+	# move all custom resource definitions to crds folder
+	mkdir charts/$(CHART_NAME)/crds
+	mv charts/$(CHART_NAME)/raw-files/customresourcedefinition*.yaml charts/$(CHART_NAME)/crds/.
+	# remove any namespace definitions
+	rm -f charts/$(CHART_NAME)/raw-files/namespace*.yaml
+	# move remaining resources to helm templates
+	mv charts/$(CHART_NAME)/raw-files/* charts/$(CHART_NAME)/templates/.
+	# remove the raw-files folder
+	rm -rf charts/$(CHART_NAME)/raw-files
+
+	# create and populate NOTES.txt
+	@echo "AWX Operator installed with Helm Chart version $(VERSION)" > charts/$(CHART_NAME)/templates/NOTES.txt
+
+	@echo "Helm chart successfully configured for $(CHART_NAME) version $(VERSION)"
+
+
+.PHONY: helm-package
+helm-package: helm-chart
+	@echo "== Package Current Chart Version =="
+	mkdir -p .cr-release-packages
+	# package the chart and put it in .cr-release-packages dir
+	$(HELM) package ./charts/awx-operator -d .cr-release-packages
+
+# List all tags oldest to newest.
+TAGS := $(shell git ls-remote --tags --sort=version:refname --refs -q | cut -d/ -f3)
+
+# The actual release happens in ansible/helm-release.yml, which calls this targer
+# until https://github.com/helm/chart-releaser/issues/122 happens, chart-releaser is not ideal for a chart
+# that is contained within a larger repo, where a tag may not require a new chart version
+.PHONY: helm-index
+helm-index:
+	# when running in CI this gh-pages are already checked out with github action to 'gh-pages' directory
+	# TODO: test if gh-pages directory exists and if not exist
+
+	@echo "== GENERATE INDEX FILE =="
+	# This step to workaround issues with old releases being dropped.
+	# Until https://github.com/helm/chart-releaser/issues/133 happens
+	@echo "== CHART FETCH previous releases =="
+	# Download all old releases
+	mkdir -p .cr-release-packages
+
+	for tag in $(TAGS); do\
+		dl_url="https://github.com/$(CHART_OWNER)/$(CHART_REPO)/releases/download/$${tag}/$(CHART_REPO)-$${tag}.tgz";\
+		echo "Downloading $${tag} from $${dl_url}";\
+		curl -RLOs -z "$(CHART_REPO)-$${tag}.tgz" --fail $${dl_url};\
+		result=$$?;\
+		if [ $${result} -eq 0 ]; then\
+			echo "Downloaded $${dl_url}";\
+			mkdir -p .cr-release-packages/$${tag};\
+			mv ./$(CHART_REPO)-$${tag}.tgz .cr-release-packages/$${tag};\
+		else\
+			echo "Skipping release $${tag}; No helm chart present";\
+			rm -rf "$(CHART_REPO)-$${tag}.tgz";\
+		fi;\
+	done;\
+
+	# generate the index file in the root of the gh-pages branch
+	# --merge will leave any values in index.yaml that don't get generated by this command, but
+	# it is likely that all values are overridden
+	$(HELM) repo index .cr-release-packages --url https://github.com/$(CHART_OWNER)/$(CHART_REPO)/releases/download/ --merge gh-pages/index.yaml
+
+	mv .cr-release-packages/index.yaml gh-pages/index.yaml

PROJECT

@@ -1,7 +1,3 @@
-# Code generated by tool. DO NOT EDIT.
-# This file is used to track the info used to scaffold your project
-# and allow the plugins properly work.
-# More info: https://book.kubebuilder.io/reference/project-config.html
 domain: ansible.com
 layout:
 - ansible.sdk.operatorframework.io/v1
@@ -31,11 +27,4 @@ resources:
   group: awx
   kind: AWXRestore
   version: v1beta1
-- api:
-    crdVersion: v1
-    namespaced: true
-  domain: ansible.com
-  group: awx
-  kind: AWXMeshIngress
-  version: v1alpha1
 version: "3"

ansible/helm-release.yml

@@ -0,0 +1,62 @@
+---
+- hosts: localhost
+  vars:
+    chart_repo: awx-operator
+  tasks:
+    - name: Look up release
+      uri:
+        url: "https://api.github.com/repos/{{ chart_owner }}/{{ chart_repo }}/releases/tags/{{ tag }}"
+      register: release
+      ignore_errors: yes
+
+    - fail:
+        msg: |
+          Release must exist before running this playbook
+      when: release is not success
+
+    - name: Build and package helm chart
+      command: |
+        make helm-package
+      environment:
+        VERSION: "{{ tag }}"
+        IMAGE_TAG_BASE: "{{ operator_image }}"
+      args:
+        chdir: "{{ playbook_dir }}/../"
+
+    # Move to chart releaser after https://github.com/helm/chart-releaser/issues/122 exists
+    - name: Upload helm chart
+      uri:
+        url: "https://uploads.github.com/repos/{{ chart_owner }}/{{ chart_repo }}/releases/{{ release.json.id }}/assets?name=awx-operator-{{ tag }}.tgz"
+        src: "{{ playbook_dir }}/../.cr-release-packages/awx-operator-{{ tag }}.tgz"
+        headers:
+          Authorization: "token {{ gh_token }}"
+          Content-Type: "application/octet-stream"
+        status_code:
+          - 200
+          - 201
+      register: asset_upload
+      changed_when: asset_upload.json.state == "uploaded"
+
+    - name: Configure git config
+      shell: |
+        git config user.name {{ gh_user }}
+        git config user.email {{ gh_user }}@users.noreply.github.com
+      args:
+        chdir: "{{ playbook_dir }}/../gh-pages"
+
+    - name: Publish helm index
+      command: |
+        make helm-index
+      environment:
+        CHART_OWNER: "{{ chart_owner }}"
+        CR_TOKEN: "{{ gh_token }}"
+      args:
+        chdir: "{{ playbook_dir }}/../"
+
+    - name: Stage and Push commit to gh-pages branch
+      shell: |
+        git add index.yaml
+        git commit -m "Updated index.yaml latest release"
+        git push
+      args:
+        chdir: "{{ playbook_dir }}/../gh-pages"

awxmeshingress-demo.yml

@@ -1,7 +0,0 @@
----
-apiVersion: awx.ansible.com/v1alpha1
-kind: AWXMeshIngress
-metadata:
-  name: awx-mesh-ingress-demo
-spec:
-  deployment_name: awx-demo

config/crd/bases/awx.ansible.com_awxbackups.yaml

@@ -90,24 +90,6 @@ spec:
               postgres_image_version:
                 description: PostgreSQL container image version to use
                 type: string
-              precreate_partition_hours:
-                description: Number of hours worth of events table partitions to precreate before backup to avoid pg_dump locks.
-                type: integer
-                format: int32
-              image_pull_policy:
-                description: The image pull policy
-                type: string
-                default: IfNotPresent
-                enum:
-                - Always
-                - always
-                - Never
-                - never
-                - IfNotPresent
-                - ifnotpresent
-              db_management_pod_node_selector:
-                description: nodeSelector for the Postgres pods to backup
-                type: string
               no_log:
                 description: Configure no_log for no_log tasks
                 type: boolean

config/crd/bases/awx.ansible.com_awxmeshingresses.yaml

@@ -1,461 +0,0 @@
----
-apiVersion: apiextensions.k8s.io/v1
-kind: CustomResourceDefinition
-metadata:
-  name: awxmeshingresses.awx.ansible.com
-spec:
-  group: awx.ansible.com
-  names:
-    kind: AWXMeshIngress
-    listKind: AWXMeshIngressList
-    plural: awxmeshingresses
-    singular: awxmeshingress
-  scope: Namespaced
-  versions:
-  - name: v1alpha1
-    schema:
-      openAPIV3Schema:
-        description: AWXMeshIngress is the Schema for the awxmeshingresses API
-        properties:
-          apiVersion:
-            description: 'APIVersion defines the versioned schema of this representation
-              of an object. Servers should convert recognized schemas to the latest
-              internal value, and may reject unrecognized values.
-              More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
-            type: string
-          kind:
-            description: 'Kind is a string value representing the REST resource this
-              object represents. Servers may infer this from the endpoint the client
-              submits requests to. Cannot be updated. In CamelCase.
-              More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
-            type: string
-          metadata:
-            type: object
-          spec:
-            description: Spec defines the desired state of AWXMeshIngress
-            type: object
-            x-kubernetes-preserve-unknown-fields: true
-            required:
-            - deployment_name
-            properties:
-              deployment_name:
-                description: Name of the AWX deployment to create the Mesh Ingress for.
-                type: string
-              image_pull_secrets:
-                description: Image pull secrets for Mesh Ingress containers.
-                type: array
-                items:
-                  type: string
-              external_hostname:
-                description: External hostname to use for the Mesh Ingress.
-                type: string
-              external_ipaddress:
-                description: External IP address to use for the Mesh Ingress.
-                type: string
-              ingress_type:
-                description: The ingress type to use to reach the deployed instance
-                type: string
-                enum:
-                - none
-                - Ingress
-                - ingress
-                - IngressRouteTCP
-                - ingressroutetcp
-                - Route
-                - route
-              ingress_api_version:
-                description: The Ingress API version to use
-                type: string
-              ingress_annotations:
-                description: Annotations to add to the Ingress Controller
-                type: string
-              ingress_class_name:
-                description: The name of ingress class to use instead of the cluster default.
-                type: string
-              ingress_controller:
-                description: Special configuration for specific Ingress Controllers
-                type: string
-              node_selector:
-                description: Assign the Mesh Ingress Pod to the specified node.
-                type: string
-              tolerations:
-                description: Scheduling tolerations for the Mesh Ingress instance.
-                type: string
-              topology_spread_constraints:
-                description: Topology spread constraints for the Mesh Ingress instance.
-                type: string
-              affinity:
-                description: Scheduling constraints to apply to the Pod definition
-                properties:
-                  nodeAffinity:
-                    properties:
-                      preferredDuringSchedulingIgnoredDuringExecution:
-                        items:
-                          properties:
-                            preference:
-                              properties:
-                                matchExpressions:
-                                  items:
-                                    properties:
-                                      key:
-                                        type: string
-                                      operator:
-                                        type: string
-                                      values:
-                                        items:
-                                          type: string
-                                        type: array
-                                    required:
-                                    - key
-                                    - operator
-                                    type: object
-                                  type: array
-                                matchFields:
-                                  items:
-                                    properties:
-                                      key:
-                                        type: string
-                                      operator:
-                                        type: string
-                                      values:
-                                        items:
-                                          type: string
-                                        type: array
-                                    required:
-                                    - key
-                                    - operator
-                                    type: object
-                                  type: array
-                              type: object
-                              x-kubernetes-map-type: atomic
-                            weight:
-                              format: int32
-                              type: integer
-                          required:
-                          - preference
-                          - weight
-                          type: object
-                        type: array
-                      requiredDuringSchedulingIgnoredDuringExecution:
-                        properties:
-                          nodeSelectorTerms:
-                            items:
-                              properties:
-                                matchExpressions:
-                                  items:
-                                    properties:
-                                      key:
-                                        type: string
-                                      operator:
-                                        type: string
-                                      values:
-                                        items:
-                                          type: string
-                                        type: array
-                                    required:
-                                    - key
-                                    - operator
-                                    type: object
-                                  type: array
-                                matchFields:
-                                  items:
-                                    properties:
-                                      key:
-                                        type: string
-                                      operator:
-                                        type: string
-                                      values:
-                                        items:
-                                          type: string
-                                        type: array
-                                    required:
-                                    - key
-                                    - operator
-                                    type: object
-                                  type: array
-                              type: object
-                              x-kubernetes-map-type: atomic
-                            type: array
-                        required:
-                        - nodeSelectorTerms
-                        type: object
-                        x-kubernetes-map-type: atomic
-                    type: object
-                  podAffinity:
-                    properties:
-                      preferredDuringSchedulingIgnoredDuringExecution:
-                        items:
-                          properties:
-                            podAffinityTerm:
-                              properties:
-                                labelSelector:
-                                  properties:
-                                    matchExpressions:
-                                      items:
-                                        properties:
-                                          key:
-                                            type: string
-                                          operator:
-                                            type: string
-                                          values:
-                                            items:
-                                              type: string
-                                            type: array
-                                        required:
-                                        - key
-                                        - operator
-                                        type: object
-                                      type: array
-                                    matchLabels:
-                                      additionalProperties:
-                                        type: string
-                                      type: object
-                                  type: object
-                                  x-kubernetes-map-type: atomic
-                                namespaceSelector:
-                                  properties:
-                                    matchExpressions:
-                                      items:
-                                        properties:
-                                          key:
-                                            type: string
-                                          operator:
-                                            type: string
-                                          values:
-                                            items:
-                                              type: string
-                                            type: array
-                                        required:
-                                        - key
-                                        - operator
-                                        type: object
-                                      type: array
-                                    matchLabels:
-                                      additionalProperties:
-                                        type: string
-                                      type: object
-                                  type: object
-                                  x-kubernetes-map-type: atomic
-                                namespaces:
-                                  items:
-                                    type: string
-                                  type: array
-                                topologyKey:
-                                  type: string
-                              required:
-                              - topologyKey
-                              type: object
-                            weight:
-                              format: int32
-                              type: integer
-                          required:
-                          - podAffinityTerm
-                          - weight
-                          type: object
-                        type: array
-                      requiredDuringSchedulingIgnoredDuringExecution:
-                        items:
-                          properties:
-                            labelSelector:
-                              properties:
-                                matchExpressions:
-                                  items:
-                                    properties:
-                                      key:
-                                        type: string
-                                      operator:
-                                        type: string
-                                      values:
-                                        items:
-                                          type: string
-                                        type: array
-                                    required:
-                                    - key
-                                    - operator
-                                    type: object
-                                  type: array
-                                matchLabels:
-                                  additionalProperties:
-                                    type: string
-                                  type: object
-                              type: object
-                              x-kubernetes-map-type: atomic
-                            namespaceSelector:
-                              properties:
-                                matchExpressions:
-                                  items:
-                                    properties:
-                                      key:
-                                        type: string
-                                      operator:
-                                        type: string
-                                      values:
-                                        items:
-                                          type: string
-                                        type: array
-                                    required:
-                                    - key
-                                    - operator
-                                    type: object
-                                  type: array
-                                matchLabels:
-                                  additionalProperties:
-                                    type: string
-                                  type: object
-                              type: object
-                              x-kubernetes-map-type: atomic
-                            namespaces:
-                              items:
-                                type: string
-                              type: array
-                            topologyKey:
-                              type: string
-                          required:
-                          - topologyKey
-                          type: object
-                        type: array
-                    type: object
-                  podAntiAffinity:
-                    properties:
-                      preferredDuringSchedulingIgnoredDuringExecution:
-                        items:
-                          properties:
-                            podAffinityTerm:
-                              properties:
-                                labelSelector:
-                                  properties:
-                                    matchExpressions:
-                                      items:
-                                        properties:
-                                          key:
-                                            type: string
-                                          operator:
-                                            type: string
-                                          values:
-                                            items:
-                                              type: string
-                                            type: array
-                                        required:
-                                        - key
-                                        - operator
-                                        type: object
-                                      type: array
-                                    matchLabels:
-                                      additionalProperties:
-                                        type: string
-                                      type: object
-                                  type: object
-                                  x-kubernetes-map-type: atomic
-                                namespaceSelector:
-                                  properties:
-                                    matchExpressions:
-                                      items:
-                                        properties:
-                                          key:
-                                            type: string
-                                          operator:
-                                            type: string
-                                          values:
-                                            items:
-                                              type: string
-                                            type: array
-                                        required:
-                                        - key
-                                        - operator
-                                        type: object
-                                      type: array
-                                    matchLabels:
-                                      additionalProperties:
-                                        type: string
-                                      type: object
-                                  type: object
-                                  x-kubernetes-map-type: atomic
-                                namespaces:
-                                  items:
-                                    type: string
-                                  type: array
-                                topologyKey:
-                                  type: string
-                              required:
-                              - topologyKey
-                              type: object
-                            weight:
-                              format: int32
-                              type: integer
-                          required:
-                          - podAffinityTerm
-                          - weight
-                          type: object
-                        type: array
-                      requiredDuringSchedulingIgnoredDuringExecution:
-                        items:
-                          properties:
-                            labelSelector:
-                              properties:
-                                matchExpressions:
-                                  items:
-                                    properties:
-                                      key:
-                                        type: string
-                                      operator:
-                                        type: string
-                                      values:
-                                        items:
-                                          type: string
-                                        type: array
-                                    required:
-                                    - key
-                                    - operator
-                                    type: object
-                                  type: array
-                                matchLabels:
-                                  additionalProperties:
-                                    type: string
-                                  type: object
-                              type: object
-                              x-kubernetes-map-type: atomic
-                            namespaceSelector:
-                              properties:
-                                matchExpressions:
-                                  items:
-                                    properties:
-                                      key:
-                                        type: string
-                                      operator:
-                                        type: string
-                                      values:
-                                        items:
-                                          type: string
-                                        type: array
-                                    required:
-                                    - key
-                                    - operator
-                                    type: object
-                                  type: array
-                                matchLabels:
-                                  additionalProperties:
-                                    type: string
-                                  type: object
-                              type: object
-                              x-kubernetes-map-type: atomic
-                            namespaces:
-                              items:
-                                type: string
-                              type: array
-                            topologyKey:
-                              type: string
-                          required:
-                          - topologyKey
-                          type: object
-                        type: array
-                    type: object
-                type: object
-          status:
-            description: Status defines the observed state of AWXMeshIngress
-            type: object
-            x-kubernetes-preserve-unknown-fields: true
-        type: object
-    served: true
-    storage: true
-    subresources:
-      status: {}

config/crd/bases/awx.ansible.com_awxrestores.yaml

@@ -39,14 +39,12 @@ spec:
           spec:
             type: object
             x-kubernetes-preserve-unknown-fields: true
-            required:
-            - deployment_name
             properties:
               backup_source:
                 description: Backup source
                 type: string
                 enum:
-                - Backup CR
+                - CR
                 - PVC
               deployment_name:
                 description: Name of the restored deployment. This should be different from the original deployment name
@@ -94,25 +92,6 @@ spec:
               postgres_image_version:
                 description: PostgreSQL container image version to use
                 type: string
-              spec_overrides:
-                description: Overrides for the AWX spec
-                # type: string
-                type: object
-                x-kubernetes-preserve-unknown-fields: true
-              image_pull_policy:
-                description: The image pull policy
-                type: string
-                default: IfNotPresent
-                enum:
-                - Always
-                - always
-                - Never
-                - never
-                - IfNotPresent
-                - ifnotpresent
-              db_management_pod_node_selector:
-                description: nodeSelector for the Postgres pods to backup
-                type: string
               no_log:
                 description: Configure no_log for no_log tasks
                 type: boolean
@@ -126,10 +105,6 @@ spec:
                 description: Maintain some of the recommended `app.kubernetes.io/*` labels on the resource (self)
                 type: boolean
                 default: true
-              force_drop_db:
-                description: Force drop the database before restoring. USE WITH CAUTION!
-                type: boolean
-                default: false
           status:
             type: object
             x-kubernetes-preserve-unknown-fields: true

config/crd/kustomization.yaml

@@ -5,5 +5,4 @@ resources:
 - bases/awx.ansible.com_awxs.yaml
 - bases/awx.ansible.com_awxbackups.yaml
 - bases/awx.ansible.com_awxrestores.yaml
-- bases/awx.ansible.com_awxmeshingresses.yaml
 #+kubebuilder:scaffold:crdkustomizeresource

config/default/kustomization.yaml

@@ -21,10 +21,12 @@ resources:
 # [PROMETHEUS] To enable prometheus monitor, uncomment all sections with 'PROMETHEUS'.
 #- ../prometheus
 
+patchesStrategicMerge:
 # Protect the /metrics endpoint by putting it behind auth.
 # If you want your controller-manager to expose the /metrics
 # endpoint w/o any authn/z, please comment the following line.
-apiVersion: kustomize.config.k8s.io/v1beta1
-kind: Kustomization
-patches:
-- path: manager_auth_proxy_patch.yaml
+- manager_auth_proxy_patch.yaml
+
+# Mount the controller config file for loading manager configurations
+# through a ComponentConfig type
+#- manager_config_patch.yaml

config/default/manager_auth_proxy_patch.yaml

@@ -12,10 +12,11 @@ spec:
       - name: kube-rbac-proxy
         securityContext:
           allowPrivilegeEscalation: false
-          capabilities:
-            drop:
-            - "ALL"
-        image: gcr.io/kubebuilder/kube-rbac-proxy:v0.15.0
+        # TODO(user): uncomment for common cases that do not require escalating privileges
+        # capabilities:
+        #   drop:
+        #     - "ALL"
+        image: gcr.io/kubebuilder/kube-rbac-proxy:v0.13.0
         args:
         - "--secure-listen-address=0.0.0.0:8443"
         - "--upstream=http://127.0.0.1:8080/"

config/manager/kustomization.yaml

@@ -5,9 +5,9 @@ generatorOptions:
   disableNameSuffixHash: true
 
 configMapGenerator:
-- files:
+- name: awx-manager-config
+  files:
   - controller_manager_config.yaml
-  name: awx-manager-config
 
 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization

config/manager/manager.yaml

@@ -39,7 +39,6 @@ spec:
         - --leader-elect
         - --leader-election-id=awx-operator
         image: controller:latest
-        imagePullPolicy: IfNotPresent
         name: awx-manager
         env:
         - name: ANSIBLE_GATHERING
@@ -52,6 +51,7 @@ spec:
               fieldPath: metadata.namespace
         securityContext:
           allowPrivilegeEscalation: false
+        # TODO(user): uncomment for common cases that do not require escalating privileges
           capabilities:
             drop:
             - "ALL"
@@ -73,7 +73,7 @@ spec:
             memory: "32Mi"
             cpu: "50m"
           limits:
-            memory: "4000Mi"
+            memory: "4096Mi"
             cpu: "2000m"
       serviceAccountName: controller-manager
       imagePullSecrets:

config/manifests/bases/awx-operator.clusterserviceversion.yaml

@@ -10,85 +10,12 @@ metadata:
     description: AWX provides a web-based user interface, REST API, and task engine
       built on top of Ansible.
     repository: https://github.com/ansible/awx-operator
-    support: forum.ansible.com
   name: awx-operator.v0.0.0
   namespace: placeholder
 spec:
   apiservicedefinitions: {}
   customresourcedefinitions:
     owned:
-    - description: Deploy a instance of AWX Mesh ingress to allow inbound connection
-        to the AWX Receptor Mesh.
-      displayName: AWX Mesh Ingress
-      kind: AWXMeshIngress
-      name: awxmeshingresses.awx.ansible.com
-      specDescriptors:
-      - displayName: Deployment Name
-        path: deployment_name
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:text
-      - displayName: External Hostname
-        path: external_hostname
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:text
-      - displayName: External IP Address
-        path: external_ipaddress
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:text
-      - displayName: Ingress Type
-        path: ingress_type
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:select:none
-        - urn:alm:descriptor:com.tectonic.ui:select:Ingress
-        - urn:alm:descriptor:com.tectonic.ui:select:IngressRouteTCP
-        - urn:alm:descriptor:com.tectonic.ui:select:Route
-      - displayName: Ingress API Version
-        path: ingress_api_version
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:text
-      - displayName: Ingress Annotations
-        path: ingress_annotations
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:text
-      - displayName: Ingress Class Name
-        path: ingress_class_name
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:text
-      - displayName: Ingress Controller
-        path: ingress_controller
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:text
-      - displayName: Node Selector
-        path: node_selector
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Tolerations
-        path: tolerations
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Topology Spread Constraints
-        path: topology_spread_constraints
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Affinity
-        path: affinity
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Optional API URLPATTERN Prefix
-        path: api_urlpattern_prefix
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:text
-      - displayName: Image Pull Secrets
-        path: image_pull_secrets
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:io.kubernetes:Secret
-      version: v1alpha1
     - description: Back up a deployment of the awx, including jobs, inventories, and
         credentials
       displayName: AWX Backup
@@ -121,24 +48,13 @@ spec:
       - displayName: Backup PVC Storage Class
         path: backup_storage_class
         x-descriptors:
-        - urn:alm:descriptor:io.kubernetes:StorageClass
+        - urn:alm:descriptor:com.tectonic.ui:text
         - urn:alm:descriptor:com.tectonic.ui:advanced
-      - displayName: Precreate Partition Hours
-        path: precreate_partition_hours
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:number
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
       - displayName: Database Backup Label Selector
         path: postgres_label_selector
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: PostgreSQL Security Context Settings
-        path: postgres_security_context_settings
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
       - displayName: PostgreSQL Image
         path: postgres_image
         x-descriptors:
@@ -149,36 +65,11 @@ spec:
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Image Pull Policy
-        path: image_pull_policy
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:imagePullPolicy
       - displayName: No Log Configuration
         path: no_log
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:booleanSwitch
-      - displayName: Set default labels on AWX resource?
-        path: set_self_labels
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:booleanSwitch
-      - displayName: Additional labels defined on the resource, which should be propagated
-          to child resources
-        path: additional_labels
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-      - displayName: Node Selector for backup management pod
-        path: db_management_pod_node_selector
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-      - displayName: Public Base URL
-        path: public_base_url
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:text
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
       statusDescriptors:
       - description: Persistent volume claim name used during backup
         displayName: Backup Claim
@@ -197,10 +88,10 @@ spec:
       kind: AWXRestore
       name: awxrestores.awx.ansible.com
       specDescriptors:
-      - description: Select what type of backup to specify. Backup CR, allows you
-          to specify the name of an AWXBackup object (recommended approach).  The
-          PVC option allows you to specify a custom PVC and directory to backup from.
-        displayName: Backup Source to restore from
+      - displayName: Backup Source to restore from
+        description: Select what type of backup to specify. Backup CR, allows you to specify
+          the name of an AWXBackup object (recommended approach).  The PVC option allows you to
+          specify a custom PVC and directory to backup from.
         path: backup_source
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:select:Backup CR
@@ -224,9 +115,8 @@ spec:
         path: backup_pvc_namespace
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:hidden
-      - description: This is the directory inside the PVC that your backup is stored
-          in.
-        displayName: Backup Directory
+      - displayName: Backup Directory
+        description: This is the directory inside the PVC that your backup is stored in.
         path: backup_dir
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:text
@@ -244,15 +134,6 @@ spec:
         path: postgres_image_version
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: AWX Spec Overrides
-        path: spec_overrides
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-      - displayName: Image Pull Policy
-        path: image_pull_policy
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:imagePullPolicy
       - displayName: Restore Management Pod Resource Requirements
         path: restore_resource_requirements
         x-descriptors:
@@ -263,25 +144,6 @@ spec:
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:booleanSwitch
-      - displayName: Set default labels on AWX resource?
-        path: set_self_labels
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:booleanSwitch
-      - displayName: Additional labels defined on the resource, which should be propagated
-          to child resources
-        path: additional_labels
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-      - displayName: Node Selector for backup management pod
-        path: db_management_pod_node_selector
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-      - displayName: Force drop database before restore
-        path: force_drop_db
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:booleanSwitch
       statusDescriptors:
       - description: The state of the restore
         displayName: Restore Status
@@ -289,13 +151,12 @@ spec:
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:text
       version: v1beta1
-    - description: Deploy a new instance of AWX. A standardized way to define, operate
-        and scale automation with Ansible.
+    - description: Deploy a new instance of AWX. A standardized way to define, operate and scale automation with Ansible.
       displayName: AWX
       kind: AWX
       name: awxs.awx.ansible.com
       specDescriptors:
-      - displayName: Hostname (Deprecated)
+      - displayName: Hostname
         path: hostname
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
@@ -325,14 +186,8 @@ spec:
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:io.kubernetes:Secret
-      - description: PostgreSQL dump additional parameters to exclude tables during migration to openshift
-        displayname: PostgreSQL Extra Arguments for Migration to Openshift
-        path: pg_dump_suffix
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - description: Name of the k8s secret the symmetric encryption key is stored
-          in.
-        displayName: Secret Key
+      - displayName: Secret Key
+        description: Name of the k8s secret the symmetric encryption key is stored in.
         path: secret_key_secret
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
@@ -371,7 +226,7 @@ spec:
         path: ingress_api_version
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:text
+        - urn:alm:descriptor:com.tectonic.ui:text 
       - displayName: Ingress Path
         path: ingress_path
         x-descriptors:
@@ -390,23 +245,12 @@ spec:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:text
         - urn:alm:descriptor:com.tectonic.ui:fieldDependency:ingress_type:Ingress
-      - displayName: Ingress TLS Secret (Deprecated)
+      - displayName: Ingress TLS Secret
         path: ingress_tls_secret
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:io.kubernetes:Secret
         - urn:alm:descriptor:com.tectonic.ui:fieldDependency:ingress_type:Ingress
-      - displayName: Ingress Hosts
-        path: ingress_hosts
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:text
-      - displayName: Ingress Controller
-        path: ingress_controller
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:text
-        - urn:alm:descriptor:com.tectonic.ui:fieldDependency:ingress_type:Ingress
       - displayName: LoadBalancer Annotations
         path: service_annotations
         x-descriptors:
@@ -426,18 +270,6 @@ spec:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:number
         - urn:alm:descriptor:com.tectonic.ui:fieldDependency:service_type:LoadBalancer
-      - displayName: LoadBalancer IP
-        path: loadbalancer_ip
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:string
-        - urn:alm:descriptor:com.tectonic.ui:fieldDependency:service_type:LoadBalancer
-      - displayName: LoadBalancer Class
-        path: loadbalancer_class
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:string
-        - urn:alm:descriptor:com.tectonic.ui:fieldDependency:service_type:LoadBalancer
       - displayName: Route API Version
         path: route_api_version
         x-descriptors:
@@ -476,11 +308,6 @@ spec:
         path: image_pull_secret
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: HostAliases for app containers
-        path: host_aliases
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:text
       - displayName: Web Container Resource Requirements
         path: web_resource_requirements
         x-descriptors:
@@ -496,105 +323,37 @@ spec:
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:resourceRequirements
-      - description: Sets permissions on the /var/lib/pgsql/data for postgres container using an init container (not Openshift)
-        displayName: PostgreSQL initialize data volume
-        path: postgres_data_volume_init
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - description: Customize the postgres init container commands (Non Openshift)
-        displayName: PostgreSQL Init Container Commands
-        path: postgres_init_container_commands
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - description: (Deprecated, use postgres_resource_requirements parameter instead)
-        displayName: PostgreSQL Init Container Resource Requirements
+      - displayName: PostgreSQL Init Container Resource Requirements
+        description: The PostgreSQL init container is not used when an external DB
+          is configured
         path: postgres_init_container_resource_requirements
         x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:hidden
+        - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:resourceRequirements
       - displayName: Redis Container Resource Requirements
         path: redis_resource_requirements
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:resourceRequirements
-      - displayName: Rsyslog Container Resource Requirements
-        path: rsyslog_resource_requirements
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:resourceRequirements
-      - description: The PostgreSQL container is not used when an external DB is configured
-        displayName: PostgreSQL Container Resource Requirements
+      - displayName: PostgreSQL Container Resource Requirements
+        description: The PostgreSQL container is not used when an external DB
+          is configured
         path: postgres_resource_requirements
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:resourceRequirements
-      - description: The PostgreSQL container is not used when an external DB is configured
-        displayName: PostgreSQL Container Storage Requirements
+      - displayName: PostgreSQL Container Storage Requirements
+        description: The PostgreSQL container is not used when an external DB
+          is configured
         path: postgres_storage_requirements
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
-      - description: Init Container resource requirements
-        path: init_container_resource_requirements
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:resourceRequirements
       - displayName: Replicas
         path: replicas
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:number
-      - displayName: Web Replicas
-        path: web_replicas
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:number
-      - displayName: Uwsgi Listen Queue Length
-        path: uwsgi_listen_queue_size
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:number
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Uwsgi Timeout
-        path: uwsgi_timeout
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:number
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Uwsgi Processes
-        path: uwsgi_processes
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:number
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: NGINX Worker Processes
-        path: nginx_worker_processes
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:number
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: NGINX Worker Connections
-        path: nginx_worker_connections
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:number
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: NGINX Worker Process CPU Affinity
-        path: nginx_worker_cpu_affinity
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:string
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: NGINX Listen Queue Length
-        path: nginx_listen_queue_size
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:number
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Task Replicas
-        path: task_replicas
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:number
       - displayName: Remove used secrets on instance removal?
         path: garbage_collect_secrets
         x-descriptors:
@@ -690,56 +449,29 @@ spec:
       - displayName: Postgres Storage Class
         path: postgres_storage_class
         x-descriptors:
-        - urn:alm:descriptor:io.kubernetes:StorageClass
         - urn:alm:descriptor:com.tectonic.ui:advanced
+        - urn:alm:descriptor:com.tectonic.ui:hidden
+      - displayName: Postgres Datapath
+        path: postgres_data_path
+        x-descriptors:
+        - urn:alm:descriptor:com.tectonic.ui:advanced
+        - urn:alm:descriptor:com.tectonic.ui:hidden
       - displayName: Postgres Extra Arguments
         path: postgres_extra_args
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:hidden
-      - description: Specify extra volumes to add to the postgres pod
-        displayName: Postgres Extra Volumes
-        path: postgres_extra_volumes
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - description: Specify volume mounts to be added to Postgres container
-        displayName: Postgres Extra Volume Mounts
-        path: postgres_extra_volume_mounts
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Enable Postgres Keepalives
-        path: postgres_keepalives
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Postgres Keepalives Count
-        path: postgres_keepalives_count
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Postgres Keepalives Idle
-        path: postgres_keepalives_idle
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Postgres Keepalives Interval
-        path: postgres_keepalives_interval
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
       - displayName: Certificate Authorirty Trust Bundle
         path: ca_trust_bundle
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: LDAP Certificate Authority Trust Bundle (Deprecated)
+      - displayName: LDAP Certificate Authority Trust Bundle
         path: ldap_cacert_secret
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:io.kubernetes:Secret
-      - displayName: LDAP Password Secret (Deprecated)
+      - displayName: LDAP Password Secret
         path: ldap_password_secret
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
@@ -774,7 +506,7 @@ spec:
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:fieldDependency:projects_use_existing_claim:_No_
-        - urn:alm:descriptor:io.kubernetes:StorageClass
+        - urn:alm:descriptor:com.tectonic.ui:text
       - description: Projects Storage Size
         displayName: Projects Storage Size
         path: projects_storage_size
@@ -859,28 +591,6 @@ spec:
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Rsyslog Args
-        path: rsyslog_args
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Rsyslog Command
-        path: rsyslog_command
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - description: Environment variables to be added to Rsyslog container
-        displayName: Rsyslog Extra Env
-        path: rsyslog_extra_env
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - description: Specify volume mounts to be added to Rsyslog container
-        displayName: Rsyslog Extra Volume Mounts
-        path: rsyslog_extra_volume_mounts
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
       - description: Specify extra volumes to add to the application pod
         displayName: Extra Volumes
         path: extra_volumes
@@ -892,46 +602,16 @@ spec:
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Web Node Selector
-        path: web_node_selector
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Task Node Selector
-        path: task_node_selector
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
       - displayName: Topology Spread Constraints
         path: topology_spread_constraints
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Web Topology Spread Constraints
-        path: web_topology_spread_constraints
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Task Topology Spread Constraints
-        path: task_topology_spread_constraints
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
       - displayName: Affinity
         path: affinity
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Web Affinity
-        path: web_affinity
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Task Affinity
-        path: task_affinity
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
       - displayName: Control Plane Priority Class
         path: control_plane_priority_class
         x-descriptors:
@@ -958,36 +638,11 @@ spec:
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Task Annotations
-        path: task_annotations
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Web Annotations
-        path: web_annotations
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Postgres Annotations
-        path: postgres_annotations
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
       - displayName: Tolerations
         path: tolerations
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Web Tolerations
-        path: web_tolerations
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Task Tolerations
-        path: task_tolerations
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
       - displayName: CSRF Cookie Secure Setting
         path: csrf_cookie_secure
         x-descriptors:
@@ -998,21 +653,11 @@ spec:
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Receptor Log Level
-        path: receptor_log_level
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Extra Settings
+      - displayName: API Extra Settings
         path: extra_settings
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:hidden
-      - displayName: Extra Settings Files
-        path: extra_settings_files
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:hidden
       - displayName: No Log Configuration
         path: no_log
         x-descriptors:
@@ -1073,8 +718,8 @@ spec:
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:booleanSwitch
-      - displayName: Additional labels defined on the resource, which should be propagated
-          to child resources
+      - displayName: Additional labels defined on the resource, which should be
+          propagated to child resources
         path: additional_labels
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
@@ -1084,90 +729,6 @@ spec:
         x-descriptors:
         - urn:alm:descriptor:com.tectonic.ui:advanced
         - urn:alm:descriptor:com.tectonic.ui:booleanSwitch
-      - displayName: Metrics-Utility Enabled
-        path: metrics_utility_enabled
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:booleanSwitch
-      - displayName: Metrics-Utility Image
-        path: metrics_utility_image
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:text
-        - urn:alm:descriptor:com.tectonic.ui:fieldDependency:metrics_utility_enabled:true
-      - displayName: Metrics-Utility Image Version
-        path: metrics_utility_image_version
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:text
-        - urn:alm:descriptor:com.tectonic.ui:fieldDependency:metrics_utility_enabled:true
-      - displayName: Metrics-Utility Image PullPolicy
-        path: metrics_utility_image_pull_policy
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:imagePullPolicy
-        - urn:alm:descriptor:com.tectonic.ui:fieldDependency:metrics_utility_enabled:true
-      - displayName: Metrics-Utility ConfigMap
-        path: metrics_utility_configmap
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:io.kubernetes:ConfigMap
-        - urn:alm:descriptor:com.tectonic.ui:fieldDependency:metrics_utility_enabled:true
-      - displayName: Metrics-Utility Secret
-        path: metrics_utility_secret
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:io.kubernetes:Secret
-        - urn:alm:descriptor:com.tectonic.ui:fieldDependency:metrics_utility_enabled:true
-      - displayName: Metrics-Utility Gather Data CronJob Schedule
-        path: metrics_utility_cronjob_gather_schedule
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:text
-        - urn:alm:descriptor:com.tectonic.ui:fieldDependency:metrics_utility_enabled:true
-      - displayName: Metrics-Utility Report CronJob Schedule
-        path: metrics_utility_cronjob_report_schedule
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:text
-        - urn:alm:descriptor:com.tectonic.ui:fieldDependency:metrics_utility_enabled:true
-      - displayName: Metrics-Utility Ship Target
-        path: metrics_utility_ship_target
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:text
-        - urn:alm:descriptor:com.tectonic.ui:fieldDependency:metrics_utility_enabled:true
-      - displayName: Metrics-Utility PVC Claim
-        path: metrics_utility_pvc_claim
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:text
-        - urn:alm:descriptor:com.tectonic.ui:fieldDependency:metrics_utility_enabled:true
-      - displayName: Metrics-Utility PVC Claim Size
-        path: metrics_utility_pvc_claim_size
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:text
-        - urn:alm:descriptor:com.tectonic.ui:fieldDependency:metrics_utility_enabled:true
-      - displayName: Metrics-Utility PVC Claim Storage Class
-        path: metrics_utility_pvc_claim_storage_class
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:io.kubernetes:StorageClass
-        - urn:alm:descriptor:com.tectonic.ui:fieldDependency:metrics_utility_enabled:true
-      - displayName: Metrics-Utility Enabled Shipping to Red Hat Hybrid Cloud Console
-        path: metrics_utility_console_enabled
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:booleanSwitch
-        - urn:alm:descriptor:com.tectonic.ui:fieldDependency:metrics_utility_enabled:true
-      - description: Scale down deployments to put AWX into an idle state
-        displayName: Idle AWX
-        path: idle_deployment
-        x-descriptors:
-        - urn:alm:descriptor:com.tectonic.ui:advanced
-        - urn:alm:descriptor:com.tectonic.ui:booleanSwitch
-        - urn:alm:descriptor:com.tectonic.ui:hidden
       statusDescriptors:
       - description: Route to access the instance deployed
         displayName: URL
@@ -1243,7 +804,7 @@ spec:
   - email: awx-project@googlegroups.com
     name: AWX Team
   maturity: alpha
-  minKubeVersion: 1.22.15
+  MinKubeVersion: 1.22.15
   provider:
     name: Ansible
     url: github.com/ansible/awx-operator

config/rbac/awxmeshingress_editor_role.yaml

@@ -1,31 +0,0 @@
-# permissions for end users to edit awxmeshingresses.
-apiVersion: rbac.authorization.k8s.io/v1
-kind: ClusterRole
-metadata:
-  labels:
-    app.kubernetes.io/name: clusterrole
-    app.kubernetes.io/instance: awxmeshingress-editor-role
-    app.kubernetes.io/component: rbac
-    app.kubernetes.io/created-by: awx-operator
-    app.kubernetes.io/part-of: awx-operator
-    app.kubernetes.io/managed-by: kustomize
-  name: awxmeshingress-editor-role
-rules:
-- apiGroups:
-  - awx.ansible.com
-  resources:
-  - awxmeshingresses
-  verbs:
-  - create
-  - delete
-  - get
-  - list
-  - patch
-  - update
-  - watch
-- apiGroups:
-  - awx.ansible.com
-  resources:
-  - awxmeshingresses/status
-  verbs:
-  - get

config/rbac/awxmeshingress_viewer_role.yaml

@@ -1,27 +0,0 @@
-# permissions for end users to view awxmeshingresses.
-apiVersion: rbac.authorization.k8s.io/v1
-kind: ClusterRole
-metadata:
-  labels:
-    app.kubernetes.io/name: clusterrole
-    app.kubernetes.io/instance: awxmeshingress-viewer-role
-    app.kubernetes.io/component: rbac
-    app.kubernetes.io/created-by: awx-operator
-    app.kubernetes.io/part-of: awx-operator
-    app.kubernetes.io/managed-by: kustomize
-  name: awxmeshingress-viewer-role
-rules:
-- apiGroups:
-  - awx.ansible.com
-  resources:
-  - awxmeshingresses
-  verbs:
-  - get
-  - list
-  - watch
-- apiGroups:
-  - awx.ansible.com
-  resources:
-  - awxmeshingresses/status
-  verbs:
-  - get

config/rbac/role.yaml

@@ -78,18 +78,6 @@ rules:
       - patch
       - update
       - watch
-  - apiGroups:
-      - batch
-    resources:
-      - cronjobs
-      - jobs
-    verbs:
-      - get
-      - list
-      - create
-      - patch
-      - update
-      - watch
   - apiGroups:
       - monitoring.coreos.com
     resources:
@@ -136,16 +124,3 @@ rules:
       - awxrestores
     verbs:
       - '*'
-  - apiGroups:
-      - traefik.containo.us
-      - traefik.io
-    resources:
-      - ingressroutetcps
-    verbs:
-      - get
-      - list
-      - create
-      - delete
-      - patch
-      - update
-      - watch

config/samples/awx_v1alpha1_awxmeshingress.yaml

@@ -1,8 +0,0 @@
-# Placeholder to pass CI and allow bundle generation
----
-apiVersion: awx.ansible.com/v1alpha1
-kind: AWXMeshIngress
-metadata:
-  name: example-awx-mesh-ingress
-spec:
-  deployment_name: example-awx

config/samples/awx_v1beta1_awx_resource_limits.yaml

@@ -1,48 +0,0 @@
----
-apiVersion: awx.ansible.com/v1beta1
-kind: AWX
-metadata:
-  name: awx-with-limits
-spec:
-  task_resource_requirements:
-    requests:
-      cpu: 100m
-      memory: 128Mi
-    limits:
-      cpu: 2000m
-      memory: 4Gi
-  web_resource_requirements:
-    requests:
-      cpu: 100m
-      memory: 128Mi
-    limits:
-      cpu: 1000m
-      memory: 4Gi
-  ee_resource_requirements:
-    requests:
-      cpu: 100m
-      memory: 64Mi
-    limits:
-      cpu: 1000m
-      memory: 4Gi
-  redis_resource_requirements:
-    requests:
-      cpu: 50m
-      memory: 64Mi
-    limits:
-      cpu: 1000m
-      memory: 4Gi
-  rsyslog_resource_requirements:
-    requests:
-      cpu: 100m
-      memory: 128Mi
-    limits:
-      cpu: 1000m
-      memory: 2Gi
-  init_container_resource_requirements:
-    requests:
-      cpu: 100m
-      memory: 128Mi
-    limits:
-      cpu: 1000m
-      memory: 2Gi

config/samples/kustomization.yaml

@@ -3,5 +3,4 @@ resources:
 - awx_v1beta1_awx.yaml
 - awx_v1beta1_awxbackup.yaml
 - awx_v1beta1_awxrestore.yaml
-- awx_v1alpha1_awxmeshingress.yaml
 #+kubebuilder:scaffold:manifestskustomizesamples

config/testing/kustomization.yaml

@@ -7,6 +7,10 @@ namePrefix: osdk-
 #commonLabels:
 #  someName: someValue
 
+patchesStrategicMerge:
+- manager_image.yaml
+- debug_logs_patch.yaml
+- ../default/manager_auth_proxy_patch.yaml
 
 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
@@ -17,7 +21,3 @@ resources:
 images:
 - name: testing
   newName: testing-operator
-patches:
-- path: manager_image.yaml
-- path: debug_logs_patch.yaml
-- path: ../default/manager_auth_proxy_patch.yaml

dev/awx-cr/awx-cr-settings.yml

@@ -1,24 +0,0 @@
----
-apiVersion: awx.ansible.com/v1beta1
-kind: AWX
-metadata:
-  name: awx
-spec:
-  service_type: clusterip
-  ingress_type: route
-  no_log: false
-
-  # Secrets
-  admin_password_secret: custom-admin-password
-  postgres_configuration_secret: custom-pg-configuration
-  secret_key_secret: custom-secret-key
-
-  # Resource Requirements
-  postgres_storage_requirements:
-    requests:
-      storage: 10Gi
-
-  # Extra Settings
-  extra_settings:
-    - setting: MAX_PAGE_SIZE
-      value: "500"

dev/awx-cr/awx-k8s-ingress.yml

@@ -1,13 +0,0 @@
----
-apiVersion: awx.ansible.com/v1beta1
-kind: AWX
-metadata:
-  name: awx
-spec:
-  service_type: nodeport
-  ingress_type: ingress
-
-  # Secrets
-  admin_password_secret: custom-admin-password
-  postgres_configuration_secret: custom-pg-configuration
-  secret_key_secret: custom-secret-key

dev/awx-cr/awx-openshift-cr.yml

@@ -1,13 +0,0 @@
----
-apiVersion: awx.ansible.com/v1beta1
-kind: AWX
-metadata:
-  name: awx
-spec:
-  service_type: clusterip
-  ingress_type: Route
-
-  # Secrets
-  admin_password_secret: custom-admin-password
-  postgres_configuration_secret: custom-pg-configuration
-  secret_key_secret: custom-secret-key

dev/secrets/admin-password-secret.yml

@@ -1,7 +0,0 @@
----
-apiVersion: v1
-kind: Secret
-metadata:
-  name: custom-admin-password
-stringData:
-  password: 'password'

dev/secrets/custom-secret-key.yml

@@ -1,7 +0,0 @@
----
-apiVersion: v1
-kind: Secret
-metadata:
-  name: custom-secret-key
-stringData:
-  secret_key: 'awxsecret'

dev/secrets/external-pg-secret.yml

@@ -1,12 +0,0 @@
----
-apiVersion: v1
-kind: Secret
-metadata:
-  name: external-pg-secret
-stringData:
-  database: 'awx'
-  host: 'awx-postgres'
-  password: 'test'
-  port: '5432'
-  type: 'managed'
-  username: 'awx'

docs/README.md

@@ -1,16 +0,0 @@
-# Building the Ansible AWX Operator Docs
-
-To build the AWX Operator docs locally:
-
-1. Clone the AWX operator repository.
-1. Preferrably, create a virtual environment for installing the dependencies.  
-   a. `python3 -m venv venv`  
-   b. `source venv/bin/activate`
-1. From the root directory:  
-   a. `pip install -r docs/requirements.txt`  
-   b. `mkdocs build`
-1. View the docs in your browser:  
-   a. `mkdocs serve`  
-   b. Open your browser and navigate to `http://127.0.0.1:8000/`
-
-This will create a new directory called `site/` in the root of your clone containing the index.html and static files.

docs/contributors-guide/author.md

@@ -1,3 +0,0 @@
-# Author
-
-This operator was originally built in 2019 by [Jeff Geerling](https://www.jeffgeerling.com) and is now maintained by the Ansible Team

docs/contributors-guide/code-of-conduct.md

@@ -1,3 +0,0 @@
-# Code of Conduct
-
-We ask all of our community members and contributors to adhere to the [Ansible code of conduct](http://docs.ansible.com/ansible/latest/community/code_of_conduct.html). If you have questions or need assistance, please reach out to our community team at [codeofconduct@ansible.com](mailto:codeofconduct@ansible.com)

docs/contributors-guide/contributing.md

@@ -1,5 +0,0 @@
-# Contributing
-
-Please visit [our contributing guidelines](https://github.com/ansible/awx-operator/blob/devel/CONTRIBUTING.md).
-
-For docs changes, create PRs on the appropriate files in the `/docs` folder.

docs/contributors-guide/get-involved.md

@@ -1,24 +0,0 @@
-# Get Involved
-
-We welcome your feedback, questions and ideas. Here's how to reach the community.
-
-## Forum
-
-Join the [Ansible Forum](https://forum.ansible.com) as a single starting point and our default communication platform for questions and help, development discussions, events, and much more. [Register](https://forum.ansible.com/signup?) to join the community. Search by categories and tags to find interesting topics or start a new one; subscribe only to topics you need!
-
-* [Get Help](https://forum.ansible.com/c/help/6): get help or help others. Please add appropriate tags if you start new discussions, for example `awx-operator` and  `documentation`.
-* [Posts tagged with 'awx-operator'](https://forum.ansible.com/tag/awx-operator): subscribe to participate in project-related conversations.
-* [Bullhorn newsletter](https://docs.ansible.com/ansible/devel/community/communication.html#the-bullhorn) used to announce releases and important changes.
-* [Social Spaces](https://forum.ansible.com/c/chat/4): gather and interact with fellow enthusiasts.
-* [News & Announcements](https://forum.ansible.com/c/news/5): track project-wide announcements including social events.
-
-For more information on the forum navigation, see [Navigating the Ansible forum](https://forum.ansible.com/t/navigating-the-ansible-forum-tags-categories-and-concepts/39) post.
-
-## Matrix
-
-For real-time interactions, conversations in the community happen over the Matrix protocol in the following channels:
-
-* [#awx:ansible.com](https://matrix.to/#/#awx:ansible.com): AWX and AWX-Operator project-related discussions.
-* [#docs:ansible.im](https://matrix.to/#/#docs:ansible.im): Ansible, AWX and AWX-Operator documentation-related discussions.
-
-For more information, see the community-hosted [Matrix FAQ](https://hackmd.io/@ansible-community/community-matrix-faq).

docs/contributors-guide/release-process.md

@@ -1,27 +0,0 @@
-# Release Process
-
-The first step is to create a draft release. Typically this will happen in the [Stage Release](https://github.com/ansible/awx/blob/devel/.github/workflows/stage.yml) workflow for AWX and you don't need to do it as a separate step.
-
-If you need to do an independent release of the operator, you can run the [Stage Release](https://github.com/ansible/awx-operator/blob/devel/.github/workflows/stage.yml) in the awx-operator repo. Both of these workflows will run smoke tests, so there is no need to do this manually.
-
-After the draft release is created, publish it and the [Promote AWX Operator image](https://github.com/ansible/awx-operator/blob/devel/.github/workflows/promote.yaml) will run, which will:
-
-- Publish image to Quay
-- Release Helm chart
-
-After the GHA is complete, the final step is to run the [publish-to-operator-hub.sh](https://github.com/ansible/awx-operator/blob/devel/hack/publish-to-operator-hub.sh) script, which will create a PR in the following repos to add the new awx-operator bundle version to OperatorHub:
-
-- <https://github.com/k8s-operatorhub/community-operators> (community operator index)
-- <https://github.com/redhat-openshift-ecosystem/community-operators-prod> (operator index shipped with Openshift)
-
-!!! note
-    The usage is documented in the script itself, but here is an example of how you would use the script to publish the 2.5.3 awx-opeator bundle to OperatorHub.
-    Note that you need to specify the version being released, as well as the previous version. This is because the bundle has a pointer to the previous version that is it being upgrade from. This is used by OLM to create a dependency graph.
-
-    ```bash
-    VERSION=2.5.3 PREV_VERSION=2.5.2 ./hack/publish-to-operator-hub.sh
-    ```
-
-    There are some quirks with running this on OS X that still need to be fixed, but the script runs smoothly on linux.
-
-As soon as CI completes successfully, the PR's will be auto-merged. Please remember to monitor those PR's to make sure that CI passes, sometimes it needs a retry.

docs/debugging.md

@@ -0,0 +1,64 @@
+# Iterating on the installer without deploying the operator
+
+Go through the [normal basic install](https://github.com/ansible/awx-operator/blob/devel/README.md#basic-install) steps.
+
+Install some dependencies:
+
+```
+$ ansible-galaxy collection install -r molecule/requirements.yml
+$ pip install -r molecule/requirements.txt
+```
+
+To prevent the changes we're about to make from being overwritten, scale down any running instance of the operator:
+
+```
+$ kubectl scale deployment awx-operator-controller-manager --replicas=0
+```
+
+Create a playbook that invokes the installer role (the operator uses ansible-runner's role execution feature):
+
+```yaml
+# run.yml
+---
+- hosts: localhost
+  roles:
+    - installer
+```
+
+Create a vars file:
+
+```yaml
+# vars.yml
+---
+ansible_operator_meta:
+  name: awx
+  namespace: awx
+service_type: nodeport
+```
+The vars file will replace the awx resource so any value that you wish to over ride using the awx resource, put in the vars file. For example, if you wish to use your own image, version and pull policy, you can specify it like below:
+
+```yaml
+# vars.yml
+---
+ansible_operator_meta:
+  name: awx
+  namespace: awx
+service_type: nodeport
+image: $DEV_DOCKER_TAG_BASE/awx_kube_devel
+image_pull_policy: Always
+image_version: $COMPOSE_TAG
+```
+
+Run the installer:
+
+```
+$ ansible-playbook run.yml -e @vars.yml -v
+```
+
+Grab the URL and admin password:
+
+```
+$ minikube service awx-service --url -n awx
+$ minikube kubectl get secret awx-admin-password -- -o jsonpath="{.data.password}" | base64 --decode
+LU6lTfvnkjUvDwL240kXKy1sNhjakZmT
+```

docs/development.md

@@ -1,58 +0,0 @@
-# Development Guide
-
-There are development scripts and yaml exaples in the [`dev/`](../dev) directory that, along with the up.sh and down.sh scripts in the root of the repo, can be used to build, deploy and test changes made to the awx-operator.
-
-
-## Build and Deploy
-
-
-If you clone the repo, and make sure you are logged in at the CLI with oc and your cluster, you can run:
-
-```
-export QUAY_USER=username
-export NAMESPACE=awx
-export TAG=test
-./up.sh
-```
-
-You can add those variables to your .bashrc file so that you can just run `./up.sh` in the future.
-
-> Note: the first time you run this, it will create quay.io repos on your fork. You will need to either make those public, or create a global pull secret on your Openshift cluster.
-
-To get the URL, if on **Openshift**, run:
-
-```
-$ oc get route
-```
-
-On **k8s with ingress**, run:
-
-```
-$ kubectl get ing
-```
-
-On **k8s with nodeport**, run:
-
-```
-$ kubectl get svc
-```
-
-The URL is then `http://<Node-IP>:<NodePort>`
-
-> Note: NodePort will only work if you expose that port on your underlying k8s node, or are accessing it from localhost.
-
-By default, the usename and password will be admin and password if using the `up.sh` script because it pre-creates a custom admin password k8s secret and specifies it on the AWX custom resource spec. Without that, a password would have been generated and stored in a k8s secret named <deployment-name>-admin-password.
-
-## Clean up
-
-
-Same thing for cleanup, just run ./down.sh and it will clean up your namespace on that cluster
-
-
-```
-./down.sh
-```
-
-## Running CI tests locally
-
-More tests coming soon...

docs/index.md

@@ -1 +0,0 @@
-../README.md

docs/installation/basic-install.md

@@ -1,177 +0,0 @@
-# Basic Install
-
-After cloning this repository, you must choose the tag to run:
-
-```sh
-git clone git@github.com:ansible/awx-operator.git
-cd awx-operator
-git tag
-git checkout tags/<tag>
-
-# For instance:
-git checkout tags/2.7.2
-```
-
-If you work from a fork and made modifications since the tag was issued, you must provide the VERSION number to deploy. Otherwise the operator will get stuck in "ImagePullBackOff" state:
-
-```sh
-export VERSION=<tag>
-
-# For instance:
-export VERSION=2.7.2
-```
-
-Once you have a running Kubernetes cluster, you can deploy AWX Operator into your cluster using [Kustomize](https://kubectl.docs.kubernetes.io/guides/introduction/kustomize/). Since kubectl version 1.14 kustomize functionality is built-in (otherwise, follow the instructions here to install the latest version of Kustomize: <https://kubectl.docs.kubernetes.io/installation/kustomize/>)
-
-!!! tip
-    If you don't have a Kubernetes cluster, you can use [Minikube](https://minikube.sigs.k8s.io/docs/) for testing purposes. See the [Minikube install docs](./creating-a-minikube-cluster-for-testing.md) for more details.
-
-!!! note
-    Some things may need to be configured slightly differently for different Kubernetes flavors for the networking aspects. When installing on Kind, see the [kind install docs](./kind-install.md) for more details.
-
-There is a make target you can run:
-
-```sh
-make deploy
-```
-
-If you have a custom operator image you have built, you can specify it with:
-
-```sh
-IMG=quay.io/$YOURNAMESPACE/awx-operator:$YOURTAG make deploy
-```
-
-Otherwise, you can manually create a file called `kustomization.yaml` with the following content:
-
-```yaml
-apiVersion: kustomize.config.k8s.io/v1beta1
-kind: Kustomization
-resources:
-  # Find the latest tag here: https://github.com/ansible/awx-operator/releases
-  - github.com/ansible/awx-operator/config/default?ref=<tag>
-
-# Set the image tags to match the git version from above
-images:
-  - name: quay.io/ansible/awx-operator
-    newTag: <tag>
-
-# Specify a custom namespace in which to install AWX
-namespace: awx
-```
-
-!!! tip
-    If you need to change any of the default settings for the operator (such as resources.limits), you can add [patches](https://kubectl.docs.kubernetes.io/references/kustomize/kustomization/patches/) at the bottom of your kustomization.yaml file.
-
-Install the manifests by running this:
-
-```sh
-$ kubectl apply -k .
-namespace/awx created
-customresourcedefinition.apiextensions.k8s.io/awxbackups.awx.ansible.com created
-customresourcedefinition.apiextensions.k8s.io/awxrestores.awx.ansible.com created
-customresourcedefinition.apiextensions.k8s.io/awxs.awx.ansible.com created
-serviceaccount/awx-operator-controller-manager created
-role.rbac.authorization.k8s.io/awx-operator-awx-manager-role created
-role.rbac.authorization.k8s.io/awx-operator-leader-election-role created
-clusterrole.rbac.authorization.k8s.io/awx-operator-metrics-reader created
-clusterrole.rbac.authorization.k8s.io/awx-operator-proxy-role created
-rolebinding.rbac.authorization.k8s.io/awx-operator-awx-manager-rolebinding created
-rolebinding.rbac.authorization.k8s.io/awx-operator-leader-election-rolebinding created
-clusterrolebinding.rbac.authorization.k8s.io/awx-operator-proxy-rolebinding created
-configmap/awx-operator-awx-manager-config created
-service/awx-operator-controller-manager-metrics-service created
-deployment.apps/awx-operator-controller-manager created
-```
-
-Wait a bit and you should have the `awx-operator` running:
-
-```sh
-$ kubectl get pods -n awx
-NAME                                               READY   STATUS    RESTARTS   AGE
-awx-operator-controller-manager-66ccd8f997-rhd4z   2/2     Running   0          11s
-```
-
-So we don't have to keep repeating `-n awx`, let's set the current namespace for `kubectl`:
-
-```sh
-kubectl config set-context --current --namespace=awx
-```
-
-Next, create a file named `awx-demo.yml` in the same folder with the suggested content below. The `metadata.name` you provide will be the name of the resulting AWX deployment.
-
-!!! note
-    If you deploy more than one AWX instance to the same namespace, be sure to use unique names.
-
-```yaml
----
-apiVersion: awx.ansible.com/v1beta1
-kind: AWX
-metadata:
-  name: awx-demo
-spec:
-  service_type: nodeport
-```
-
-!!! tip
-    It may make sense to create and specify your own secret key for your deployment so that if the k8s secret gets deleted, it can be re-created if needed.  If it is not provided, one will be auto-generated, but cannot be recovered if lost. Read more [here](../user-guide/admin-user-account-configuration.md#secret-key-configuration).
-
-If you are on Openshift, you can take advantage of Routes by specifying the following your spec. This will automatically create a Route for you with a custom hostname. This can be found on the Route section of the Openshift Console.
-
-```yaml
----
-apiVersion: awx.ansible.com/v1beta1
-kind: AWX
-metadata:
-  name: awx-demo
-spec:
-  service_type: clusterip
-  ingress_type: Route
-```
-
-Make sure to add this new file to the list of `resources` in your `kustomization.yaml` file:
-
-```yaml
-...
-resources:
-  - github.com/ansible/awx-operator/config/default?ref=<tag>
-  # Add this extra line:
-  - awx-demo.yml
-...
-```
-
-Finally, apply the changes to create the AWX instance in your cluster:
-
-```sh
-kubectl apply -k .
-```
-
-After a few seconds, you should see the operator begin to create new resources:
-
-```sh
-$ kubectl get pods -l "app.kubernetes.io/managed-by=awx-operator"
-NAME                        READY   STATUS    RESTARTS   AGE
-awx-demo-77d96f88d5-pnhr8   4/4     Running   0          3m24s
-awx-demo-postgres-0         1/1     Running   0          3m34s
-
-$ kubectl get svc -l "app.kubernetes.io/managed-by=awx-operator"
-NAME                TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)        AGE
-awx-demo-postgres   ClusterIP   None           <none>        5432/TCP       4m4s
-awx-demo-service    NodePort    10.109.40.38   <none>        80:31006/TCP   3m56s
-```
-
-After a few minutes, the new AWX instance will be deployed. You can look at the operator pod logs in order to know where the installation process is at:
-
-```sh
-kubectl logs -f deployments/awx-operator-controller-manager -c awx-manager
-```
-
-Once deployed, your AWX instance should now be reachable at `http://localhost:<assigned-nodeport>/` (in this case, `http://localhost:31006/`).
-
-By default, the admin user is `admin` and the password is available in the `<resourcename>-admin-password` secret. To retrieve the admin password, run:
-
-```sh
-$ kubectl get secret awx-demo-admin-password -o jsonpath="{.data.password}" | base64 --decode ; echo
-yDL2Cx5Za94g9MvBP6B73nzVLlmfgPjR
-```
-
-You just completed the most basic install of an AWX instance via this operator. Congratulations!!!

docs/installation/creating-a-minikube-cluster-for-testing.md

@@ -1,61 +0,0 @@
-# Creating a minikube cluster for testing
-
-If you do not have an existing cluster, the `awx-operator` can be deployed on a [Minikube](https://minikube.sigs.k8s.io/docs/) cluster for testing purposes. Due to different OS and hardware environments, please refer to the official Minikube documentation for further information.
-
-```sh
-$ minikube start --cpus=4 --memory=6g --addons=ingress
-😄  minikube v1.23.2 on Fedora 34
-✨  Using the docker driver based on existing profile
-👍  Starting control plane node minikube in cluster minikube
-🚜  Pulling base image ...
-🏃  Updating the running docker "minikube" container ...
-🐳  Preparing Kubernetes v1.22.2 on Docker 20.10.8 ...
-🔎  Verifying Kubernetes components...
-    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
-    ▪ Using image k8s.gcr.io/ingress-nginx/controller:v1.0.0-beta.3
-    ▪ Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.0
-    ▪ Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.0
-🔎  Verifying ingress addon...
-🌟  Enabled addons: storage-provisioner, default-storageclass, ingress
-🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
-```
-
-Once Minikube is deployed, check if the node(s) and `kube-apiserver` communication is working as expected.
-
-```sh
-$ minikube kubectl -- get nodes
-NAME       STATUS   ROLES                  AGE    VERSION
-minikube   Ready    control-plane,master   113s   v1.22.2
-
-$ minikube kubectl -- get pods -A
-NAMESPACE       NAME                                        READY   STATUS      RESTARTS   AGE
-ingress-nginx   ingress-nginx-admission-create--1-kk67h     0/1     Completed   0          2m1s
-ingress-nginx   ingress-nginx-admission-patch--1-7mp2r      0/1     Completed   1          2m1s
-ingress-nginx   ingress-nginx-controller-69bdbc4d57-bmwg8   1/1     Running     0          2m
-kube-system     coredns-78fcd69978-q7nmx                    1/1     Running     0          2m
-kube-system     etcd-minikube                               1/1     Running     0          2m12s
-kube-system     kube-apiserver-minikube                     1/1     Running     0          2m16s
-kube-system     kube-controller-manager-minikube            1/1     Running     0          2m12s
-kube-system     kube-proxy-5mmnw                            1/1     Running     0          2m1s
-kube-system     kube-scheduler-minikube                     1/1     Running     0          2m15s
-kube-system     storage-provisioner                         1/1     Running     0          2m11s
-```
-
-It is not required for `kubectl` to be separately installed since it comes already wrapped inside minikube. As demonstrated above, simply prefix `minikube kubectl --` before kubectl command, i.e. `kubectl get nodes` would become `minikube kubectl -- get nodes`
-
-Let's create an alias for easier usage:
-
-```sh
-alias kubectl="minikube kubectl --"
-```
-
-Now, you can proceed with the installation of the AWX Operator and AWX. Please refer to the [Basic Install](basic-install.md) for further instructions.
-
-!!! tip
-    Once your AWX has been deployed, the AWX instance will be accessible by running:
-
-    ```sh
-    minikube service -n awx awx-demo-service --url
-    ```
-
-For an example using the Nginx Ingress Controller in Minikube, don't miss our [demo video](https://asciinema.org/a/416946).

docs/installation/kind-install.md

@@ -1,119 +0,0 @@
-# AWX Operator on Kind
-
-## Kind Install
-
-Install Kind by running the following. Refer to the [official Kind documentation](https://kind.sigs.k8s.io/docs/user/quick-start/) for more information.
-
-```sh
-# For Intel Macs
-[ $(uname -m) = x86_64 ] && curl -Lo ./kind https://kind.sigs.k8s.io/dl/v0.20.0/kind-darwin-amd64
-# For M1 / ARM Macs
-[ $(uname -m) = arm64 ] && curl -Lo ./kind https://kind.sigs.k8s.io/dl/v0.20.0/kind-darwin-arm64
-chmod +x ./kind
-mv ./kind /some-dir-in-your-PATH/kind
-```
-
-### Create the Kind cluster
-
-Create a file called `kind.config`
-
-```yaml
-apiVersion: kind.x-k8s.io/v1alpha4
-kind: Cluster
-nodes:
-- role: control-plane
-  extraPortMappings:
-  - containerPort: 32000
-    hostPort: 32000
-    listenAddress: "0.0.0.0" # Optional, defaults to "0.0.0.0"
-    protocol: tcp # Optional, defaults to tcp
-- role: worker
-```
-
-Then create a cluster using that config
-
-```sh
-kind create cluster --config=kind.config
-```
-
-Set cluster context for kubectl
-
-```sh
-kubectl cluster-info --context kind-kind
-```
-
-Install NGINX Ingress Controller
-
-```sh
-kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/deploy/static/provider/kind/deploy.yaml
-```
-
-## AWX
-
-Set the namespace context
-
-```sh
-kubectl config set-context --current --namespace=awx
-```
-
-Checkout the tag you want to install from
-
-```sh
-git checkout 2.7.2
-```
-
-Create a file named `kustomization.yaml` in the root of your local awx-operator clone. Include the following:
-
-```sh
-apiVersion: kustomize.config.k8s.io/v1beta1
-kind: Kustomization
-resources:
-  # Find the latest tag here: https://github.com/ansible/awx-operator/releases
-  - github.com/ansible/awx-operator/config/default?ref=2.7.2
-
-# Set the image tags to match the git version from above
-images:
-  - name: quay.io/ansible/awx-operator
-    newTag: 2.7.2
-
-# Specify a custom namespace in which to install AWX
-namespace: awx
-```
-
-Run the following to apply the yaml
-
-```sh
-kubectl apply -k .
-```
-
-Create a file called `awx-cr.yaml` with the following contents and any configuration changes you may wish to add.
-
-```yaml
----
-apiVersion: awx.ansible.com/v1beta1
-kind: AWX
-metadata:
-  name: awx-demo
-spec:
-  service_type: nodeport
-  nodeport_port: 32000
-```
-
-Create your AWX CR
-
-```sh
-kubectl create -f awx-cr.yaml
-```
-
-Your AWX instance should now be reachable at <http://localhost:32000/>
-
-!!! note
-    If you configured a custom `nodeport_port`, you can find it by running `kubectl -n awx get svc awx-demo-service`
-
-## Cleanup
-
-When you are done, you can delete all of this by running
-
-```sh
-kind delete cluster
-```

docs/migration.md

@@ -19,8 +19,7 @@ stringData:
 type: Opaque
 ```
 
-!!! note
-    `<resourcename>` must match the `name` of the AWX object you are creating. In our example below, it is `awx`.
+**Note**: `<resourcename>` must match the `name` of the AWX object you are creating. In our example below, it is `awx`.
 
 ### Old Database Credentials
 
@@ -42,14 +41,16 @@ stringData:
 type: Opaque
 ```
 
-!!! note
-    For `host`, a URL resolvable by the cluster could look something like `postgresql.<namespace>.svc.<cluster domain>`, where `<namespace>` is filled in with the namespace of the AWX deployment you are migrating data from, and `<cluster domain>` is filled in with the internal kubernetes cluster domain (In most cases it's `cluster.local`).
+> For `host`, a URL resolvable by the cluster could look something like `postgresql.<namespace>.svc.cluster.local`, where `<namespace>` is filled in with the namespace of the AWX deployment you are migrating data from.
 
-If your AWX deployment is already using an external database server or its database is otherwise not managed by the AWX deployment, you can instead create the same secret as above but omit the `-old-` from the `name`.
-In the next section pass it in through `postgres_configuration_secret` instead, omitting the `_old_` from the key and ensuring the value matches the name of the secret. This will make AWX pick up on the existing database and apply any pending migrations.
-It is strongly recommended to backup your database beforehand.
+If your AWX deployment is already using an external database server or its database is otherwise not managed
+by the AWX deployment, you can instead create the same secret as above but omit the `-old-` from the `name`.
+In the next section pass it in through `postgres_configuration_secret` instead, omitting the `_old_`
+from the key and ensuring the value matches the name of the secret. This will make AWX pick up on the existing
+database and apply any pending migrations. It is strongly recommended to backup your database beforehand.
 
-The postgresql pod for the old deployment is used when streaming data to the new postgresql pod.  If your postgresql pod has a custom label, you can pass that via the `postgres_label_selector` variable to make sure the postgresql pod can be found.
+The postgresql pod for the old deployment is used when streaming data to the new postgresql pod.  If your postgresql pod has a custom label,
+you can pass that via the `postgres_label_selector` variable to make sure the postgresql pod can be found.
 
 ## Deploy AWX
 
@@ -65,16 +66,7 @@ spec:
   secret_key_secret: <resourcename>-secret-key
   ...
 ```
-### Exclude postgreSQL tables during migration (optional)
-
-Use the `pg_dump_suffix` parameter under `AWX.spec` to customize the pg_dump command that will execute during migration. This variable will append your provided pg_dump parameters to the end of the 'standard' command. For example, to exclude the data from 'main_jobevent' and 'main_job' to decrease the size of the backup use:
-
-```
-pg_dump_suffix: "--exclude-table-data 'main_jobevent*' --exclude-table-data 'main_job'"
-```
-
 ## Important Note
-
 If you intend to put all the above in one file, make sure to separate each block with three dashes like so:
 
 ```yaml
@@ -87,5 +79,4 @@ If you intend to put all the above in one file, make sure to separate each block
 ---
 # AWX Config
 ```
-
 Failing to do so will lead to an inoperable setup.

docs/requirements.in

@@ -1,3 +0,0 @@
-# This requirements file is used for AWX Operator latest doc builds.
-
-mkdocs-ansible

docs/requirements.txt

@@ -1,193 +0,0 @@
-#
-# This file is autogenerated by pip-compile with Python 3.12
-# by the following command:
-#
-#    pip-compile --allow-unsafe --output-file=docs/requirements.txt --strip-extras docs/requirements.in
-#
-babel==2.14.0
-    # via mkdocs-material
-beautifulsoup4==4.12.3
-    # via
-    #   linkchecker
-    #   mkdocs-htmlproofer-plugin
-    #   readtime
-cairocffi==1.6.1
-    # via cairosvg
-cairosvg==2.7.0
-    # via mkdocs-ansible
-certifi==2024.2.2
-    # via requests
-cffi==1.16.0
-    # via cairocffi
-charset-normalizer==3.3.2
-    # via requests
-click==8.1.7
-    # via
-    #   mkdocs
-    #   mkdocstrings
-colorama==0.4.6
-    # via
-    #   griffe
-    #   mkdocs-material
-csscompressor==0.9.5
-    # via mkdocs-minify-plugin
-cssselect==1.2.0
-    # via pyquery
-cssselect2==0.7.0
-    # via cairosvg
-defusedxml==0.7.1
-    # via cairosvg
-dnspython==2.6.1
-    # via linkchecker
-ghp-import==2.1.0
-    # via mkdocs
-griffe==0.40.1
-    # via mkdocstrings-python
-htmlmin2==0.1.13
-    # via mkdocs-minify-plugin
-idna==3.6
-    # via requests
-jinja2==3.1.3
-    # via
-    #   mkdocs
-    #   mkdocs-macros-plugin
-    #   mkdocs-material
-    #   mkdocstrings
-jsmin==3.0.1
-    # via mkdocs-minify-plugin
-linkchecker==10.4.0
-    # via mkdocs-ansible
-lxml==5.1.0
-    # via
-    #   mkdocs-material
-    #   pyquery
-markdown==3.5.2
-    # via
-    #   markdown-include
-    #   mkdocs
-    #   mkdocs-autorefs
-    #   mkdocs-htmlproofer-plugin
-    #   mkdocs-material
-    #   mkdocstrings
-    #   pymdown-extensions
-markdown-exec==1.8.0
-    # via mkdocs-ansible
-markdown-include==0.8.1
-    # via mkdocs-ansible
-markdown2==2.4.12
-    # via readtime
-markupsafe==2.1.5
-    # via
-    #   jinja2
-    #   mkdocs
-    #   mkdocstrings
-mergedeep==1.3.4
-    # via mkdocs
-mkdocs==1.5.3
-    # via
-    #   mkdocs-ansible
-    #   mkdocs-autorefs
-    #   mkdocs-gen-files
-    #   mkdocs-htmlproofer-plugin
-    #   mkdocs-macros-plugin
-    #   mkdocs-material
-    #   mkdocs-minify-plugin
-    #   mkdocs-monorepo-plugin
-    #   mkdocstrings
-mkdocs-ansible==24.3.1
-    # via -r requirements.in
-mkdocs-autorefs==0.5.0
-    # via mkdocstrings
-mkdocs-gen-files==0.5.0
-    # via mkdocs-ansible
-mkdocs-htmlproofer-plugin==1.0.0
-    # via mkdocs-ansible
-mkdocs-macros-plugin==1.0.5
-    # via mkdocs-ansible
-mkdocs-material==9.2.6
-    # via mkdocs-ansible
-mkdocs-material-extensions==1.3.1
-    # via
-    #   mkdocs-ansible
-    #   mkdocs-material
-mkdocs-minify-plugin==0.8.0
-    # via mkdocs-ansible
-mkdocs-monorepo-plugin==1.1.0
-    # via mkdocs-ansible
-mkdocstrings==0.24.0
-    # via
-    #   mkdocs-ansible
-    #   mkdocstrings-python
-mkdocstrings-python==1.8.0
-    # via mkdocs-ansible
-packaging==23.2
-    # via mkdocs
-paginate==0.5.6
-    # via mkdocs-material
-pathspec==0.12.1
-    # via mkdocs
-pillow==10.0.1
-    # via
-    #   cairosvg
-    #   mkdocs-ansible
-pipdeptree==2.7.1
-    # via mkdocs-ansible
-platformdirs==4.2.0
-    # via
-    #   mkdocs
-    #   mkdocstrings
-pycparser==2.21
-    # via cffi
-pygments==2.17.2
-    # via mkdocs-material
-pymdown-extensions==10.0.1
-    # via
-    #   markdown-exec
-    #   mkdocs-ansible
-    #   mkdocs-material
-    #   mkdocstrings
-pyquery==2.0.0
-    # via readtime
-python-dateutil==2.8.2
-    # via
-    #   ghp-import
-    #   mkdocs-macros-plugin
-python-slugify==8.0.4
-    # via mkdocs-monorepo-plugin
-pyyaml==6.0.1
-    # via
-    #   mkdocs
-    #   mkdocs-macros-plugin
-    #   pymdown-extensions
-    #   pyyaml-env-tag
-pyyaml-env-tag==0.1
-    # via mkdocs
-readtime==3.0.0
-    # via mkdocs-material
-regex==2023.12.25
-    # via mkdocs-material
-requests==2.31.0
-    # via
-    #   linkchecker
-    #   mkdocs-htmlproofer-plugin
-    #   mkdocs-material
-six==1.16.0
-    # via python-dateutil
-soupsieve==2.5
-    # via beautifulsoup4
-termcolor==2.4.0
-    # via mkdocs-macros-plugin
-text-unidecode==1.3
-    # via python-slugify
-tinycss2==1.2.1
-    # via
-    #   cairosvg
-    #   cssselect2
-urllib3==2.2.1
-    # via requests
-watchdog==4.0.0
-    # via mkdocs
-webencodings==0.5.1
-    # via
-    #   cssselect2
-    #   tinycss2

docs/troubleshooting/debugging.md

@@ -1,132 +0,0 @@
-# Debugging the AWX Operator
-
-## General Debugging
-
-When the operator is deploying AWX, it is running the `installer` role inside the operator container. If the AWX CR's status is `Failed`, it is often useful to look at the awx-operator container logs, which shows the output of the installer role. To see these logs, run:
-
-```sh
-kubectl logs deployments/awx-operator-controller-manager -c awx-manager -f
-```
-
-### Inspect k8s Resources
-
-Past that, it is often useful to inspect various resources the AWX Operator manages like:
-
-* awx
-* awxbackup
-* awxrestore
-* pod
-* deployment
-* pvc
-* service
-* ingress
-* route
-* secrets
-* serviceaccount
-
-And if installing via OperatorHub and OLM:
-
-* subscription
-* csv
-* installPlan
-* catalogSource
-
-To inspect these resources you can use these commands
-
-```sh
-# Inspecting k8s resources
-kubectl describe -n <namespace> <resource> <resource-name>
-kubectl get -n <namespace> <resource> <resource-name> -o yaml
-kubectl logs -n <namespace> <resource> <resource-name>
-
-# Inspecting Pods
-kubectl exec -it -n <namespace> <pod> <pod-name>
-```
-
-### Configure No Log
-
-It is possible to show task output for debugging by setting no_log to false on the AWX CR spec.
-This will show output in the awx-operator logs for any failed tasks where no_log was set to true.
-
-For example:
-
-```sh
----
-apiVersion: awx.ansible.com/v1beta1
-kind: AWX
-metadata:
-  name: awx-demo
-spec:
-  service_type: nodeport
-  no_log: false                  # <------------
-
-```
-
-## Iterating on the installer without deploying the operator
-
-Go through the [normal basic install](../installation/basic-install.md) steps.
-
-Install some dependencies:
-
-```sh
-ansible-galaxy collection install -r molecule/requirements.yml
-pip install -r molecule/requirements.txt
-```
-
-To prevent the changes we're about to make from being overwritten, scale down any running instance of the operator:
-
-```sh
-kubectl scale deployment awx-operator-controller-manager --replicas=0
-```
-
-Create a playbook that invokes the installer role (the operator uses ansible-runner's role execution feature):
-
-```yaml
-# run.yml
----
-- hosts: localhost
-  roles:
-    - installer
-```
-
-Create a vars file:
-
-```yaml
-# vars.yml
----
-ansible_operator_meta:
-  name: awx
-  namespace: awx
-set_self_labels: false
-update_status: false
-service_type: nodeport
-```
-
-The vars file will replace the awx resource so any value that you wish to over ride using the awx resource, put in the vars file. For example, if you wish to use your own image, version and pull policy, you can specify it like below:
-
-```yaml
-# vars.yml
----
-ansible_operator_meta:
-  name: awx
-  namespace: awx
-set_self_labels: false
-update_status: false
-service_type: nodeport
-image: $DEV_DOCKER_TAG_BASE/awx_kube_devel
-image_pull_policy: Always
-image_version: $COMPOSE_TAG
-```
-
-Run the installer:
-
-```sh
-ansible-playbook run.yml -e @vars.yml -v
-```
-
-Grab the URL and admin password:
-
-```sh
-$ kubectl get secret awx-admin-password -- -o jsonpath="{.data.password}" | base64 --decode ; echo
-LU6lTfvnkjUvDwL240kXKy1sNhjakZmT
-```

docs/uninstall/uninstall.md

@@ -1,13 +0,0 @@
-# Uninstall
-
-To uninstall an AWX deployment instance, you basically need to remove the AWX kind related to that instance. For example, to delete an AWX instance named awx-demo, you would do:
-
-```sh
-$ kubectl delete awx awx-demo
-awx.awx.ansible.com "awx-demo" deleted
-```
-
-Deleting an AWX instance will remove all related deployments and statefulsets, however, persistent volumes and secrets will remain. To enforce secrets also getting removed, you can use `garbage_collect_secrets: true`.
-
-!!! note
-    If you ever intend to recover an AWX from an existing database you will need a copy of the secrets in order to perform a successful recovery.

docs/upgrade/upgrading.md

@@ -1,56 +0,0 @@
-# Upgrading
-
-To upgrade AWX, it is recommended to upgrade the awx-operator to the version that maps to the desired version of AWX. To find the version of AWX that will be installed by the awx-operator by default, check the version specified in the `DEFAULT_AWX_VERSION` variable for that particular release. You can do so by running the following command
-
-```shell
-AWX_OPERATOR_VERSION=2.8.0
-docker run --entrypoint="" quay.io/ansible/awx-operator:$AWX_OPERATOR_VERSION bash -c "env | grep DEFAULT_AWX_VERSION"
-```
-
-Make sure you have a backup before upgrading, then upgrade operator by invoking `make deploy` on the desired tag or by applying the `kustomization.yaml` that contains desired version of the operator, and in turn also upgrade your AWX deployment.
-
-## Backup
-
-The first part of any upgrade should be a backup. Note, there are secrets in the pod which work in conjunction with the database. Having just a database backup without the required secrets will not be sufficient for recovering from an issue when upgrading to a new version. See the [backup role documentation](https://github.com/ansible/awx-operator/tree/devel/roles/backup) for information on how to backup your database and secrets.
-
-In the event you need to recover the backup see the [restore role documentation](https://github.com/ansible/awx-operator/tree/devel/roles/restore). _Before Restoring from a backup_, be sure to:
-
-- delete the old existing AWX CR
-- delete the persistent volume claim (PVC) for the database from the old deployment, which has a name like `postgres-15-<deployment-name>-postgres-15-0`
-
-**Note**: Do not delete the namespace/project, as that will delete the backup and the backup's PVC as well.
-
-## PostgreSQL Upgrade Considerations
-
-If there is a PostgreSQL major version upgrade, after the data directory on the PVC is migrated to the new version, the old PVC is kept by default.
-This provides the ability to roll back if needed, but can take up extra storage space in your cluster unnecessarily. You can configure it to be deleted automatically after a successful upgrade by setting the following variable on the AWX spec.
-
-```yaml
-spec:
-  postgres_keep_pvc_after_upgrade: False
-```
-
-## Caveats for upgrading to v0.14.0
-
-### Cluster-scope to Namespace-scope considerations
-
-Starting with awx-operator 0.14.0, AWX can only be deployed in the namespace that the operator exists in. This is called a namespace-scoped operator. If you are upgrading from an earlier version, you will want to delete your existing `awx-operator` service account, role and role binding.
-
-### Project is now based on v1.x of the operator-sdk project
-
-Starting with awx-operator 0.14.0, the project is now based on operator-sdk 1.x. You may need to manually delete your old operator Deployment to avoid issues.
-
-### Steps to upgrade to v0.14.0
-
-Delete your old AWX Operator and existing `awx-operator` service account, role and role binding in `default` namespace first:
-
-```sh
-kubectl -n default delete deployment awx-operator
-kubectl -n default delete serviceaccount awx-operator
-kubectl -n default delete clusterrolebinding awx-operator
-kubectl -n default delete clusterrole awx-operator
-```
-
-Then install the new AWX Operator by following the instructions in [Basic Install](../installation/basic-install.md). The `NAMESPACE` environment variable have to be the name of the namespace in which your old AWX instance resides.
-
-Once the new AWX Operator is up and running, your AWX deployment will also be upgraded.

docs/user-guide/admin-user-account-configuration.md

@@ -1,64 +0,0 @@
-# Admin user account configuration
-
-There are three variables that are customizable for the admin user account creation.
-
-| Name                  | Description                                  | Default            |
-| --------------------- | -------------------------------------------- | ------------------ |
-| admin_user            | Name of the admin user                       | `admin`            |
-| admin_email           | Email of the admin user                      | `test@example.com` |
-| admin_password_secret | Secret that contains the admin user password | Empty string       |
-
-!!! warning
-    `admin_password_secret` must be a Kubernetes secret and not your text clear password.
-
-If `admin_password_secret` is not provided, the operator will look for a secret named `<resourcename>-admin-password` for the admin password. If it is not present, the operator will generate a password and create a Secret from it named `<resourcename>-admin-password`.
-
-To retrieve the admin password, run `kubectl get secret <resourcename>-admin-password -o jsonpath="{.data.password}" | base64 --decode ; echo`
-
-The secret that is expected to be passed should be formatted as follow:
-
-```yaml
----
-apiVersion: v1
-kind: Secret
-metadata:
-  name: <resourcename>-admin-password
-  namespace: <target namespace>
-stringData:
-  password: mysuperlongpassword
-```
-
-## Secret Key Configuration
-
-This key is used to encrypt sensitive data in the database.
-
-| Name              | Description                                           | Default          |
-| ----------------- | ----------------------------------------------------- | ---------------- |
-| secret_key_secret | Secret that contains the symmetric key for encryption | Generated        |
-
-!!! warning
-    `secret_key_secret` must be a Kubernetes secret and not your text clear secret value.
-
-If `secret_key_secret` is not provided, the operator will look for a secret named `<resourcename>-secret-key` for the secret key. If it is not present, the operator will generate a password and create a Secret from it named `<resourcename>-secret-key`. It is important to not delete this secret as it will be needed for upgrades and if the pods get scaled down at any point. If you are using a GitOps flow, you will want to pass a secret key secret.
-
-The secret should be formatted as follow:
-
-```yaml
----
-apiVersion: v1
-kind: Secret
-metadata:
-  name: custom-awx-secret-key
-  namespace: <target namespace>
-stringData:
-  secret_key: supersecuresecretkey
-```
-
-Then specify the secret name on the AWX spec:
-
-```yaml
----
-spec:
-  ...
-  secret_key_secret: custom-awx-secret-key
-```

docs/user-guide/advanced-configuration/assigning-awx-pods-to-specific-nodes.md

@@ -1,95 +0,0 @@
-# Assigning AWX pods to specific nodes
-
-You can constrain the AWX pods created by the operator to run on a certain subset of nodes. `node_selector` and `postgres_selector` constrains
-the AWX pods to run only on the nodes that match all the specified key/value pairs. `tolerations` and `postgres_tolerations` allow the AWX
-pods to be scheduled onto nodes with matching taints.
-The ability to specify topologySpreadConstraints is also allowed through `topology_spread_constraints`
-If you want to use affinity rules for your AWX pod you can use the `affinity` option.
-
-If you want to constrain the web and task pods individually, you can do so by specifying the deployment type before the specific setting. For
-example, specifying `task_tolerations` will allow the AWX task pod to be scheduled onto nodes with matching taints.
-
-| Name                             | Description                              | Default                          |
-| -------------------------------- | ---------------------------------------- | -------------------------------- |
-| postgres_image                   | Path of the image to pull                | quay.io/sclorg/postgresql-15-c9s |
-| postgres_image_version           | Image version to pull                    | latest                           |
-| node_selector                    | AWX pods' nodeSelector                   | ''                               |
-| web_node_selector                | AWX web pods' nodeSelector               | ''                               |
-| task_node_selector               | AWX task pods' nodeSelector              | ''                               |
-| topology_spread_constraints      | AWX pods' topologySpreadConstraints      | ''                               |
-| web_topology_spread_constraints  | AWX web pods' topologySpreadConstraints  | ''                               |
-| task_topology_spread_constraints | AWX task pods' topologySpreadConstraints | ''                               |
-| affinity                         | AWX pods' affinity rules                 | ''                               |
-| web_affinity                     | AWX web pods' affinity rules             | ''                               |
-| task_affinity                    | AWX task pods' affinity rules            | ''                               |
-| tolerations                      | AWX pods' tolerations                    | ''                               |
-| web_tolerations                  | AWX web pods' tolerations                | ''                               |
-| task_tolerations                 | AWX task pods' tolerations               | ''                               |
-| annotations                      | AWX pods' annotations                    | ''                               |
-| postgres_selector                | Postgres pods' nodeSelector              | ''                               |
-| postgres_tolerations             | Postgres pods' tolerations               | ''                               |
-
-Example of customization could be:
-
-```yaml
----
-spec:
-  ...
-  node_selector: |
-    disktype: ssd
-    kubernetes.io/arch: amd64
-    kubernetes.io/os: linux
-  topology_spread_constraints: |
-    - maxSkew: 100
-      topologyKey: "topology.kubernetes.io/zone"
-      whenUnsatisfiable: "ScheduleAnyway"
-      labelSelector:
-        matchLabels:
-          app.kubernetes.io/name: "<resourcename>"
-  tolerations: |
-    - key: "dedicated"
-      operator: "Equal"
-      value: "AWX"
-      effect: "NoSchedule"
-  task_tolerations: |
-    - key: "dedicated"
-      operator: "Equal"
-      value: "AWX_task"
-      effect: "NoSchedule"
-  postgres_selector: |
-    disktype: ssd
-    kubernetes.io/arch: amd64
-    kubernetes.io/os: linux
-  postgres_tolerations: |
-    - key: "dedicated"
-      operator: "Equal"
-      value: "AWX"
-      effect: "NoSchedule"
-  affinity:
-    nodeAffinity:
-      preferredDuringSchedulingIgnoredDuringExecution:
-      - weight: 1
-        preference:
-          matchExpressions:
-          - key: another-node-label-key
-            operator: In
-            values:
-            - another-node-label-value
-            - another-node-label-value
-    podAntiAffinity:
-      preferredDuringSchedulingIgnoredDuringExecution:
-      - weight: 100
-        podAffinityTerm:
-          labelSelector:
-            matchExpressions:
-            - key: security
-              operator: In
-              values:
-              - S2
-          topologyKey: topology.kubernetes.io/zone
-```
-
-## Special Note on DB-Migration Job Scheduling
-
-For the **db-migration job**, which applies database migrations at cluster startup, you can specify scheduling settings using the `task_*` configurations such as `task_node_selector`, `task_tolerations`, etc.  
-If these task-specific settings are not defined, the job will automatically use the global AWX configurations like `node_selector` and `tolerations`.

docs/user-guide/advanced-configuration/auto-upgrade.md

@@ -1,37 +0,0 @@
-# Auto upgrade
-
-With this parameter you can influence the behavior during an operator upgrade.  
-If set to `true`, the operator will upgrade the specific instance directly.  
-When the value is set to `false`, and we have a running deployment, the operator will not update the AWX instance.  
-This can be useful when you have multiple AWX instances which you want to upgrade step by step instead of all at once.  
-
-| Name         | Description                        | Default |
-| -------------| ---------------------------------- | ------- |
-| auto_upgrade | Automatic upgrade of AWX instances | true    |
-
-Example configuration of `auto_upgrade` parameter
-
-```yaml
-spec:
-  auto_upgrade: true
-```
-
-## Upgrade of instances without auto upgrade
-
-There are two ways to upgrade instances which are marked with the 'auto_upgrade: false' flag.  
-
-Changing flags:
-
-- change the auto_upgrade flag on your AWX object to true  
-- wait until the upgrade process of that instance is finished
-- change the auto_upgrade flag on your AWX object back to false  
-
-Delete the deployment:
-
-- delete the deployment object of your AWX instance
-
-    ```sh
-    kubectl -n awx delete deployment <yourInstanceName> 
-    ```
-
-- wait until the instance gets redeployed

docs/user-guide/advanced-configuration/container-probes.md

@@ -1,53 +0,0 @@
-# Container Probes
-
-These parameters control the usage of liveness and readiness container probes for
-the web and task containers.
-
-!!! tip
-    All of probes are disabled by default for now, to enable it, set the `*_period` parameters. For example:
-
-    ```yaml
-    spec:
-      web_liveness_period: 15
-      web_readiness_period: 15
-      task_liveness_period: 15
-      task_readiness_period: 15
-    ```
-
-## Web / Task Container Liveness Check
-
-The liveness probe queries the status of the supervisor daemon of the container.  The probe will fail if it
-detects one of the services in a state other than "RUNNING".
-
-| Name         | Description                        | Default |
-| -------------| -----------------------------------|---------|
-| web_liveness_period | Time period in seconds between each probe check.  The value of 0 disables the probe. | 0    |
-| web_liveness_initial_delay | Initial delay before starting probes in seconds | 5   |
-| web_liveness_failure_threshold| Number of consecutive failure events to identify failure of container | 3    |
-| web_liveness_timeout | Number of seconds to wait for a probe response from container | 1    |
-| task_liveness_period | Time period in seconds between each probe check.  The value of 0 disables the probe. | 0    |
-| task_liveness_initial_delay | Initial delay before starting probes in seconds | 5   |
-| task_liveness_failure_threshold| Number of consecutive failure events to identify failure of container | 3    |
-| task_liveness_timeout | Number of seconds to wait for a probe response from container | 1    |
-
-## Web Container Readiness Check
-
-This is an HTTP check against the status endpoint to confirm the system is still able to respond to web requests.
-
-| Name         | Description                        | Default |
-| -------------| ---------------------------------- | ------- |
-| web_readiness_period | Time period in seconds between each probe check.  The value of 0 disables the probe. | 0    |
-| web_readiness_initial_delay | Initial delay before starting probes in seconds | 5   |
-| web_readiness_failure_threshold| Number of consecutive failure events to identify failure of container | 3    |
-| web_readiness_timeout | Number of seconds to wait for a probe response from container | 1    |
-
-## Task Container Readiness Check
-
-This is a command probe using the builtin check command of the awx-manage utility.
-
-| Name         | Description                        | Default |
-| -------------| ---------------------------------- | ------- |
-| task_readiness_period | Time period in seconds between each probe check.  The value of 0 disables the probe. | 0    |
-| task_readiness_initial_delay | Initial delay before starting probes in seconds | 5   |
-| task_readiness_failure_threshold| Number of consecutive failure events to identify failure of container | 3    |
-| task_readiness_timeout | Number of seconds to wait for a probe response from container | 1    |

docs/user-guide/advanced-configuration/containers-resource-requirements.md

@@ -1,72 +0,0 @@
-# Containers Resource Requirements
-
-The resource requirements for both, the task and the web containers are configurable - both the lower end (requests) and the upper end (limits).
-
-| Name                                 | Description                                                  | Default                              |
-| ------------------------------------ | ------------------------------------------------------------ | ------------------------------------ |
-| web_resource_requirements            | Web container resource requirements                          | requests: {cpu: 100m, memory: 128Mi} |
-| task_resource_requirements           | Task container resource requirements                         | requests: {cpu: 100m, memory: 128Mi} |
-| ee_resource_requirements             | EE control plane container resource requirements             | requests: {cpu: 50m, memory: 64Mi}   |
-| redis_resource_requirements          | Redis container resource requirements                        | requests: {cpu: 100m, memory: 128Mi} |
-| postgres_resource_requirements       | Postgres container (and initContainer) resource requirements | requests: {cpu: 10m, memory: 64Mi}   |
-| rsyslog_resource_requirements        | Rsyslog container resource requirements                      | requests: {cpu: 100m, memory: 128Mi} |
-| init_container_resource_requirements | Init Container resource requirements                         | requests: {cpu: 100m, memory: 128Mi} |
-
-Example of customization could be:
-
-```yaml
----
-spec:
-  ...
-
-  task_resource_requirements:
-    requests:
-      cpu: 100m
-      memory: 128Mi
-      ephemeral-storage: 100M
-    limits:
-      cpu: 2000m
-      memory: 4Gi
-      ephemeral-storage: 500M
-  web_resource_requirements:
-    requests:
-      cpu: 100m
-      memory: 128Mi
-    limits:
-      cpu: 1000m
-      memory: 4Gi
-  ee_resource_requirements:
-    requests:
-      cpu: 100m
-      memory: 64Mi
-    limits:
-      cpu: 1000m
-      memory: 4Gi
-  redis_resource_requirements:
-    requests:
-      cpu: 50m
-      memory: 64Mi
-    limits:
-      cpu: 1000m
-      memory: 4Gi
-  rsyslog_resource_requirements:
-    requests:
-      cpu: 100m
-      memory: 128Mi
-    limits:
-      cpu: 1000m
-      memory: 2Gi
-  init_container_resource_requirements:
-    requests:
-      cpu: 100m
-      memory: 128Mi
-    limits:
-      cpu: 1000m
-      memory: 2Gi
-```
-
-## Limits and ResourceQuotas
-
-If the cluster you are deploying in has a ResoruceQuota, you will need to configure resource limits for all of the pods deployed in that cluster. This can be done for AWX pods on the AWX spec in the manner shown above.
-
-There is an example you can use in [`awx_v1beta1_awx_resource_limits.yaml`](https://raw.githubusercontent.com/ansible/awx-operator/devel/config/samples/awx_v1beta1_awx_resource_limits.yaml).

docs/user-guide/advanced-configuration/csrf-cookie-secure-setting.md

@@ -1,14 +0,0 @@
-# CSRF Cookie Secure Setting
-
-With `csrf_cookie_secure`, you can pass the value for `CSRF_COOKIE_SECURE` to `/etc/tower/settings.py`
-
-| Name               | Description        | Default |
-| ------------------ | ------------------ | ------- |
-| csrf_cookie_secure | CSRF Cookie Secure | ''      |
-
-Example configuration of the `csrf_cookie_secure` setting:
-
-```yaml
-spec:
-  csrf_cookie_secure: 'False'
-```

docs/user-guide/advanced-configuration/custom-receptor-certs.md

@@ -1,24 +0,0 @@
-# Custom Receptor CA
-
-The control nodes on the K8S cluster will communicate with execution nodes via mutual TLS TCP connections, running via Receptor.
-Execution nodes will verify incoming connections by ensuring the x509 certificate was issued by a trusted Certificate Authority (CA).
-
-A user may wish to provide their own CA for this validation. If no CA is provided, AWX Operator will automatically generate one using OpenSSL.
-
-Given custom `ca.crt` and `ca.key` stored locally, run the following,
-
-```bash
-kubectl create secret tls awx-demo-receptor-ca \
-   --cert=/path/to/ca.crt --key=/path/to/ca.key
-```
-
-The secret should be named `{AWX Custom Resource name}-receptor-ca`. In the above the AWX CR name is "awx-demo". Please replace "awx-demo" with your AWX Custom Resource name.
-
-If this secret is created after AWX is deployed, run the following to restart the deployment,
-
-```bash
-kubectl rollout restart deployment awx-demo
-```
-
-!!! warning
-    Changing the receptor CA will break connections to any existing execution nodes. These nodes will enter an `unavailable` state, and jobs will not be able to run on them. Users will need to download and re-run the install bundle for each execution node. This will replace the TLS certificate files with those signed by the new CA. The execution nodes should then appear in a `ready` state after a few minutes.

docs/user-guide/advanced-configuration/custom-volume-and-volume-mount-options.md

@@ -1,200 +0,0 @@
-# Custom Volume and Volume Mount Options
-
-In a scenario where custom volumes and volume mounts are required to either overwrite defaults or mount configuration files.
-
-| Name                               | Description                                              | Default |
-| ---------------------------------- | -------------------------------------------------------- | ------- |
-| extra_volumes                      | Specify extra volumes to add to the application pod      | ''      |
-| web_extra_volume_mounts            | Specify volume mounts to be added to Web container       | ''      |
-| task_extra_volume_mounts           | Specify volume mounts to be added to Task container      | ''      |
-| rsyslog_extra_volume_mounts        | Specify volume mounts to be added to Rsyslog container   | ''      |
-| ee_extra_volume_mounts             | Specify volume mounts to be added to Execution container | ''      |
-| init_container_extra_volume_mounts | Specify volume mounts to be added to Init container      | ''      |
-| init_container_extra_commands      | Specify additional commands for Init container           | ''      |
-
-!!! warning
-    The `ee_extra_volume_mounts` and `extra_volumes` will only take effect to the globally available Execution Environments. For custom `ee`, please [customize the Pod spec](https://docs.ansible.com/ansible-tower/latest/html/administration/external_execution_envs.html#customize-the-pod-spec).
-
-Example configuration for ConfigMap
-
-```yaml
----
-apiVersion: v1
-kind: ConfigMap
-metadata:
-  name: <resourcename>-extra-config
-  namespace: <target namespace>
-data:
-  ansible.cfg: |
-    [defaults]
-    remote_tmp = /tmp
-    [ssh_connection]
-    ssh_args = -C -o ControlMaster=auto -o ControlPersist=60s
-```
-
-Example spec file for volumes and volume mounts
-
-```yaml
----
-spec:
-  ...
-  extra_volumes: |
-    - name: ansible-cfg
-      configMap:
-        defaultMode: 420
-        items:
-          - key: ansible.cfg
-            path: ansible.cfg
-        name: <resourcename>-extra-config
-    - name: shared-volume
-      persistentVolumeClaim:
-        claimName: my-external-volume-claim
-
-  init_container_extra_volume_mounts: |
-    - name: shared-volume
-      mountPath: /shared
-
-  init_container_extra_commands: |
-    # set proper permissions (rwx) for the awx user
-    chmod 775 /shared
-    chgrp 1000 /shared
-
-  ee_extra_volume_mounts: |
-    - name: ansible-cfg
-      mountPath: /etc/ansible/ansible.cfg
-      subPath: ansible.cfg
-```
-
-!!! warning
-    **Volume and VolumeMount names cannot contain underscores(_)**
-
-## Custom UWSGI Configuration
-
-We allow the customization of three UWSGI parameters:
-
-* [processes](https://uwsgi-docs.readthedocs.io/en/latest/Options.html#processes) with `uwsgi_processes` (default 5)
-* [listen](https://uwsgi-docs.readthedocs.io/en/latest/Options.html#listen) with `uwsgi_listen_queue_size` (default 128)
-* [harakiri](https://uwsgi-docs.readthedocs.io/en/latest/Options.html#harakiri) with `uwsgi_timeout` (default 30)
-
-**Note:** Increasing the listen queue beyond 128 requires that the sysctl setting net.core.somaxconn be set to an equal value or higher.
-  The operator will set the appropriate securityContext sysctl value for you, but it is a required that this sysctl be added to an allowlist on the kubelet level. [See kubernetes docs about allowing this sysctl setting](https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/#enabling-unsafe-sysctls).
-
-The `processes` and `listen` vars relate to the vertical and horizontal scalibility of the web service.
-
-Increasing the number of processes allows more requests to be actively handled
-per web pod, but will consume more CPU and Memory and the resource requests
-should be increased in tandem.  Increasing the listen queue allows uwsgi to
-queue up requests not yet being handled by the active worker processes, which
-may allow the web pods to handle more "bursty" request patterns if many
-requests (more than 128) tend to come in a short period of time, but can all be
-handled before any other time outs may apply. Also see related nginx
-configuration.
-
-The `uwsgi_timeout` variable determines after how many seconds a request will
-be forecibly killed by uwsgi. A "graceful" timeout signal is sent to the worker
-2 seconds prior to attempt to get a traceback of what may be causing the
-request to hang.
-
-
-## Custom Nginx Configuration
-
-Using the [extra_volumes feature](#custom-volume-and-volume-mount-options), it is possible to extend the nginx.conf.
-
-1. Create a ConfigMap with the extra settings you want to include in the nginx.conf
-2. Create an extra_volumes entry in the AWX spec for this ConfigMap
-3. Create an web_extra_volume_mounts entry in the AWX spec to mount this volume
-
-The AWX nginx config automatically includes /etc/nginx/conf.d/*.conf if present.
-
-Additionally there are some global configuration values in the base nginx
-config that are available for setting with individual variables.
-These vars relate to the vertical and horizontal scalibility of the web service.
-Increasing the number of processes allows more requests to be actively handled
-per web pod, but will consume more CPU and Memory and the resource requests
-should be increased in tandem.  Increasing the listen queue allows nginx to
-queue up requests not yet being handled by the active worker processes, which
-may allow the web pods to handle more "bursty" request patterns if many
-requests (more than 128) tend to come in a short period of time, but can all be
-handled before any other time outs may apply. Also see related uwsgi
-configuration.
-
-* [worker_processes](http://nginx.org/en/docs/ngx_core_module.html#worker_processes) with `nginx_worker_processes` (default of 1)
-* [worker_cpu_affinity](http://nginx.org/en/docs/ngx_core_module.html#worker_cpu_affinity) with `nginx_worker_cpu_affinity` (default "auto")
-* [worker_connections](http://nginx.org/en/docs/ngx_core_module.html#worker_connections) with `nginx_worker_connections` (minimum of 1024)
-* [listen](https://nginx.org/en/docs/http/ngx_http_core_module.html#listen) with `nginx_listen_queue_size` (default same as uwsgi listen queue size)
-
-## Custom Logos
-
-You can use custom volume mounts to mount in your own logos to be displayed instead of the AWX logo.
-There are two different logos, one to be displayed on page headers, and one for the login screen.
-
-First, create configmaps for the logos from local `logo-login.svg` and `logo-header.svg` files.
-
-```bash
-kubectl create configmap logo-login-configmap --from-file logo-login.svg
-kubectl create configmap logo-header-configmap --from-file logo-header.svg
-```
-
-Then specify the extra_volume and web_extra_volume_mounts on your AWX CR spec
-
-```yaml
----
-spec:
-  ...
-  extra_volumes: |
-    - name: logo-login
-      configMap:
-        defaultMode: 420
-        items:
-          - key: logo-login.svg
-            path: logo-login.svg
-        name: logo-login-configmap
-    - name: logo-header
-      configMap:
-        defaultMode: 420
-        items:
-          - key: logo-header.svg
-            path: logo-header.svg
-        name: logo-header-configmap
-  web_extra_volume_mounts: |
-    - name: logo-login
-      mountPath: /var/lib/awx/public/static/media/logo-login.svg
-      subPath: logo-login.svg
-    - name: logo-header
-      mountPath: /var/lib/awx/public/static/media/logo-header.svg
-      subPath: logo-header.svg
-```
-
-## Custom Favicon
-
-You can also use custom volume mounts to mount in your own favicon to be displayed in your AWX browser tab.
-
-First, create the configmap from a local `favicon.ico` file.
-
-```bash
-kubectl create configmap favicon-configmap --from-file favicon.ico
-```
-
-Then specify the extra_volume and web_extra_volume_mounts on your AWX CR spec
-
-```yaml
----
-spec:
-  ...
-  extra_volumes: |
-    - name: favicon
-      configMap:
-        defaultMode: 420
-        items:
-          - key: favicon.ico
-            path: favicon.ico
-        name: favicon-configmap
-  web_extra_volume_mounts: |
-    - name: favicon
-      mountPath: /var/lib/awx/public/static/media/favicon.ico
-      subPath: favicon.ico
-```
-
-## Custom AWX Configuration
-
-Refer to the [Extra Settings](./extra-settings.md) documentation for customizing the AWX configuration.

docs/user-guide/advanced-configuration/deploying-a-specific-version-of-awx.md

@@ -1,90 +0,0 @@
-# Using images from private registries
-
-## Available variables to use images from private registries
-
-There are variables that are customizable for awx the image management.
-
-| Name                          | Description                   | Default                                    |
-| ----------------------------- | ----------------------------- | ------------------------------------------ |
-| image                         | Path of the image to pull     | quay.io/ansible/awx                        |
-| image_version                 | Image version to pull         | value of DEFAULT_AWX_VERSION or latest     |
-| image_pull_policy             | The pull policy to adopt      | IfNotPresent                               |
-| image_pull_secrets            | The pull secrets to use       | None                                       |
-| ee_images                     | A list of EEs to register     | quay.io/ansible/awx-ee:DEFAULT_AWX_VERSION |
-| ee_pull_credentials_secret    | The pull secret for ee_images | None                                       |
-| redis_image                   | Path of the image to pull     | docker.io/redis                            |
-| redis_image_version           | Image version to pull         | latest                                     |
-| control_plane_ee_image        | Image version to pull         | quay.io/ansible/awx-ee:DEFAULT_AWX_VERSION |
-| init_container_image          | Path of the image to pull     | quay.io/ansible/awx-ee                     |
-| init_container_image_version  | Image version to pull         | value of DEFAULT_AWX_VERSION or latest     |
-| init_projects_container_image | Image version to pull         | quay.io/centos/centos:stream9              |
-
-Example of customization could be:
-
-```yaml
----
-spec:
-  ...
-  image: myorg/my-custom-awx
-  image_version: latest
-  image_pull_policy: Always
-  image_pull_secrets:
-    - pull_secret_name
-  ee_images:
-    - name: my-custom-awx-ee
-      image: myorg/my-custom-awx-ee
-  control_plane_ee_image: myorg/my-custom-awx-ee:latest
-  init_container_image: myorg/my-custom-awx-ee
-  init_container_image_version: latest
-  init_projects_container_image: myorg/my-mirrored-centos:stream9
-```
-
-!!! warning
-    The `image` and `image_version` are intended for local mirroring scenarios. Please note that using a version of AWX other than the one bundled with the `awx-operator` is **not** supported. For the default values, check the [main.yml](https://github.com/ansible/awx-operator/blob/devel/roles/installer/defaults/main.yml) file.
-
-## Default execution environments from private registries
-
-In order to register default execution environments from private registries, the Custom Resource needs to know about the pull credentials. Those credentials should be stored as a secret and either specified as `ee_pull_credentials_secret` at the CR spec level, or simply be present on the namespace under the name `<resourcename>-ee-pull-credentials` . Instance initialization will register a `Container registry` type credential on the deployed instance and assign it to the registered default execution environments.
-
-The secret should be formatted as follows:
-
-```yaml
----
-apiVersion: v1
-kind: Secret
-metadata:
-  name: <resourcename>-ee-pull-credentials
-  namespace: <target namespace>
-stringData:
-  url: <registry url. i.e. quay.io>
-  username: <username to connect as>
-  password: <password to connect with>
-  ssl_verify: <Optional attribute. Whether verify ssl connection or not. Accepted values "True" (default), "False" >
-type: Opaque
-```
-
-## Control plane ee from private registry
-
-The images listed in `ee_images` will be added as globally available Execution Environments. The `control_plane_ee_image` will be used to run project updates. In order to use a private image for any of these you'll need to use `image_pull_secrets` to provide a list of k8s pull secrets to access it. Currently the same secret is used for any of these images supplied at install time.
-
-You can create `image_pull_secret`
-
-```sh
-kubectl create secret <resoucename>-cp-pull-credentials regcred --docker-server=<your-registry-server> --docker-username=<your-name> --docker-password=<your-pword> --docker-email=<your-email>
-```
-
-If you need more control (for example, to set a namespace or a label on the new secret) then you can customize the Secret before storing it
-
-Example spec file extra-config
-
-```yaml
----
-apiVersion: v1
-kind: Secret
-metadata:
-  name: <resoucename>-cp-pull-credentials
-  namespace: <target namespace>
-data:
-  .dockerconfigjson: <base64 docker config>
-type: kubernetes.io/dockerconfigjson
-```

docs/user-guide/advanced-configuration/disable-ipv6.md

@@ -1,19 +0,0 @@
-# Disable IPv6
-
-Starting with AWX Operator release 0.24.0, [IPv6 was enabled in ngnix configuration](https://github.com/ansible/awx-operator/pull/950) which causes
-upgrades and installs to fail in environments where IPv6 is not allowed. Starting in 1.1.1 release, you can set the `ipv6_disabled` flag on the AWX
-spec. If you need to use an AWX operator version between 0.24.0 and 1.1.1 in an IPv6 disabled environment, it is suggested to enabled ipv6 on worker
-nodes.
-
-In order to disable ipv6 on ngnix configuration (awx-web container), add following to the AWX spec.
-
-The following variables are customizable:
-
-| Name          | Description            | Default |
-| ------------- | ---------------------- | ------- |
-| ipv6_disabled | Flag to disable ipv6   | false   |
-
-```yaml
-spec:
-  ipv6_disabled: true
-```

docs/user-guide/advanced-configuration/enabling-ldap-integration-at-awx-bootstrap.md

@@ -1,143 +0,0 @@
-# Enabling LDAP Integration at AWX bootstrap (Deprecated)
-
-A sample of extra settings can be found as below. All possible options can be found here: <https://django-auth-ldap.readthedocs.io/en/latest/reference.html#settings>
-
-Refer to the [Extra Settings](./extra-settings.md) page for more information on how to configure extra settings.
-
-!!! tip
-    To trust a custom Certificate Authority for your LDAP server, or to specify password LDAP bind DN, refer to the [Trusting a Custom Certificate Authority](./trusting-a-custom-certificate-authority.md) page.
-
-## Configure LDAP integration via `extra_settings_files`
-
-Create a Python file with arbitrary name, e.g. `custom_ldap_settings.py`, and add the following content for example:
-
-```python title="custom_ldap_settings.py"
-AUTH_LDAP_SERVER_URI = "ldaps://ad01.abc.com:636 ldaps://ad02.abc.com:636"
-AUTH_LDAP_BIND_DN = "CN=LDAP User,OU=Service Accounts,DC=abc,DC=com"
-AUTH_LDAP_USER_SEARCH = LDAPSearch(
-    "DC=abc,DC=com",
-    ldap.SCOPE_SUBTREE,
-    "(sAMAccountName=%(user)s)",
-)
-AUTH_LDAP_GROUP_SEARCH = LDAPSearch(
-    "OU=Groups,DC=abc,DC=com",
-    ldap.SCOPE_SUBTREE,
-    "(objectClass=group)",
-)
-AUTH_LDAP_GROUP_TYPE = GroupOfNamesType()
-AUTH_LDAP_USER_ATTR_MAP = {
-    "first_name": "givenName",
-    "last_name": "sn",
-    "email": "mail",
-}
-AUTH_LDAP_REQUIRE_GROUP = "CN=operators,OU=Groups,DC=abc,DC=com"
-AUTH_LDAP_USER_FLAGS_BY_GROUP = {
-    "is_superuser": ["CN=admin,OU=Groups,DC=abc,DC=com"],
-}
-AUTH_LDAP_ORGANIZATION_MAP = {
-    "abc": {
-        "admins": "CN=admin,OU=Groups,DC=abc,DC=com",
-        "remove_admins": False,
-        "remove_users": False,
-        "users": True,
-    }
-}
-AUTH_LDAP_TEAM_MAP = {
-    "admin": {
-        "organization": "abc",
-        "remove": True,
-        "users": "CN=admin,OU=Groups,DC=abc,DC=com",
-    }
-}
-```
-
-Create a ConfigMap with the content of the above Python file.
-
-```bash
-kubectl create configmap custom-ldap-settings \
-  --from-file /PATH/TO/YOUR/custom_ldap_settings.py
-```
-
-Then specify this ConfigMap to the `extra_settings_files` parameter.
-
-```yaml
-spec:
-  extra_settings_files:
-    configmaps:
-      - name: custom-ldap-settings
-        key: custom_ldap_settings.py
-```
-
-!!! note
-    If you have embedded some sensitive information like passwords in the Python file, you can create and pass a Secret instead of a ConfigMap.
-
-    ```bash
-    kubectl create secret generic custom-ldap-settings \
-      --from-file /PATH/TO/YOUR/custom_ldap_settings.py
-    ```
-
-    ```yaml
-    spec:
-      extra_settings_files:
-        secrets:
-          - name: custom-ldap-settings
-            key: custom_ldap_settings.py
-    ```
-
-## Configure LDAP integration via `extra_settings`
-
-!!! note
-    These values are inserted into a Python file, so pay close attention to which values need quotes and which do not.
-
-```yaml
-spec:
-  extra_settings:
-    - setting: AUTH_LDAP_SERVER_URI
-      value: >-
-        "ldaps://ad01.abc.com:636 ldaps://ad02.abc.com:636"
-
-    - setting: AUTH_LDAP_BIND_DN
-      value: >-
-        "CN=LDAP User,OU=Service Accounts,DC=abc,DC=com"
-
-    - setting: AUTH_LDAP_USER_SEARCH
-      value: 'LDAPSearch("DC=abc,DC=com",ldap.SCOPE_SUBTREE,"(sAMAccountName=%(user)s)",)'
-
-    - setting: AUTH_LDAP_GROUP_SEARCH
-      value: 'LDAPSearch("OU=Groups,DC=abc,DC=com",ldap.SCOPE_SUBTREE,"(objectClass=group)",)'
-
-    - setting: AUTH_LDAP_GROUP_TYPE
-      value: 'GroupOfNamesType()'
-
-    - setting: AUTH_LDAP_USER_ATTR_MAP
-      value: '{"first_name": "givenName","last_name": "sn","email": "mail"}'
-
-    - setting: AUTH_LDAP_REQUIRE_GROUP
-      value: >-
-        "CN=operators,OU=Groups,DC=abc,DC=com"
-    - setting: AUTH_LDAP_USER_FLAGS_BY_GROUP
-      value: {
-        "is_superuser": [
-          "CN=admin,OU=Groups,DC=abc,DC=com"
-        ]
-      }
-
-    - setting: AUTH_LDAP_ORGANIZATION_MAP
-      value: {
-        "abc": {
-          "admins": "CN=admin,OU=Groups,DC=abc,DC=com",
-          "remove_users": false,
-          "remove_admins": false,
-          "users": true
-        }
-      }
-
-    - setting: AUTH_LDAP_TEAM_MAP
-      value: {
-        "admin": {
-          "remove": true,
-          "users": "CN=admin,OU=Groups,DC=abc,DC=com",
-          "organization": "abc"
-        }
-      }
-```

docs/user-guide/advanced-configuration/exporting-environment-variables-to-containers.md

@@ -1,31 +0,0 @@
-# Exporting Environment Variables to Containers
-
-If you need to export custom environment variables to your containers.
-
-| Name              | Description                                            | Default |
-| ----------------- | ------------------------------------------------------ | ------- |
-| task_extra_env    | Environment variables to be added to Task container    | ''      |
-| web_extra_env     | Environment variables to be added to Web container     | ''      |
-| rsyslog_extra_env | Environment variables to be added to Rsyslog container | ''      |
-| ee_extra_env      | Environment variables to be added to EE container      | ''      |
-
-!!! warning
-    The `ee_extra_env` will only take effect to the globally available Execution Environments. For custom `ee`, please [customize the Pod spec](https://docs.ansible.com/ansible-tower/latest/html/administration/external_execution_envs.html#customize-the-pod-spec).
-
-Example configuration of environment variables
-
-```yaml
-  spec:
-    task_extra_env: |
-      - name: MYCUSTOMVAR
-        value: foo
-    web_extra_env: |
-      - name: MYCUSTOMVAR
-        value: foo
-    rsyslog_extra_env: |
-      - name: MYCUSTOMVAR
-        value: foo
-    ee_extra_env: |
-      - name: MYCUSTOMVAR
-        value: foo
-```

docs/user-guide/advanced-configuration/extra-settings.md

@@ -1,120 +0,0 @@
-# Extra Settings
-
-With `extra_settings` and `extra_settings_files`, you can pass multiple custom settings to AWX via the AWX Operator.
-
-!!! note
-    Parameters configured in `extra_settings` or `extra_settings_files` are set as read-only settings in AWX. As a result, they cannot be changed in the UI after deployment.
-
-    If you need to change the setting after the initial deployment, you need to change it on the AWX CR spec (for `extra_settings`) or corresponding ConfigMap or Secret (for `extra_settings_files`). After updating ConfigMap or Secret, you need to restart the AWX pods to apply the changes.
-
-!!! note
-    If the same setting is set in both `extra_settings` and `extra_settings_files`, the setting in `extra_settings_files` will take precedence.
-
-## Add extra settings with `extra_settings`
-
-You can pass extra settings by specifying the pair of the setting name and value as the `extra_settings` parameter.
-
-The settings passed via `extra_settings` will be appended to the `/etc/tower/settings.py`.
-
-| Name           | Description    | Default   |
-| -------------- | -------------- | --------- |
-| extra_settings | Extra settings | `[]`      |
-
-Example configuration of `extra_settings` parameter
-
-```yaml
-spec:
-  extra_settings:
-    - setting: MAX_PAGE_SIZE
-      value: "500"
-
-    # LDAP is deprecated
-    - setting: AUTH_LDAP_BIND_DN
-      value: "cn=admin,dc=example,dc=com"
-
-    - setting: LOG_AGGREGATOR_LEVEL
-      value: "'DEBUG'"
-```
-
-Note for some settings, such as `LOG_AGGREGATOR_LEVEL`, the value may need double quotes.
-
-## Add extra settings with `extra_settings_files`
-
-You can pass extra settings by specifying the additional settings files in the ConfigMaps or Secrets as the `extra_settings_files` parameter.
-
-The settings files passed via `extra_settings_files` will be mounted as the files under the `/etc/tower/conf.d`.
-
-| Name                 | Description          | Default   |
-| -------------------- | -------------------- | --------- |
-| extra_settings_files | Extra settings files | `{}`      |
-
-!!! note
-    If the same setting is set in multiple files in `extra_settings_files`, it would be difficult to predict which would be adopted since these files are loaded in arbitrary order that [`glob`](https://docs.python.org/3/library/glob.html) returns. For a reliable setting, do not include the same key in more than one file.
-
-Create ConfigMaps or Secrets that contain custom settings files (`*.py`).
-
-```python title="custom_job_settings.py"
-AWX_TASK_ENV = {
-    "HTTPS_PROXY": "http://proxy.example.com:3128",
-    "HTTP_PROXY": "http://proxy.example.com:3128",
-    "NO_PROXY": "127.0.0.1,localhost,.example.com"
-}
-GALAXY_TASK_ENV = {
-    "ANSIBLE_FORCE_COLOR": "false",
-    "GIT_SSH_COMMAND": "ssh -o StrictHostKeyChecking=no",
-}
-```
-
-```python title="custom_system_settings.py"
-REMOTE_HOST_HEADERS = [
-    "HTTP_X_FORWARDED_FOR",
-    "REMOTE_ADDR",
-    "REMOTE_HOST",
-]
-```
-
-```python title="custom_passwords.py"
-SUBSCRIPTIONS_PASSWORD = "my-super-secure-subscription-password123!"
-REDHAT_PASSWORD = "my-super-secure-redhat-password123!"
-```
-
-```bash title="Create ConfigMap and Secret"
-# Create ConfigMap
-kubectl create configmap my-custom-settings \
-  --from-file /PATH/TO/YOUR/custom_job_settings.py \
-  --from-file /PATH/TO/YOUR/custom_system_settings.py
-
-# Create Secret
-kubectl create secret generic my-custom-passwords \
-  --from-file /PATH/TO/YOUR/custom_passwords.py
-```
-
-Then specify them in the AWX CR spec. Here is an example configuration of `extra_settings_files` parameter.
-
-```yaml
-spec:
-  extra_settings_files:
-    configmaps:
-      - name: my-custom-settings        # The name of the ConfigMap
-        key: custom_job_settings.py     # The key in the ConfigMap, which means the file name
-      - name: my-custom-settings
-        key: custom_system_settings.py
-    secrets:
-      - name: my-custom-passwords       # The name of the Secret
-        key: custom_passwords.py        # The key in the Secret, which means the file name
-```
-
-!!! Warning "Restriction"
-    There are some restrictions on the ConfigMaps or Secrets used in `extra_settings_files`.
-
-    - The keys in ConfigMaps or Secrets MUST be the name of python files and MUST end with `.py`
-    - The keys in ConfigMaps or Secrets MUST consists of alphanumeric characters, `-`, `_` or `.`
-    - The keys in ConfigMaps or Secrets are converted to the following strings, which MUST not exceed 63 characters
-        - Keys in ConfigMaps: `<instance name>-<KEY>-configmap`
-        - Keys in Secrets: `<instance name>-<KEY>-secret`
-    - Following keys are reserved and MUST NOT be used in ConfigMaps or Secrets
-        - `credentials.py`
-        - `execution_environments.py`
-        - `ldap.py`
-
-    Refer to the Kubernetes documentations ([[1]](https://kubernetes.io/docs/reference/kubernetes-api/config-and-storage-resources/config-map-v1/), [[2]](https://kubernetes.io/docs/reference/kubernetes-api/config-and-storage-resources/secret-v1/), [[3]](https://kubernetes.io/docs/reference/kubernetes-api/config-and-storage-resources/volume/), [[4]](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/)) for more information about character types and length restrictions.

docs/user-guide/advanced-configuration/horizontal-pod-autoscaler.md

@@ -1,24 +0,0 @@
-# Horizontal Pod Autoscaler (HPA)
-
-Horizontal Pod Autoscaler allows Kubernetes to scale the number of replicas of
-deployments in response to configured metrics.
-
-This feature conflicts with the operators ability to manage the number of static
-replicas to create for each deployment.
-
-The use of the settings below will tell the operator to not manage the replicas
-field on the identified deployments even if a replicas count has been set for those
-properties in the operator resource.
-
-| Name                   | Description                                                                   | Default |
-| ---------------------- | ----------------------------------------------------------------------------- | ------- |
-| web_manage_replicas    | Indicates operator should control the replicas count for the web deployment.  | true    |
-| task_manage_replicas   | Indicates operator should control the replicas count for the task deployment. | true    |
-
-## Recommended Settings for HPA
-
-Please see the Kubernetes documentation on how to configure the horizontal pod
-autoscaler.
-
-The values for optimal HPA are cluster and need specific so general guidelines
-are not available at this time.

docs/user-guide/advanced-configuration/host-aliases.md

@@ -1,19 +0,0 @@
-# HostAliases
-
-Sometimes you might need to use [HostAliases](https://kubernetes.io/docs/tasks/network/customize-hosts-file-for-pods/) in web/task containers.
-
-| Name         | Description           | Default |
-| ------------ | --------------------- | ------- |
-| host_aliases | A list of HostAliases | None    |
-
-Example of customization could be:
-
-```yaml
----
-spec:
-  ...
-  host_aliases:
-    - ip: <name-of-your-ip>
-      hostnames:
-        - <name-of-your-domain>
-```

docs/user-guide/advanced-configuration/labeling-operator-managed-objects.md

@@ -1,26 +0,0 @@
-# Labeling operator managed objects
-
-In certain situations labeling of Kubernetes objects managed by the operator might be desired (e.g. for owner identification purposes).
-For that `additional_labels` parameter could be used:
-
-| Name                        | Description                                                                              | Default |
-| --------------------------- | ---------------------------------------------------------------------------------------- | ------- |
-| additional_labels           | Additional labels defined on the resource, which should be propagated to child resources | []      |
-
-Example configuration where only `my/team` and `my/service` labels will be propagated to child objects (`Deployment`, `Secret`s, `ServiceAccount`, etc):
-
-```yaml
-apiVersion: awx.ansible.com/v1beta1
-kind: AWX
-metadata:
-  name: awx-demo
-  labels:
-    my/team: "foo"
-    my/service: "bar"
-    my/do-not-inherit: "yes"
-spec:
-  additional_labels:
-    - my/team
-    - my/service
-...
-```

docs/user-guide/advanced-configuration/mesh-ingress.md

@@ -1,229 +0,0 @@
-# Mesh Ingress
-
-The mesh ingress allows users to peer external execution and hop nodes into the AWX control plane.
-This guide focuses on how to enable and configure the mesh ingress.
-For more information about remote execution and hop nodes and how to create them, refer to the [Managing Capacity With Instances](https://ansible.readthedocs.io/projects/awx/en/latest/administration/instances.html) chapter of the AWX Administration Guide.
-
-## Prerequisites
-
-- AWX operator version > 2.11.0
-- AWX > 23.8.0
-
-## Deploy and configure AWXMeshIngress
-
-!!! note
-    The mesh ingress uses the `control_plane_ee_image` and `image_pull_policy` fields of the AWX instance to determine image and policy to be adopted.
-    Defaulted to `quay.io/ansible/awx-ee:latest` and `Always`.
-    Currently there are no dedicated parameters to specify the image and policy.
-
-### On Red Hat OpenShift with Operator managed Route
-
-To deploy a mesh ingress on OpenShift, create the AWXMeshIngress resource on the namespace where your AWX instance is running on.
-
-Example:
-
-```yaml
----
-apiVersion: awx.ansible.com/v1alpha1
-kind: AWXMeshIngress
-metadata:
-  name: <mesh ingress name>
-spec:
-  deployment_name: <awx instance name>
-```
-
-### On Kubernetes with Operator managed Ingress (NGINX)
-
-To deploy a mesh ingress on Kubernetes cluster which has [NGINX Ingress Controller](https://www.nginx.com/products/nginx-ingress-controller/), create the AWXMeshIngress resource on the namespace where your AWX instance is running on.
-
-Note that AWXMeshIngress requires [SSL Passthrough](https://kubernetes.github.io/ingress-nginx/user-guide/tls/#ssl-passthrough) enabled which is disabled by default. Ensure it is enabled on your NGINX Ingress Controller.
-
-By specifying `ingress_controller` as `nginx`, AWX Operator will generate Ingress resource that has `nginx.ingress.kubernetes.io/ssl-passthrough` annotation set to `"true"`.
-
-Example:
-
-```yaml
----
-apiVersion: awx.ansible.com/v1alpha1
-kind: AWXMeshIngress
-metadata:
-  name: <mesh ingress name>
-spec:
-  deployment_name: <awx instance name>
-
-  ingress_type: Ingress
-  ingress_controller: nginx
-  ingress_class_name: nginx
-
-  external_hostname: <fqdn for mesh ingress>
-```
-
-### On Kubernetes with Operator managed Ingress (Traefik)
-
-To deploy a mesh ingress on Kubernetes cluster which has [Traefik Kubernetes Ingress provider](https://doc.traefik.io/traefik/providers/kubernetes-ingress/), create the AWXMeshIngress resource on the namespace where your AWX instance is running on.
-
-Note that by deploying following AWXMeshIngress, AWX Operator will generate IngressRouteTCP resource that has `websecure` as an `entryPoints`. If this does not satisfy your requirement, refer to [User managed Ingress section](#on-kubernetes-with-user-managed-ingress) and  create an IngressRouteTCP resource manually.
-
-Example:
-
-```yaml
----
-apiVersion: awx.ansible.com/v1alpha1
-kind: AWXMeshIngress
-metadata:
-  name: <mesh ingress name>
-spec:
-  deployment_name: <awx instance name>
-
-  ingress_type: IngressRouteTCP
-  ingress_controller: traefik
-  ingress_class_name: traefik
-  ingress_api_version: traefik.io/v1alpha1
-
-  external_hostname: <fqdn for mesh ingress>
-```
-
-!!! tip
-    AWX Operator supports both API groups `traefik.io` and `traefik.containo.us` in `ingress_api_version` for Traefik, but it is recommended to use `traefik.io` since `traefik.containo.us` is deprecated in Traefik v2.10 and is removed in Traefik v3. Refer to [Traefik documentation](https://doc.traefik.io/traefik/migration/v2/#v210) for more information about deprecation.
-
-    If you can't see any IngressRouteTCP resources by `kubectl` command after deploying mesh ingress, you should fully qualify the resource name with API group, `kubectl get ingressroutetcp.traefik.io` or `kubectl get ingressroutetcp.traefik.containo.us` for example.
-
-### On Kubernetes with User managed Ingress
-
-To deploy a mesh ingress on Kubernetes cluster, create the AWXMeshIngress resource on the namespace where your AWX instance is running on.
-
-Alternatively, if you wish to create your own Ingress resource, you can deploy a mesh ingress with `ingress_type` set to `none` and then manually create an Ingress resource with any configuration.
-
-In this case, the `external_hostname` is still required as it is used to generate the certificate that will be used by Receptor.
-
-Example:
-
-```yaml
----
-apiVersion: awx.ansible.com/v1alpha1
-kind: AWXMeshIngress
-metadata:
-  name: <mesh ingress name>
-spec:
-  deployment_name: <awx instance name>
-
-  ingress_type: none  # This line can be omitted since this is the default value
-  external_hostname: <fqdn for mesh ingress>
-```
-
-The requirements for user managed Ingress resource are as follows:
-
-- Supports WebSocket
-- SSL/TLS Passthrough enabled
-- Accessible over port `443`
-- Having the same hostname as `external_hostname` in the AWXMeshIngress resource
-- Routing the traffic to port `27199` of the Service of the same name as the AWXMeshIngress resource
-
-These are example Ingress resources for NGINX and Traefik.
-
-```yaml
-# Ingress for NGINX Ingress Controller
----
-apiVersion: networking.k8s.io/v1
-kind: Ingress
-metadata:
-  name: <mesh ingress name>
-  annotations:
-    nginx.ingress.kubernetes.io/ssl-passthrough: "true"
-spec:
-  ingressClassName: nginx
-  rules:
-    - host: <fqdn for mesh ingress>
-      http:
-        paths:
-          - path: /
-            pathType: Prefix
-            backend:
-              service:
-                name: <mesh ingress name>
-                port:
-                  number: 27199
-```
-
-```yaml
-# Ingress for Traefik Kubernetes Ingress provider
----
-apiVersion: traefik.io/v1alpha1
-kind: IngressRouteTCP
-metadata:
-  name: <mesh ingress name>
-spec:
-  entryPoints:
-    - websecure
-  routes:
-    - match: HostSNI(`<fqdn for mesh ingress>`)
-      services:
-        - name: <mesh ingress name>
-          port: 27199
-  tls:
-    passthrough: true
-```
-
-## Validating setup of Mesh Ingress
-
-After AWXMeshIngress has been successfully created, a new Instance with the same name will be registered to AWX and will be visible on the Instance UI page
-
-![mesh ingress instance on AWX UI](./images/mesh-ingress-instance-on-awx-ui.png)
-
-The Instance should have at least 2 listener addresses.
-
-In this example, the mesh ingress has two listener addresses:
-
-- one for internal, that is used for peering to by all control nodes (top)
-- one for external, that is exposed to a route so external execution nodes can peer into it (bottom))
-
-![mesh ingress instance listener address on awx ui](./images/mesh-ingress-instance-listener-address-on-awx-ui.png)
-
-When selecting peer for new instance the mesh ingress instance should now be present as a option.
-![peering to mesh ingress on awx ui](./images/peering-to-mesh-ingress-on-awx-ui.png)
-
-For more information about how to create external remote execution and hop nodes and configuring the mesh, see AWX Documentation on [Add a instance](https://ansible.readthedocs.io/projects/awx/en/latest/administration/instances.html#add-an-instance).
-
-## Custom Resource Definitions
-
-### AWXMeshIngress
-
-AWXMeshIngress controls the deployment and configuration of mesh ingress on AWX
-
-| Name                                                                                                                          | Description                                                                                                                                                         |
-| ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`apiVersion`**                                                                                                              | awx.ansible.com/v1alpha1                                                                                                                                            |
-| **`kind`**                                                                                                                    | AWXMeshIngress                                                                                                                                                      |
-| **`metadata`** ([ObjectMeta](https://kubernetes.io/docs/reference/kubernetes-api/common-definitions/object-meta/#ObjectMeta)) | Standard object's metadata. [More info](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata)                               |
-| **`spec`** ([AWXMeshIngressSpec](#awxmeshingressspec))                                                                        | Spec is the desired state of the AWXMeshIngress. [More info](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status)   |
-| **`status`** ([AWXMeshIngressStatus](#awxmeshingressstatus))                                                                  | Status is the current state of the AWXMeshIngress. [More info](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status) |
-
-#### AWXMeshIngressSpec
-
-AWXMeshIngressSpec is the description of the configuration for AWXMeshIngress.
-
-| Name                                     | Description                                                                                                                                                                                                                                 | Default                                        |
-| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
-| **`deployment_name`** (string), required | Name of the AWX deployment to create the Mesh Ingress for.                                                                                                                                                                                  | `awx`                                          |
-| **`ingress_type`** (string)              | Ingress type for ingress managed by the operator. Options: `none`, `Ingress`, `IngressRouteTCP`, `Route`                                                                                                                                    | `Route` (on OpenShift), `none` (on Kubernetes) |
-| **`external_hostname`** (string)         | External hostname is an optional field used for specifying the external hostname defined in an [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/). This parameter is automatically generated on OpenShift          | N/A                                            |
-| **`external_ipaddress`** (string)        | External IP Address is an optional field used for specifying the external IP address defined in an [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/)                                                              | N/A                                            |
-| **`ingress_api_version`** (string)       | API Version for ingress managed by the operator. This parameter is ignored when `ingress_type` is `Route`                                                                                                                                   | `networking.k8s.io/v1`                         |
-| **`ingress_annotations`** (string)       | Additional annotation on the ingress managed by the operator. This parameter is ignored when `ingress_type` is `Route`                                                                                                                      | `""`                                           |
-| **`ingress_controller`** (string)        | Special configuration for specific Ingress Controllers. This parameter is ignored when `ingress_type` is `Route`                                                                                                                            | `""`                                           |
-| **`ingress_class_name`** (string)        | The name of ingress class to use instead of the cluster default. see [IngressSpec](https://kubernetes.io/docs/reference/kubernetes-api/service-resources/ingress-v1/#IngressSpec). This parameter is ignored when `ingress_type` is `Route` | `""`                                           |
-
-#### AWXMeshIngressStatus
-
-AWXMeshIngressStatus describe the current state of the AWXMeshIngress.
-
-### AWXMeshIngressList
-
-AWXMeshIngressList is a collection of AWXMeshIngress.
-
-| Name                                                                                                                    | Description                                                                                                                                                                                                                                                                                          |
-| ----------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **`items`** ([AWXMeshIngress](#awxmeshingress))                                                                         | items is the list of Ingress.                                                                                                                                                                                                                                                                        |
-| **`apiVersion`** (string)                                                                                               | APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. [More info](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources)  |
-| **`kind`** (string)                                                                                                     | Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. [More info](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds) |
-| **`metadata`** ([ListMeta](https://kubernetes.io/docs/reference/kubernetes-api/common-definitions/list-meta/#ListMeta)) | Standard object's metadata. [More info](https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata)                                                                                                                                                                |

docs/user-guide/advanced-configuration/no-log.md

@@ -1,14 +0,0 @@
-# No Log
-
-Configure no_log for tasks with no_log
-
-| Name   | Description          | Default |
-| ------ | -------------------- | ------- |
-| no_log | No log configuration | 'true'  |
-
-Example configuration of `no_log` parameter
-
-```yaml
-spec:
-  no_log: true
-```

docs/user-guide/advanced-configuration/persisting-projects-directory.md

@@ -1,22 +0,0 @@
-# Persisting Projects Directory
-
-In cases which you want to persist the `/var/lib/projects` directory, there are few variables that are customizable for the `awx-operator`.
-
-| Name                         | Description                                                                                    | Default       |
-| ---------------------------- | ---------------------------------------------------------------------------------------------- | ------------- |
-| projects_persistence         | Whether or not the /var/lib/projects directory will be persistent                              | false         |
-| projects_storage_class       | Define the PersistentVolume storage class                                                      | ''            |
-| projects_storage_size        | Define the PersistentVolume size                                                               | 8Gi           |
-| projects_storage_access_mode | Define the PersistentVolume access mode                                                        | ReadWriteMany |
-| projects_existing_claim      | Define an existing PersistentVolumeClaim to use (cannot be combined with `projects_storage_*`) | ''            |
-
-Example of customization when the `awx-operator` automatically handles the persistent volume could be:
-
-```yaml
----
-spec:
-  ...
-  projects_persistence: true
-  projects_storage_class: rook-ceph
-  projects_storage_size: 20Gi
-```

docs/user-guide/advanced-configuration/pods-termination-grace-period.md

@@ -1,18 +0,0 @@
-# Pods termination grace period
-
-During deployment restarts or new rollouts, when old ReplicaSet Pods are being terminated, the corresponding jobs which are managed (executed or controlled) by old AWX Pods may end up in `Error` state as there is no mechanism to transfer them to the newly spawned AWX Pods.
-To work around the problem one could set `termination_grace_period_seconds` in AWX spec, which does the following:
-
-- It sets the corresponding [`terminationGracePeriodSeconds`](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination) Pod spec of the AWX Deployment to the value provided
-    - The grace period is the duration in seconds after the processes running in the pod are sent a termination signal and the time when the processes are forcibly halted with a kill signal
-
-- It adds a [`PreStop`](https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/#hook-handler-execution) hook script, which will keep AWX Pods in terminating state until it finished, up to `terminationGracePeriodSeconds`.
-    - This grace period applies to the total time it takes for both the PreStop hook to execute and for the Container to stop normally
-    - While the hook script just waits until the corresponding AWX Pod (instance) no longer has any managed jobs, in which case it finishes with success and hands over the overall Pod termination process to normal AWX processes.
-
-One may want to set this value to the maximum duration they accept to wait for the affected Jobs to finish.
-Keeping in mind that such finishing jobs may increase Pods termination time in such situations as `kubectl rollout restart`, AWX upgrade by the operator, or Kubernetes [API-initiatedevictions](https://kubernetes.io/docs/concepts/scheduling-eviction/api-eviction/).
-
-| Name                             | Description                                                     | Default |
-| -------------------------------- | --------------------------------------------------------------- | ------- |
-| termination_grace_period_seconds | Optional duration in seconds pods needs to terminate gracefully | not set |

docs/user-guide/advanced-configuration/priority-classes.md

@@ -1,12 +0,0 @@
-# Priority Classes
-
-The AWX and Postgres pods can be assigned a custom PriorityClass to rank their importance compared to other pods in your cluster, which determines which pods get evicted first if resources are running low.
-First, [create your PriorityClass](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#priorityclass) if needed.
-Then set the name of your priority class to the control plane and postgres pods as shown below.
-
-```yaml
-spec:
-  ...
-  control_plane_priority_class: awx-demo-high-priority
-  postgres_priority_class: awx-demo-medium-priority
-```

docs/user-guide/advanced-configuration/privileged-tasks.md

@@ -1,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:
-
-```yaml
----
-spec:
-  ...
-  task_privileged: true
-```
-
-If you are attempting to do this on an OpenShift cluster, you will need to grant the `awx` ServiceAccount the `privileged` SCC, which can be done with:
-
-```sh
-oc adm policy add-scc-to-user privileged -z awx
-```
-
-Again, this is the most relaxed SCC that is provided by OpenShift, so be sure to familiarize yourself with the security concerns that accompany this action.

docs/user-guide/advanced-configuration/redis-container-capabilities.md

@@ -1,13 +0,0 @@
-# Redis container capabilities
-
-Depending on your kubernetes cluster and settings you might need to grant some capabilities to the redis container so it can start. Set the `redis_capabilities` option so the capabilities are added in the deployment.
-
-```yaml
----
-spec:
-  ...
-  redis_capabilities:
-    - CHOWN
-    - SETUID
-    - SETGID
-```

docs/user-guide/advanced-configuration/scaling-the-web-and-task-pods-independently.md

@@ -1,13 +0,0 @@
-# Scaling the Web and Task Pods independently
-
-You can scale replicas up or down for each deployment by using the `web_replicas` or `task_replicas` respectively. You can scale all pods across both deployments by using `replicas` as well. The logic behind these CRD keys acts as such:
-
-- If you specify the `replicas` field, the key passed will scale both the `web` and `task` replicas to the same number.
-- If `web_replicas` or `task_replicas` is ever passed, it will override the existing `replicas` field on the specific deployment with the new key value.
-
-These new replicas can be constrained in a similar manner to previous single deployments by appending the particular deployment name in front of the constraint used. More about those new constraints can be found in the [Assigning AWX pods to specific nodes](./assigning-awx-pods-to-specific-nodes.md) page.
-
-## Horizontal Pod Autoscaling
-
-The operator is capable of working with Kubernetes' HPA capabilities.  See [Horizontal Pod Autoscaler](./horizontal-pod-autoscaler.md)
-documentation for more information.

docs/user-guide/advanced-configuration/security-context.md

@@ -1,21 +0,0 @@
-# Security Context
-
-It is possible to modify some `SecurityContext` proprieties of the various deployments and stateful sets if needed.
-
-| Name                               | Description                                  | Default |
-| ---------------------------------- | -------------------------------------------- | ------- |
-| security_context_settings          | SecurityContext for Task and Web deployments | {}      |
-| postgres_security_context_settings | SecurityContext for PostgreSQL container | {}      |
-
-Example configuration securityContext for the Task and Web deployments:
-
-```yaml
-spec:
-  security_context_settings:
-    allowPrivilegeEscalation: false
-    capabilities:
-        drop:
-        - ALL
-  postgres_security_context_settings:
-    runAsNonRoot: true
-```

docs/user-guide/advanced-configuration/service-account.md

@@ -1,15 +0,0 @@
-# Service Account
-
-If you need to modify some `ServiceAccount` proprieties
-
-| Name                        | Description                       | Default |
-| --------------------------- | --------------------------------- | ------- |
-| service_account_annotations | Annotations to the ServiceAccount | ''      |
-
-Example configuration of environment variables
-
-```yaml
-spec:
-  service_account_annotations: |
-    eks.amazonaws.com/role-arn: arn:aws:iam::<ACCOUNT_ID>:role/<IAM_ROLE_NAME>
-```

docs/user-guide/advanced-configuration/session-cookie-secure-setting.md

@@ -1,14 +0,0 @@
-# Session Cookie Secure Setting
-
-With `session_cookie_secure`, you can pass the value for `SESSION_COOKIE_SECURE` to `/etc/tower/settings.py`
-
-| Name                  | Description           | Default |
-| --------------------- | --------------------- | ------- |
-| session_cookie_secure | Session Cookie Secure | ''      |
-
-Example configuration of the `session_cookie_secure` setting:
-
-```yaml
-  spec:
-    session_cookie_secure: 'False'
-```

docs/user-guide/advanced-configuration/trusting-a-custom-certificate-authority.md

@@ -1,54 +0,0 @@
-# Trusting a Custom Certificate Authority
-
-In cases which you need to trust a custom Certificate Authority, there are few variables you can customize for the `awx-operator`.
-
-Trusting a custom Certificate Authority allows the AWX to access network services configured with SSL certificates issued locally, such as cloning a project from from an internal Git server via HTTPS. It is common for these scenarios, experiencing the error [unable to verify the first certificate](https://github.com/ansible/awx-operator/issues/376).
-
-| Name                                | Description                              | Default |
-|-------------------------------------| ---------------------------------------- |---------|
-| ldap_cacert_secret _(deprecated)_   | LDAP Certificate Authority secret name   | ''      |
-| ldap_password_secret _(deprecated)_ | LDAP BIND DN Password secret name        | ''      |
-| bundle_cacert_secret                | Certificate Authority secret name        | ''      |
-
-Please note the `awx-operator` will look for the data field `ldap-ca.crt` in the specified secret when using the `ldap_cacert_secret`, whereas the data field `bundle-ca.crt` is required for `bundle_cacert_secret` parameter.
-
-Example of customization could be:
-
-```yaml
----
-spec:
-  ...
-  ldap_cacert_secret: <resourcename>-custom-certs
-  ldap_password_secret: <resourcename>-ldap-password
-  bundle_cacert_secret: <resourcename>-custom-certs
-```
-
-Create the secret with `kustomization.yaml` file:
-
-```yaml
-...
-secretGenerator:
-  - name: <resourcename>-custom-certs
-    files:
-      - bundle-ca.crt=<path+filename>
-    options:
-      disableNameSuffixHash: true
-...
-```
-
-Create the secret with CLI:
-
-* Certificate Authority secret
-
-    ```sh
-    kubectl create secret generic <resourcename>-custom-certs \
-      --from-file=ldap-ca.crt=<PATH/TO/YOUR/CA/PEM/FILE>  \
-      --from-file=bundle-ca.crt=<PATH/TO/YOUR/CA/PEM/FILE>
-    ```
-
-* LDAP BIND DN Password secret
-
-    ```sh
-    kubectl create secret generic <resourcename>-ldap-password \
-      --from-literal=ldap-password=<your_ldap_dn_password>
-    ```