diff --git a/docs/installation/kubernetes/_category_.json b/docs/installation/kubernetes/_category_.json
new file mode 100644
index 0000000..05c9c1b
--- /dev/null
+++ b/docs/installation/kubernetes/_category_.json
@@ -0,0 +1,7 @@
+{
+  "label": "Kubernetes",
+  "position": 4,
+  "link": {
+    "type": "generated-index"
+  }
+}
diff --git a/docs/installation/kubernetes/helm_chart.md b/docs/installation/kubernetes/helm_chart.md
new file mode 100644
index 0000000..b056d51
--- /dev/null
+++ b/docs/installation/kubernetes/helm_chart.md
@@ -0,0 +1,111 @@
+---
+sidebar_position: 1
+---
+
+# Helm Chart
+Thanks to [Chris-Greaves](https://github.com/Chris-Greaves) for the amazing work.
+
+## Basic usage
+
+**Add and check the repo**
+```bash
+helm repo add planka http://plankanban.github.io/planka
+helm search repo planka
+```
+
+**Generate *SECRETKEY* and install Planka**
+```bash
+export SECRETKEY=$(openssl rand -hex 64)
+helm install planka . --set secretkey=$SECRETKEY  \
+--set admin_email="demo@demo.demo"  \
+--set admin_password="demo"  \
+--set admin_name="Demo Demo" \
+--set admin_username="demo"
+```
+
+> **NOTE:** The command `openssl rand -hex 64` is needed to create a random hexadecimal key for planka. On Windows you can use Git Bash to run that command.
+
+**To access Planka you can port forward using the following command:**
+
+```bash
+kubectl port-forward $POD_NAME 3000:1337
+```
+
+### Accessing Externally
+
+**To access Planka externally you can use the following configuration**
+```bash
+# HTTP only
+helm install planka . --set secretkey=$SECRETKEY \
+--set admin_email="demo@demo.demo"  \
+--set admin_password="demo"  \
+--set admin_name="Demo Demo" \
+--set admin_username="demo"
+--set ingress.enabled=true \
+--set ingress.hosts[0].host=planka.example.dev \
+
+# HTTPS
+helm install planka . --set secretkey=$SECRETKEY \
+--set admin_email="demo@demo.demo"  \
+--set admin_password="demo"  \
+--set admin_name="Demo Demo" \
+--set admin_username="demo"
+--set ingress.enabled=true \
+--set ingress.hosts[0].host=planka.example.dev \
+--set ingress.tls[0].secretName=planka-tls \
+--set ingress.tls[0].hosts[0]=planka.example.dev \
+```
+
+**The recommended way is to create a ``values.yaml`` file**
+```yaml
+secretkey: "<InsertSecretKey>"
+# The admin section needs to be present for new instances of Planka, after the first start you can remove the lines starting with admin_. If you want the admin user to be unchangeable admin_email: has to stay
+# After changing the config you have to run ```helm upgrade  planka . -f values.yaml```
+
+# Admin user
+admin_email: "demo@demo.demo" # Do not remove if you want to prevent this user from being edited/deleted
+admin_password: "demo"
+admin_name: "Demo Demo"
+admin_username: "demo"
+# Admin user
+
+ingress:
+  enabled: true
+  hosts:
+    - host: planka.example.dev
+      paths:
+        - path: /
+          pathType: ImplementationSpecific
+
+# Needed for HTTPS
+  tls:
+   - secretName: planka-tls # existing TLS secret in k8s
+     hosts:
+       - planka.example.dev
+```
+
+```bash
+helm install planka planka/planka -f values.yaml
+```
+### Access Planka
+Now you can browse to **http://YOUR_DOMAIN_NAME:YOUR_PORT** and login as **YOUR_ADMIN_EMAIL** with password **YOUR_ADMIN_PASSWORD**
+
+
+
+### Things to consider if production hosting
+
+If you want to host Planka for more than just playing around with, you might want to do the following things:
+
+- Create a `values.yaml` with your config, as this will make applying upgrades much easier in the future.
+- Create your `secretkey` once and store it either in a secure vault, or in your `values.yaml` file so it will be the same for upgrading in the future.
+- Specify a password for `postgresql.auth.password` as there have been issues with the postgresql chart generating new passwords locking you out of the data you've already stored. (see [this issue](https://github.com/bitnami/charts/issues/2061))
+
+Any questions or concerns, [raise an issue](https://github.com/Chris-Greaves/planka-helm-chart/issues/new).
+
+### Issues
+
+By using the Bitnami chart for PostgreSQL, there is an issue where once deployed, if trying to use a different password then it will be ignored as the Persistant Volume (PV) will already exist with the previous password. See warning from Bitnami below:
+
+> **Warning!** Setting a password will be ignored on new installation in the case when previous Posgresql release was deleted through the helm command. In that case, old PVC will have an old password, and setting it through helm won't take effect. Deleting persistent volumes (PVs) will solve the issue. Refer to [issue 2061](https://github.com/bitnami/charts/issues/2061) for more details
+
+If you want to fully uninstall this chart including the data, follow [these steps](https://github.com/bitnami/charts/blob/main/bitnami/postgresql/README.md#uninstalling-the-chart) from the Bitnami Chart's docs.