Stanislav Zaprudskiy
94d68bf382
With the previous approach, not all associated (mounted) CM/Secrets changes caused the Deployment to be rolled out, but also the Deployment could have been rolled out unnecessary during e.g. Ingress or Service changes (which do not require Pod restarts). Previously existing Pod removal (state: absent) was not complete as other pods continued to exist, but also is not needed with this commit change due to added Pods annotations. The added Deployment Pod annotations now cause the new ReplicaSet version to be rolled out, effectively causing replacement of the previously existing Pods in accordance with the deployment `strategy` (https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.25/#deploymentstrategy-v1-apps, `RollingUpdate`) whenever there is a change in the associated CMs or Secrets referenced in annotations. This implementation is quite standard and widely used for Helm workflows - https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments
AWX
This role builds and maintains an Ansible Tower instance inside of Kubernetes.
Requirements
TODO.
Role Variables
See defaults/main.yml for all the role variables that you can override.
TODO: add variable description table.
Dependencies
N/A
Example Playbook
- hosts: localhost
connection: local
roles:
- awx
License
MIT / BSD