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

Makefile

@@ -41,7 +41,7 @@ IMAGE_PREFIX=${IMAGE_NAMESPACE}/
 endif
 
 .PHONY: all
-all: cli server-image controller-image repo-server-image argocd-util
+all: cli server-image controller-image repo-server-image argocd-util install-manifest
 
 .PHONY: protogen
 protogen:
@@ -78,10 +78,14 @@ cli-darwin: clean-debug
 argocd-util: clean-debug
 	CGO_ENABLED=0 go build -v -i -ldflags '${LDFLAGS} -extldflags "-static"' -o ${DIST_DIR}/argocd-util ./cmd/argocd-util
 
+.PHONY: install-manifest
+install-manifest: clean-debug
+	cat manifests/components/*.yaml > manifests/install.yaml
+
 .PHONY: server
 server: clean-debug
 	CGO_ENABLED=0 ${PACKR_CMD} build -v -i -ldflags '${LDFLAGS}' -o ${DIST_DIR}/argocd-server ./cmd/argocd-server
-
+	
 .PHONY: server-image
 server-image:
 	docker build --build-arg BINARY=argocd-server -t $(IMAGE_PREFIX)argocd-server:$(IMAGE_TAG) -f Dockerfile-argocd .

docs/getting_started.md

@@ -18,9 +18,11 @@ chmod +x /usr/local/bin/argocd
 
 ## 2. Install ArgoCD
 ```
-argocd install
+kubectl create namespace argocd
+kubectl apply -n argocd -f https://github.com/argoproj/argo-cd/blob/master/manifests/install.yaml
 ```
-This will create a new namespace, `argocd`, where ArgoCD services and application resources will live.
+This will create a new namespace, `argocd` where ArgoCD services and application resources will live.
+This will also create key replicasets, deployments and services needed for ArgoCD
 
 ## 3. Open access to ArgoCD API server
 
@@ -136,4 +138,4 @@ ArgoCD supports additional features such as SSO, WebHooks, RBAC. See the followi
 these up:
 * [Configuring SSO](sso.md)
 * [Configuring RBAC](rbac.md)
-* [Configuring WebHooks](webhook.md)
+* [Configuring WebHooks](webhook.md)

manifests/01a_application-crd.yaml → manifests/components/01a_application-crd.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: apiextensions.k8s.io/v1beta1
 kind: CustomResourceDefinition
 metadata:

manifests/01b_appproject-crd.yaml → manifests/components/01b_appproject-crd.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: apiextensions.k8s.io/v1beta1
 kind: CustomResourceDefinition
 metadata:

manifests/02a_argocd-cm.yaml → manifests/components/02a_argocd-cm.yaml

@@ -1,3 +1,4 @@
+---
 # NOTE: the values here are just a example and are not the values used during an install.
 apiVersion: v1
 kind: ConfigMap
@@ -6,4 +7,3 @@ metadata:
 data:
   # please see https://github.com/argoproj/argo-cd/blob/master/docs/sso.md#2-configure-argocd-for-sso 
   # for more details about how to setup data config needed for sso
-

manifests/02b_argocd-secret.yaml → manifests/components/02b_argocd-secret.yaml

@@ -1,3 +1,4 @@
+---
 # NOTE: the values in this secret are provided as working manifest example and are not the values
 # used during an install. New values will be generated as part of `argocd install`
 apiVersion: v1
@@ -11,4 +12,4 @@ type: Opaque
   # The following keys hold the shared secret for authenticating GitHub/GitLab/BitBucket webhook
   # events. To enable webhooks, configure one or more of the following keys with the shared git
   # provider webhook secret. The payload URL configured in the git provider should use the 
-  # /api/webhook endpoint of your ArgoCD instance (e.g. https://argocd.example.com/api/webhook)
+  # /api/webhook endpoint of your ArgoCD instance (e.g. https://argocd.example.com/api/webhook)

manifests/02c_argocd-rbac-cm.yaml → manifests/components/02c_argocd-rbac-cm.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: v1
 kind: ConfigMap
 metadata:

manifests/03a_application-controller-sa.yaml → manifests/components/03a_application-controller-sa.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: v1
 kind: ServiceAccount
 metadata:

manifests/03b_application-controller-role.yaml → manifests/components/03b_application-controller-role.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: Role
 metadata:

manifests/03c_application-controller-rolebinding.yaml → manifests/components/03c_application-controller-rolebinding.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: RoleBinding
 metadata:

manifests/03d_application-controller-deployment.yaml → manifests/components/03d_application-controller-deployment.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: apps/v1beta2
 kind: Deployment
 metadata:

manifests/04a_argocd-server-sa.yaml → manifests/components/04a_argocd-server-sa.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: v1
 kind: ServiceAccount
 metadata:

manifests/04b_argocd-server-role.yaml → manifests/components/04b_argocd-server-role.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: Role
 metadata:

manifests/04c_argocd-server-rolebinding.yaml → manifests/components/04c_argocd-server-rolebinding.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: RoleBinding
 metadata:

manifests/04d_argocd-server-deployment.yaml → manifests/components/04d_argocd-server-deployment.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: apps/v1beta2
 kind: Deployment
 metadata:

manifests/04e_argocd-server-service.yaml → manifests/components/04e_argocd-server-service.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: v1
 kind: Service
 metadata:

manifests/05a_argocd-repo-server-deployment.yaml → manifests/components/05a_argocd-repo-server-deployment.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: apps/v1beta2
 kind: Deployment
 metadata:

manifests/05b_argocd-repo-server-service.yaml → manifests/components/05b_argocd-repo-server-service.yaml

@@ -1,3 +1,4 @@
+---
 apiVersion: v1
 kind: Service
 metadata: