why is navigator in a container instead of a package? #1928
VorlMaldor
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to understand why navigator was put into a container (EE) instead of just making it a package like everything else.
There are a lot of reasons to not use containers:
added complexity of the install and just the general complexity that comes with containers
having to export volumes for the EE to see your playbooks/inventories/etc etc
added complexity just talking to controller node to run plays
What made navigator inside an EE the way to go? Is it just an attempt to help "encourage" people to use containers more?
What can't be done with an RPM for navigator that required the container?
Beta Was this translation helpful? Give feedback.
All reactions