-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Refactor of containers #189
Comments
ansible-container still lacks a lot of the features that we would need to deploy our current pod specification so this would be heavily blocked on that. |
You've thrown down the gauntlet, sir! I suspect you're correct, and there may yet be a feature or two missing. I'll poke at it this week, and see if I can make some progress. We do have support for multi-container pods, and secrets. We are missing config maps, however. Need to figure out where that fits in our container.yml. Will work in totally separate repo, and see if we can create a proof of concept. It'll be a good exercise for Ansible Container. --Chris |
would be nice with a docker_swarm_service support aswell, is it underway for docker_container? |
It looks like a most of the work has already been finished in this unofficial AWX Container project. I don't know how compatible it's BSD license is with AWX's Apache license and it could be possible to merge in and continue this work officially. At the very least, this provides an outline of how AWX should look and behave when built and deployed by Ansible Container. |
That's one spin on it. Still want to do it from our side, and figure out how to properly handle config maps. |
is this issue still needed now that ansible-container is no more? |
I think this is not going to be done as specified here. |
Adjust spacing for add/edit org form
ISSUE TYPE
COMPONENT NAME
SUMMARY
Refactoring of containers / build to ansible-container and have content published in Galaxy.
The text was updated successfully, but these errors were encountered: