Skip to content
This repository has been archived by the owner on Jul 24, 2018. It is now read-only.

Confusing installation #187

Open
xeor opened this issue Jan 1, 2018 · 1 comment
Open

Confusing installation #187

xeor opened this issue Jan 1, 2018 · 1 comment
Assignees

Comments

@xeor
Copy link

xeor commented Jan 1, 2018

Is this a bug report or feature request?: feature request

Python Version (output of python --version): Python 3.6.3

Development or Deployment Environment?: osx against a remote k8s cluster

Release Tag or Master: master

Expected Behavior: not that much confusion, using armada

What Actually Happened: lot of confusion..

How to Reproduce the Issue (as minimally as possible):

Any Additional Comments:
It's not clear to me how armada should be installed and used. In the docs, there are instructions telling me to do a docker run -d ..., but there are not much docs about installing the cli itself. There is a guide for using it as a helm-plugin tho.. But is that the same?

So why isn't there a pip install armanda-helm or similar? And why do I need to run a docker container on the side? Do it need to run at the same place as tiller?

Basically, I think the install-docs are very unclear..
If the docker container-sidekick needs to be there because of many deps, why does it need to run daemonized?

@MarshM
Copy link
Contributor

MarshM commented Jan 8, 2018

Thanks for the feedback. We're working on reviewing and updating our docs, and will pull you in at a later date to help contribute to a patchset review in GerritHub.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants