mirror of
https://github.com/Expand-sys/awx-on-k3s
synced 2025-12-15 21:42:15 +11:00
feat: bump operator version to 1.3.0
This commit is contained in:
parent
f2326436f1
commit
cb07b78209
8 changed files with 17 additions and 17 deletions
14
README.md
14
README.md
|
|
@ -31,15 +31,15 @@ An example implementation of AWX on single node K3s using AWX Operator, with eas
|
|||
- CentOS Stream 8 (Minimal)
|
||||
- K3s v1.25.6+k3s1
|
||||
- Products that will be deployed:
|
||||
- AWX Operator 1.2.0
|
||||
- AWX 21.12.0
|
||||
- AWX Operator 1.3.0
|
||||
- AWX 21.13.0
|
||||
- PostgreSQL 13
|
||||
|
||||
## References
|
||||
|
||||
- [K3s - Lightweight Kubernetes](https://docs.k3s.io/)
|
||||
- [INSTALL.md on ansible/awx](https://github.com/ansible/awx/blob/21.12.0/INSTALL.md) @21.12.0
|
||||
- [README.md on ansible/awx-operator](https://github.com/ansible/awx-operator/blob/1.2.0/README.md) @1.2.0
|
||||
- [INSTALL.md on ansible/awx](https://github.com/ansible/awx/blob/21.13.0/INSTALL.md) @21.13.0
|
||||
- [README.md on ansible/awx-operator](https://github.com/ansible/awx-operator/blob/1.3.0/README.md) @1.3.0
|
||||
|
||||
## Requirements
|
||||
|
||||
|
|
@ -90,7 +90,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 1.2.0
|
||||
git checkout 1.3.0
|
||||
```
|
||||
|
||||
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`.
|
||||
|
|
@ -127,7 +127,7 @@ If you want to use files suitable for the specific version of AWX Operator, [ref
|
|||
cd ~
|
||||
git clone https://github.com/kurokobo/awx-on-k3s.git
|
||||
cd awx-on-k3s
|
||||
git checkout 1.2.0
|
||||
git checkout 1.3.0
|
||||
```
|
||||
|
||||
Generate a Self-Signed certificate. Note that IP address can't be specified. If you want to use a certificate from public ACME CA such as Let's Encrypt or ZeroSSL instead of Self-Signed certificate, follow the guide on [📁 **Use SSL Certificate from Public ACME CA**](acme) first and come back to this step when done.
|
||||
|
|
@ -200,7 +200,7 @@ $ kubectl -n awx logs -f deployments/awx-operator-controller-manager
|
|||
...
|
||||
----- Ansible Task Status Event StdOut (awx.ansible.com/v1beta1, Kind=AWX, awx/awx) -----
|
||||
PLAY RECAP *********************************************************************
|
||||
localhost : ok=77 changed=0 unreachable=0 failed=0 skipped=71 rescued=0 ignored=1
|
||||
localhost : ok=80 changed=0 unreachable=0 failed=0 skipped=78 rescued=0 ignored=1
|
||||
```
|
||||
|
||||
Required objects has been deployed next to AWX Operator in `awx` namespace.
|
||||
|
|
|
|||
|
|
@ -32,7 +32,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/1.2.0/roles/backup) for acceptable fields. | `deployment_name: awx`<br>`backup_pvc: awx-backup-claim`<br>`clean_backup_on_delete: true` |
|
||||
| `awxbackup_spec` | The `spec` of the `AWXBackup` resource. Refer [official documentation](https://github.com/ansible/awx-operator/tree/1.3.0/roles/backup) for acceptable fields. | `deployment_name: awx`<br>`backup_pvc: awx-backup-claim`<br>`clean_backup_on_delete: true` |
|
||||
| `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. | `30` |
|
||||
|
||||
|
|
|
|||
|
|
@ -5,10 +5,10 @@ metadata:
|
|||
name: awx
|
||||
spec:
|
||||
# These parameters are designed for use with:
|
||||
# - AWX Operator: 1.2.0
|
||||
# https://github.com/ansible/awx-operator/blob/1.2.0/README.md
|
||||
# - AWX: 21.12.0
|
||||
# https://github.com/ansible/awx/blob/21.12.0/INSTALL.md
|
||||
# - AWX Operator: 1.3.0
|
||||
# https://github.com/ansible/awx-operator/blob/1.3.0/README.md
|
||||
# - AWX: 21.13.0
|
||||
# https://github.com/ansible/awx/blob/21.13.0/INSTALL.md
|
||||
|
||||
admin_user: admin
|
||||
admin_password_secret: awx-admin-password
|
||||
|
|
|
|||
|
|
@ -222,7 +222,6 @@ If you simply need additional Ansible collections only, and no additional Pip or
|
|||
|
||||
The procedure is quite simple, create and place `collections/requirements.yml` on your project root including the list of the collections which you want to use.
|
||||
|
||||
The format of `collections/requirements.yml` is the same as [the `requirements.yml` for ansible-galaxy](
|
||||
https://docs.ansible.com/ansible/latest/galaxy/user_guide.html#install-multiple-collections-with-a-requirements-file).
|
||||
The format of `collections/requirements.yml` is the same as [the `requirements.yml` for ansible-galaxy](https://docs.ansible.com/ansible/latest/galaxy/user_guide.html#install-multiple-collections-with-a-requirements-file).
|
||||
|
||||
If `collections/requirements.yml` is present in your project, AWX will install the collections accordingly while updating project.
|
||||
|
|
|
|||
|
|
@ -100,7 +100,7 @@ $ kubectl -n awx logs -f deployments/awx-operator-controller-manager
|
|||
...
|
||||
----- Ansible Task Status Event StdOut (awx.ansible.com/v1beta1, Kind=AWX, awx/awx) -----
|
||||
PLAY RECAP *********************************************************************
|
||||
localhost : ok=79 changed=0 unreachable=0 failed=0 skipped=69 rescued=0 ignored=1
|
||||
localhost : ok=82 changed=0 unreachable=0 failed=0 skipped=76 rescued=0 ignored=1
|
||||
```
|
||||
|
||||
This will create AWXRestore object in the namespace, and now your AWX is restored.
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ This repository includes ready-to-use files as an example to run Ansible Runner.
|
|||
- CentOS Stream 8 (Minimal)
|
||||
- Python 3.9
|
||||
- Docker 20.10.17
|
||||
- Ansible Runner 2.3.1
|
||||
- Ansible Runner 2.3.2
|
||||
|
||||
## Install
|
||||
|
||||
|
|
|
|||
|
|
@ -179,7 +179,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/1.2.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/1.3.0/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
|
||||
|
|
|
|||
|
|
@ -10,6 +10,7 @@ The table below maps the AWX Operator versions and bundled AWX versions.
|
|||
|
||||
| AWX Operator | AWX |
|
||||
| - | - |
|
||||
| 1.3.0 | 21.13.0 |
|
||||
| 1.2.0 | 21.12.0 |
|
||||
| 1.1.4 | 21.11.0 |
|
||||
| 1.1.3 | 21.10.2 |
|
||||
|
|
|
|||
Loading…
Reference in a new issue