Enable alternative tillerNamespace to be specified when deploying (#373)

deployment/monocular/README.md

@@ -53,6 +53,15 @@ The command removes all the Kubernetes components associated with the chart and
 
 See the [values](values.yaml) for the full list of configurable values.
 
+
+### Pointing to a different namespace
+
+If tiller is not running in default namespace `kube-system`, you can provide the correct namespace with the following:
+
+```console
+$ helm install monocular/monocular --set api.config.tillerNamespace=YOUR_NAMESPACE
+```
+
 ### Disabling Helm releases (deployment) management
 
 If you want to run Monocular without giving the option to install and manage charts in your cluster, similar to [KubeApps](https://kubeapps.com) you can configure `api.config.releasesEnabled`:

deployment/monocular/templates/NOTES.txt

@@ -24,4 +24,6 @@ Visit https://github.com/kubernetes-helm/monocular for more information.
 {{ if .Values.api.config.releasesEnabled -}}
 **IMPORTANT**: Releases are enabled, which will allow anybody with access to the running instance to create, list and delete any Helm release existing in your cluster.
 This feature is aimed for internal, behind the firewall deployments of Monocular, please plan accordingly. To disable this, re-install Monocular setting api.config.releasesEnabled=false.
-{{ end }}
+{{ end }}
+
+Monocular expects tiller-deploy to be found in namespace {{ .Values.api.config.tillerNamespace }}

deployment/monocular/values.yaml

@@ -49,6 +49,7 @@ api:
         - "x-xsrf-token"
     # Enable Helm deployment integration
     releasesEnabled: true
+    tillerNamespace: kube-system
     # Cache refresh interval in sec.
     cacheRefreshInterval: 3600
 ui: