feat: bump operator version to 0.20.1

README.md

@@ -29,15 +29,15 @@ An example implementation of AWX on single node K3s using AWX Operator, with eas
   - CentOS Stream 8 (Minimal)
   - K3s v1.22.7+k3s1
 - Products that will be deployed:
-  - AWX Operator 0.20.0
-  - AWX 20.1.0
+  - AWX Operator 0.20.1
+  - AWX 21.0.0
   - PostgreSQL 12
 
 ## References
 
 - [K3s - Lightweight Kubernetes](https://rancher.com/docs/k3s/latest/en/)
-- [INSTALL.md on ansible/awx](https://github.com/ansible/awx/blob/20.1.0/INSTALL.md) @20.1.0
-- [README.md on ansible/awx-operator](https://github.com/ansible/awx-operator/blob/0.20.0/README.md) @0.20.0
+- [INSTALL.md on ansible/awx](https://github.com/ansible/awx/blob/21.0.0/INSTALL.md) @21.0.0
+- [README.md on ansible/awx-operator](https://github.com/ansible/awx-operator/blob/0.20.1/README.md) @0.20.1
 
 ## Requirements
 
@@ -83,7 +83,7 @@ Install specified version of AWX Operator. Note that this procedure is applicabl
 cd ~
 git clone https://github.com/ansible/awx-operator.git
 cd awx-operator
-git checkout 0.20.0
+git checkout 0.20.1
 ```
 
 Export the name of the namespace where you want to deploy AWX Operator as the environment variable `NAMESPACE` and run `make deploy`. The default namespace is `awx`.
@@ -190,7 +190,7 @@ $ kubectl -n awx logs -f deployments/awx-operator-controller-manager -c awx-mana
 ...
 ----- Ansible Task Status Event StdOut (awx.ansible.com/v1beta1, Kind=AWX, awx/awx) -----
 PLAY RECAP *********************************************************************
-localhost                  : ok=66   changed=0    unreachable=0    failed=0    skipped=43   rescued=0    ignored=0
+localhost                  : ok=65   changed=0    unreachable=0    failed=0    skipped=43   rescued=0    ignored=0
 ```
 
 Required objects has been deployed next to AWX Operator in `awx` namespace.

acme/README.md

@@ -42,7 +42,7 @@ This guide does not provide any information how to configure Azure, other DNS se
 Deploy cert-manager first.
 
 ```bash
-kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.7.2/cert-manager.yaml
+kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.8.0/cert-manager.yaml
 ```
 
 Ensure the pods in `cert-manager` namespace are running.

backup/ansible/README.md

@@ -30,7 +30,7 @@ An example simple playbook for Ansible is also provided in this repository. This
 | - | - | - |
 | `awxbackup_namespace` | The name of the NameSpace where the `AWXBackup` resource will be created. | `awx` |
 | `awxbackup_name` | The name of the `AWXBackup` resource. Dynamically generated using execution time by default. | `awxbackup-{{ lookup('pipe', 'date +%Y-%m-%d-%H-%M-%S') }}` |
-| `awxbackup_spec` | The `spec` of the `AWXBackup` resource. Refer [official documentation](https://github.com/ansible/awx-operator/tree/0.20.0/roles/backup) for acceptable fields. | `{'deployment_name':'awx','backup_pvc':'awx-backup-claim'}` |
+| `awxbackup_spec` | The `spec` of the `AWXBackup` resource. Refer [official documentation](https://github.com/ansible/awx-operator/tree/0.20.1/roles/backup) for acceptable fields. | `{'deployment_name':'awx','backup_pvc':'awx-backup-claim'}` |
 | `awxbackup_timeout` | Time to wait for backup to complete, in seconds. If exceeded, the playbook will fail. | `600` |
 | `awxbackup_keep_days` | Number of days to keep `AWXBackup` resources. `AWXBackup` resources older than this value will be deleted by this playbook. Set `0` to keep forever. **Note that the actual backup data will remain in the PVC after the `AWXBackup` resource is deleted.** | `30` |
 
@@ -108,9 +108,10 @@ It is also possible to making the backup of the AWX itself where the Job Templat
    - Specify your API Token as `API authentication bearer token`.
    - Toggle `Verify SSL` if needed.
 2. Add new Project including the playbook.
-   - You can specify this repository (`https://github.com/kurokobo/awx-on-k3s.git`) directly, but use with caution. The playbook in this repository is subject to change without notice.
+   - You can specify this repository (`https://github.com/kurokobo/awx-on-k3s.git`) directly, but use with caution. The playbook in this repository is subject to change without notice. You can use [Tag](https://github.com/kurokobo/awx-on-k3s/tags) or [Commit](https://github.com/kurokobo/awx-on-k3s/commits/main) to fix the version to be used.
 3. Add new Job Template which use the playbook.
-   - Select your `backup.yml` as `Playbook`.
    - Select appropriate `Execution Environment`. The default `AWX EE (latest)` (`quay.io/ansible/awx-ee:latest`) contains required collections and modules by defaut, so it's good for the first choice.
+   - Select your `backup.yml` as `Playbook`.
+   - Select your Credentials created in the above step.
    - Specify `Variables` as needed.
 4. (Optional) Add new Schedules for periodic backups.

base/awx.yaml

@@ -5,10 +5,10 @@ metadata:
   name: awx
 spec:
   # These parameters are designed for use with:
-  # - AWX Operator: 0.20.0
-  #   https://github.com/ansible/awx-operator/blob/0.20.0/README.md
-  # - AWX: 20.1.0
-  #   https://github.com/ansible/awx/blob/20.1.0/INSTALL.md
+  # - AWX Operator: 0.20.1
+  #   https://github.com/ansible/awx-operator/blob/0.20.1/README.md
+  # - AWX: 21.0.0
+  #   https://github.com/ansible/awx/blob/21.0.0/INSTALL.md
 
   admin_user: admin
   admin_password_secret: awx-admin-password

restore/README.md

@@ -22,9 +22,14 @@ It is strongly recommended that the version of AWX Operator is the same as the v
 
 ### Prepare for Restore
 
-If your PV, PVC, and Secret still exist, no preparation is required.
+If your AWX instance is running, it is recommended that it be deleted along with any data in the PV for the PostgreSQL first, in order to restore to be succeeded.
 
-If you are restoring the entire AWX to a new environment, create the PVs and PVCs first to be restored.
+```bash
+kubectl -n awx delete awx awx
+sudo rm -rf /data/postgres
+```
+
+Then prepare directories for your PVs. `/data/projects` is required if you are restoring the entire AWX to a new environment.
 
 ```bash
 sudo mkdir -p /data/postgres
@@ -92,7 +97,7 @@ $ kubectl -n awx logs -f deployments/awx-operator-controller-manager -c awx-mana
 ...
 ----- Ansible Task Status Event StdOut (awx.ansible.com/v1beta1, Kind=AWX, awx/awx) -----
 PLAY RECAP *********************************************************************
-localhost                  : ok=68   changed=0    unreachable=0    failed=0    skipped=41   rescued=0    ignored=0
+localhost                  : ok=67   changed=0    unreachable=0    failed=0    skipped=41   rescued=0    ignored=0
 ```
 
 This will create AWXRestore object in the namespace, and now your AWX is restored.

tips/troubleshooting.md

@@ -153,7 +153,7 @@ Typical solutions are one of the following:
       ee_resource_requirements: {}     👈👈👈
     ```
 
-  - You can specify more specific value for each containers. Refer [official documentation](https://github.com/ansible/awx-operator/blob/0.20.0/README.md#containers-resource-requirements) for details.
+  - You can specify more specific value for each containers. Refer [official documentation](https://github.com/ansible/awx-operator/blob/0.20.1/README.md#containers-resource-requirements) for details.
   - In this way you can run AWX with fewer resources, but you may encounter performance issues.
 
 ### The Pod is `Pending` with "1 pod has unbound immediate PersistentVolumeClaims." event

tips/upgrade-operator.md

@@ -11,6 +11,7 @@ Note that once you upgrade AWX Operator, your AWX will also be upgraded automati
 
 | AWX Operator | AWX |
 | - | - |
+| 0.20.1 | 21.0.0 |
 | 0.20.0 | 20.1.0 |
 | 0.19.0 | 20.0.1 |
 | 0.18.0 | 20.0.1 |