playbook

[djdanielsson]

so this is just one playbook and it runs but looks like there is an issue with the DB not starting, I didn't verify if my other code brought everything up either so I might go back and double check that to see if it also has the same issue. But I thought I would show you what I was thinking and if you thought it was simple enough to put here or if it needed it's own repo. It isn't perfect, I had regex issues and gave up for now and put the exact number of spaces to make it work. there are a few other things that probably needs tweaking and improving as well.

[djdanielsson]

ok fixed the postgres issue, I had to change the permissions on the directories, not sure why but when I checked the pods log it said permission denied so I upped them to 755 and it worked

[djdanielsson]

I also hit an issue with the galaxy operator and it was saying 'patchesStrategicMerge is deprecated update to patches' so I PR'ed that change which is why I am changing the resource ref to main which now has that change.

[djdanielsson]

I think this is working and is simpler solution and automates closely to how your instructions are laid out. #334

[kurokobo]

@djdanielsson Thanks for sending PR.

I have not tested it, but have briefly looked at the contents. Sorry to say this, but there would be a significant number of comments to review this PR, that would almost have to be reworked. Mainly, I intend to correct the following points, but I don't have enough time right now to make detailed review comments:

• Keep kustomization.yaml for galaxy untouched
• Move everything to the ansible directory
• Split the playbook into multiple task files and import it
• Add inventory file and ansible.cfg
• Manage variables in inventory file
• Add tasks to confirm that the deployment was successful
• Add documentation

Once I add a playbook, as long as I maintain this repository, I, not you, will be responsible for its maintenance, answering questions about how to use the playbook, helping to troubleshoot when it does not work, etc. Thus, I will be spending a lot of time and effort for this one playbook in the long run.

For this reason, I want it to be my style of playbook, even if it goes against your style. Even if this PR were merged, it would most likely be reworked by myself. So if you want this playbook to stay the same, pleaes continue with your own repository.

I really appreciate your quick work and hope you understand my situation and concerns.

[djdanielsson]

so the galaxy change is required until they do a new release because with the current config the kuberneties.core module will not deploy it due to using depreciated syntax which I put in a PR and has been merged into main. as for all the other stuff I understand wanting it to be your own style which makes things way easier to maintain, I can either close the PR or if you want me to leave it as a draft so you can copy some of the tasks to maybe save you some effort I am fine with either way.

[kurokobo]

https://github.com/kurokobo/awx-on-k3s/issues/334#issuecomment-2142141569