expand/awx-on-k3s
1
0
Fork 0
mirror of https://github.com/Expand-sys/awx-on-k3s synced 2025-12-15 21:42:15 +11:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs: update guide inventory sync and proxy configuration

Browse source
This commit is contained in:
kurokobo 2024-03-06 00:53:42 +09:00
parent c5601b1b9f
commit 4e28ccab34
No known key found for this signature in database
GPG key ID: A6224377E5B0604E
2 changed files with 28 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
tips/trust-custom-ca.md
View file

@ -233,9 +233,7 @@ In this example, the value of the environment variable `REQUESTS_CA_BUNDLE` is s
### Method 1: Use Container Group
This method can be used for standard jobs, such as the case that some modules in your playbook require custom CA certificates.
Note that this method can't be used for accessing inventory sources since current AWX does not support specifying Container Group for inventory sync.
This method can be used for standard jobs, such as the case that some modules in your playbook require custom CA certificates. In addition, this method can also be used to access inventory sources.
#### Create Secret
@ -319,7 +317,9 @@ If you just want to place CA certificates somewhere on automation job pods and `
#### Specify Container Group
The Container Group can be specified as `Instance Groups` for the Job Template.
The Container Group can be specified as `Instance Groups` for the Job Template or Organization.
If you want to use this Container Group to access inventory sources, specify it as `Instance Groups` for the Inventory or Organization.
### Method 2: Mount host filesystem

24
tips/use-http-proxy.md
View file

@ -92,3 +92,27 @@ kubectl apply -k base
Now you need to wait some time until K3S has restarted all your pods.
After logging in you can navigate to `Settings` > `Jobs settings` in the AWX UI and find your proxy settings in the `Extra Environment Variables` block. But note that you will not be able to edit the setting via Web UI once the configuration has passed through AWX Operator. If you want to modify your configuration, use AWX Operator again.
> [!TIP]
> The proxy settings above don't work as expected for the specific use cases such as social authentication. If you are in these cases behind proxy, try adding proxy settings by AWX Operator in different way. This can't be configured and reviewed by AWX UI.
>
> ```yaml
> ...
> spec:
> ...
> task_extra_env: | 👈👈👈
> - name: HTTP_PROXY 👈👈👈
> value: http://proxy.example.com:3128 👈👈👈
> - name: HTTPS_PROXY 👈👈👈
> value: http://proxy.example.com:3128 👈👈👈
> - name: NO_PROXY 👈👈👈
> value: 127.0.0.1,localhost,.example.com 👈👈👈
>
> web_extra_env: | 👈👈👈
> - name: HTTP_PROXY 👈👈👈
> value: http://proxy.example.com:3128 👈👈👈
> - name: HTTPS_PROXY 👈👈👈
> value: http://proxy.example.com:3128 👈👈👈
> - name: NO_PROXY 👈👈👈
> value: 127.0.0.1,localhost,.example.com 👈👈👈
> ```