You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I would like to accomplish in this epic is to take our Docker Static setup and 'Ansibilise' it. The final product should be a system of playbooks and scripts which allow static container deployment via AWX or command line.
OK - testing this on another aarch64 box using k3s. Noting that by default it doesn't work as non-root because exporting KUBECONFIG to be /etc/rancher/k3s/k3s.yaml is something that is not-world readable and gets reset on each restart. Also:
A simple make deploy doesn't work because the images being pulled (quay.io/ansible/awx-operator:x.y.z) appear to be x64 only, but they'll work under qemu emulation (Not ideal for production
Version 2.11.0 appears not to work - 2.10.0 deploys ok
kubectl logs was close to useless (but pointed me at the arch mismatch issue) kubectl describe is your friend for better status logs until you start the actual AWX deploy when kubectl logs -f is useful
I still need to figure out how to make /Vendor_Files into the appropriate container
Turning #3306 into an epic.
What I would like to accomplish in this epic is to take our Docker Static setup and 'Ansibilise' it. The final product should be a system of playbooks and scripts which allow static container deployment via AWX or command line.
We have https://github.com/adoptium/infrastructure/blob/master/ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/DockerStatic/tasks/main.yml, but it is monolithic. I want to create something more modular, in which a user can choose which containers to deploy, which to remove, as well as an update to date inventory file containing a list of running containers.
Objectives, not necessarily in order:
The text was updated successfully, but these errors were encountered: