docs: correct minor issues

This commit is contained in:
kurokobo 2023-05-11 22:40:15 +09:00
parent 34bc330f0b
commit 65b1fcf40b
4 changed files with 7 additions and 7 deletions

View file

@ -6,7 +6,7 @@ An example implementation of AWX on single node K3s using AWX Operator, with eas
- Accessible over HTTPS from remote host - Accessible over HTTPS from remote host
- All data will be stored under `/data` - All data will be stored under `/data`
- Fixed (configurable) passwords for AWX and PostgreSQL - Fixed (configurable) passwords for AWX and PostgreSQL
- Fixed (configurable) versions of AWX and PostgreSQL - Fixed (configurable) versions of AWX
**If you want to view the guide for the specific version of AWX Operator, switch the page to the desired tag instead of the `main` branch.** **If you want to view the guide for the specific version of AWX Operator, switch the page to the desired tag instead of the `main` branch.**
@ -296,7 +296,7 @@ Refer [📁 **Back up AWX using AWX Operator**](backup) and [📁 **Restore AWX
- [📝Deploy older version of AWX Operator](tips/deploy-older-operator.md) - [📝Deploy older version of AWX Operator](tips/deploy-older-operator.md)
- [📝Upgrade AWX Operator and AWX](tips/upgrade-operator.md) - [📝Upgrade AWX Operator and AWX](tips/upgrade-operator.md)
- [📝Workaround for the rate limit on Docker Hub](tips/dockerhub-rate-limit.md) - [📝Workaround for the rate limit on Docker Hub](tips/dockerhub-rate-limit.md)
- [📝Version Mapping between AWX Operator and AWX](tips/version-mapping.md) - [📝Version Mapping for AWX Operator and AWX](tips/version-mapping.md)
- [📝Use Kerberos authentication to connect to Windows hosts](tips/use-kerberos.md) - [📝Use Kerberos authentication to connect to Windows hosts](tips/use-kerberos.md)
- [📝Use Helm or Operator Lifecycle Manager to manage AWX Operator and AWX](tips/alternative-methods.md) - [📝Use Helm or Operator Lifecycle Manager to manage AWX Operator and AWX](tips/alternative-methods.md)
- [📝Troubleshooting Guide](tips/troubleshooting.md) - [📝Troubleshooting Guide](tips/troubleshooting.md)

View file

@ -10,7 +10,7 @@
- [📝Deploy older version of AWX Operator](deploy-older-operator.md) - [📝Deploy older version of AWX Operator](deploy-older-operator.md)
- [📝Upgrade AWX Operator and AWX](upgrade-operator.md) - [📝Upgrade AWX Operator and AWX](upgrade-operator.md)
- [📝Workaround for the rate limit on Docker Hub](dockerhub-rate-limit.md) - [📝Workaround for the rate limit on Docker Hub](dockerhub-rate-limit.md)
- [📝Version Mapping between AWX Operator and AWX](version-mapping.md) - [📝Version Mapping for AWX Operator and AWX](version-mapping.md)
- [📝Use Kerberos authentication to connect to Windows hosts](use-kerberos.md) - [📝Use Kerberos authentication to connect to Windows hosts](use-kerberos.md)
- [📝Use Helm or Operator Lifecycle Manager to manage AWX Operator and AWX](alternative-methods.md) - [📝Use Helm or Operator Lifecycle Manager to manage AWX Operator and AWX](alternative-methods.md)
- [📝Troubleshooting Guide](troubleshooting.md) - [📝Troubleshooting Guide](troubleshooting.md)

View file

@ -7,7 +7,7 @@ This guide provides the procedure for the following three types of upgrading AWX
- Upgrade from `0.13.0` (e.g. from `0.13.0` to `0.14.0`) - Upgrade from `0.13.0` (e.g. from `0.13.0` to `0.14.0`)
- Upgrade from `0.12.0` or earlier (e.g. from `0.12.0` to `0.13.0`) - Upgrade from `0.12.0` or earlier (e.g. from `0.12.0` to `0.13.0`)
Note that once you upgrade AWX Operator, your AWX will also be upgraded automatically to the version bundled with the upgraded AWX Operator as shown in [📝Version Mapping between AWX Operator and AWX](version-mapping.md). Note that once you upgrade AWX Operator, your AWX will also be upgraded automatically to the version bundled with the upgraded AWX Operator as shown in [📝Version Mapping for AWX Operator and AWX](version-mapping.md).
[There is `image_version` parameter for AWX resource to change which image will be used](https://github.com/ansible/awx-operator#deploying-a-specific-version-of-awx), but it appears that using a version of AWX other than the one bundled with the AWX Operator [is currently not supported](https://github.com/ansible/awx-operator#deploying-a-specific-version-of-awx). Conversely, if you want to upgrade AWX, you need to plan to upgrade AWX Operator first. [There is `image_version` parameter for AWX resource to change which image will be used](https://github.com/ansible/awx-operator#deploying-a-specific-version-of-awx), but it appears that using a version of AWX other than the one bundled with the AWX Operator [is currently not supported](https://github.com/ansible/awx-operator#deploying-a-specific-version-of-awx). Conversely, if you want to upgrade AWX, you need to plan to upgrade AWX Operator first.

View file

@ -1,10 +1,10 @@
<!-- omit in toc --> <!-- omit in toc -->
# Version Mapping between AWX Operator and AWX # Version Mapping for AWX Operator and AWX
- [Default version mapping between AWX Operator and AWX](#default-version-mapping-between-awx-operator-and-awx) - [Default version mapping for AWX Operator and AWX](#default-version-mapping-for-awx-operator-and-awx)
- [Appendix: Gather bundled AWX version from AWX Operator](#appendix-gather-bundled-awx-version-from-awx-operator) - [Appendix: Gather bundled AWX version from AWX Operator](#appendix-gather-bundled-awx-version-from-awx-operator)
## Default version mapping between AWX Operator and AWX ## Default version mapping for AWX Operator and AWX
The table below maps the AWX Operator versions and bundled AWX versions. The table below maps the AWX Operator versions and bundled AWX versions.