first run of kubeapps up/down

[ngtuna]

This is the first shape of $ kubeapps up/down.

• For testing purpose, kubeapps will read yaml files at $HOME/.kubeapps directory and deploy them to k8s. Thus, we can easily update/replace manifests.
• Support KUBECONFIG env (default to ~/.kube/config)
• Support --dry-run
• Support --namespace (default to api.NamespaceDefault)

Building

$ go build kubeapps -o main.go

Usage

$ kubeapps up
$ kubeapps down
// update manifests
$ kubeapps up

[ngtuna]

Please note to review commit each. There is a commit for vendorup that will destroy your browser.

[ngtuna]

I should merge it directly to have a good shape of the repo. We'll work later on further PRs.

[andresmgot]

Sorry, I didn't have the time to take a look to this. Two comments:

• I think we should maintain a list of stuff to install rather than trying to install indiscriminately the things present in the manifest folder. That way it would be easier to handle partial installations/uninstallation.
• My advice is to start writing test as soon as possible (as far as the implementation is validated). You should test the current behavior and the possible inputs/outputs. Plus the functions in root.go (mostly getHome, buildOutOfClusterConfig, and parseObjects) would benefit from unit tests.