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

fix: replace custom ee with 2.12-custom

Browse source
This commit is contained in:
kurokobo 2022-02-19 13:37:35 +09:00
parent 800627d9dd
commit e9e2e54b26
3 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
containergroup/README.md
View file

@ -132,7 +132,7 @@ NAME READY STATUS RESTARTS AGE
automation-job-50-qsjbp 1/1 Running 0 17s
```
The Pod has your own specification as defined above.
The Pod has your own specification as defined above. Note that the `image` in example output below has been overridden by the Execution Environment which defined in Job Template.
```bash
$ kubectl -n ee-demo get pod automation-job-50-qsjbp -o yaml
@ -146,7 +146,7 @@ metadata:
spec:
containers:
...
image: registry.example.com/ansible/ee:2.10-custom
image: registry.example.com/ansible/ee:2.12-custom
...
resources:
limits:

4
galaxy/README.md
View file

@ -547,8 +547,8 @@ Then simply `login`, `tag` and `push`.
```bash
docker login galaxy.example.com
docker tag registry.example.com/ansible/ee:2.10-custom galaxy.example.com/demo/ee:2.10-custom
docker push galaxy.example.com/demo/ee:2.10-custom
docker tag registry.example.com/ansible/ee:2.12-custom galaxy.example.com/demo/ee:2.12-custom
docker push galaxy.example.com/demo/ee:2.12-custom
```
## Use with AWX

2
runner/env/settings vendored
View file

@ -1,7 +1,7 @@
---
process_isolation: true
process_isolation_executable: docker
container_image: registry.example.com/ansible/ee:2.10-custom
container_image: registry.example.com/ansible/ee:2.12-custom
# Specify additional bind-mount points to an isolated Docker or Podman container.
# Note that this is UNDOCUMENTED option.