[stable/spinnaker] Leverage Halyard for installation

stable/spinnaker/Chart.yaml

@@ -1,8 +1,8 @@
 apiVersion: v1
 description: Open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.
 name: spinnaker
-version: 0.5.0
-appVersion: 1.6.0
+version: 1.0.0
+appVersion: 1.8.0
 home: http://spinnaker.io/
 sources:
 - https://github.com/spinnaker
@@ -11,3 +11,5 @@ icon: https://pbs.twimg.com/profile_images/669205226994319362/O7OjwPrh_400x400.p
 maintainers:
 - name: viglesiasce
   email: [email protected]
+- name: lwander
+  email: [email protected]

stable/spinnaker/OWNERS

@@ -0,0 +1,6 @@
+approvers:
+- viglesiasce
+- lwander
+reviewers:
+- viglesiasce
+- lwander

stable/spinnaker/README.md

@@ -15,7 +15,7 @@ For more information on Spinnaker and its capabilities, see it's [documentation]
 To install the chart with the release name `my-release`:
 
 ```bash
-$ helm install --name my-release stable/spinnaker
+$ helm install --name my-release stable/spinnaker --timeout 600
 ```
 
 Note that this chart pulls in many different Docker images so can take a while to fully install. 
@@ -55,5 +55,38 @@ for Spinnaker. If you want to add arbitrary clusters need to do the following:
       contexts:
       # Names of contexts available in the uploaded kubeconfig
       - my-context
+      # This is the context from the list above that you would like
+      # to deploy Spinnaker itself to.
+      deploymentContext: my-context
     ```
 
+## Customizing your installation
+
+### Manual
+While the default installation is ready to handle your Kubernetes deployments, there are
+many different integrations that you can turn on with Spinnaker. In order to customize
+Spinnaker, you can use the [Halyard](https://www.spinnaker.io/reference/halyard/) command line `hal` 
+to edit the configuration and apply it to what has already been deployed.
+
+Halyard has an in-cluster daemon that stores your configuration. You can exec a shell in this pod to
+make and apply your changes. The Halyard daemon is configured with a persistent volume to ensure that
+your configuration data persists any node failures, reboots or upgrades.
+
+For example:
+
+```shell
+$ helm install -n cd stable/spinnaker
+$ kubectl exec -it cd-spinnaker-halyard-0 bash
+spinnaker@cd-spinnaker-halyard-0:/workdir$ hal version list
+```
+
+### Automated
+If you have known set of commands that you'd like to run after the base config steps or if
+you'd like to override some settings before the Spinnaker deployment is applied, you can enable
+the `halyard.additionalConfig.enabled` flag. You will need to create a config map that contains a key
+contianing the `hal` commands you'd like to run. You can set the key via the config map name via `halyard.additionalConfig.configMapName` and the key via `halyard.additionalConfig.configMapKey`. The `DAEMON_ENDPOINT` environment variable can be used in your custom commands to
+get a prepopulated URL that points to your Halyard daemon within the cluster. For example:
+
+```shell
+hal --daemon-endpoint $DAEMON_ENDPOINT config security authn oauth2 enable
+```