Merge pull request #6016 from pmint93/master

Add docs: running metabase on kubernetes

docs/operations-guide/running-metabase-on-kubernetes.md

+# Running Metabase on Kubernetes
+
+This guide will help you install Metabase on Kubernetes using [Metabase Helm chart](https://github.com/kubernetes/charts/tree/master/stable/metabase)
+
+### Prerequisites
+
+* Kubernetes 1.4+ with Beta APIs enabled
+
+* [Kubernetes Helm](https://github.com/kubernetes/helm) installed
+
+
+### Installing
+
+To install with the release name `my-release`:
+
+```bash
+$ helm install --name my-release stable/metabase
+```
+
+### Configuring
+
+By default, backend database (H2) is stored inside container, and will be lost after container restart.
+
+So we **highly recommended** to use MySQL or Postgres instead.
+
+Copy these [**default configuration**](https://github.com/kubernetes/charts/blob/master/stable/metabase/values.yaml) into a new file named `metabase-config.yaml`, then modify as your need.
+
+Deploy Metabase using your config file:
+
+```bash
+$ helm install --name my-release -f metabase-config.yaml stable/metabase
+```
+

docs/operations-guide/start.md

@@ -40,6 +40,9 @@ Community support only at this time, but we have reports of Metabase instances r
 #### [Running on Debian as a service](running-metabase-on-debian.md)
 Community support only at this time, but learn how to deploy Metabase as a service on Debian (and Debian-based) systems. Simple, guided, step-by-step approach that will work on any VPS.
 
+#### [Running on Kubernetes](running-metabase-on-kubernetes.md)
+Community Helm chart for running Metabase on Kubernetes
+
 # Upgrading Metabase
 
 Before you attempt to upgrade Metabase, you should make a backup of the application database just in case. While it is unlikely you will need to roll back, it will do wonders for your peace of mind.