(resolves 254 ) update getting started to work for post 0.6

[JazminElkan-Gonzalez]

Do not merge until after 0.6 is released

[JazminElkan-Gonzalez]

@jessesuen this is the docs update that we will need to push out once the new version of argo-cd is out and we are no longer relying on the install script.

[jessesuen]

Some improvements:

1. I'd like to remove the requirement that a user has to git clone our repo to install ArgoCD. Instead, we should have instructions like:

kubectl apply -f https://github.com/argoproj/argo-cd/blob/master/manifests/install.yaml

I think we should re-organize our manifests to the following structure:

manifests/
    install.yaml
    components/
        01a_application-crd.yaml
        01b_appproject-crd.yaml

Our makefile should autogenerate install.yaml during build by doing:
cat manifests/components/*.yaml > manifests/install.yaml

2. Let's also remove the 00_namespace.yaml and instruct the user to create their own namespace. This will make install.yaml completely portable. So the instructions then become:

kubectl create namespace argocd
kubectl apply -n argocd -f https://github.com/argoproj/argo-cd/blob/master/manifests/install.yaml

[bhack]

It could be nice to simplify the install with an official helm chart.

[JazminElkan-Gonzalez]

@jessesuen that totally makes sense, forgot this would be used outside of a developer context.
I have updated the PR appropriately.

for 2. is this just so the user can use different namespaces a bit easier? (I also made the change to match this, just wondering the benefits)

for the helm trade off, this feels like a larger change and I the use-case for these manifests is rather small so not sure if such a change is needed at this time. but I'll bring it up during standup today and we can review it.

[jessesuen]

2. is this just so the user can use different namespaces a bit easier? (I also made the change to match this, just wondering the benefits)

Correct. If we create the namespace for them, then they have no options.

It could be nice to simplify the install with an official helm chart.

I'm not opposed to this, but I think it can wait until we start pushing adoption.

[jessesuen]

These instructions still need to change to kubectl apply http://..../install.yaml

[JazminElkan-Gonzalez]

yeah, oops. updated @jessesuen

[jessesuen]

LGTM! Please don't merge until we cut a v0.6 release

[jessesuen]

This will also create key replicasets, deployments and services needed for ArgoCD

I think this statement is a little confusing: we don't explicitly create replicasets since they are implicitly created by our deployments. Also the fact that we create a deployment/service should also be obvious.

[jessesuen]

It looks like we're missing a step between step 2 and 3. We need instructions on how to login to ArgoCD using the pod name as the password.

Also, it seems like we should have a API to reset password. I'll file another issue for this. I think it's important for v0.6