diff --git a/README.md b/README.md
index 6ab975a07..572ecbc43 100644
--- a/README.md
+++ b/README.md
@@ -109,6 +109,21 @@ Sit back and relax and have a look into your kubernetes dashboard.
 Wait until all pods turn green and they don't show a warning
 `Waiting: ContainerCreating` anymore.
 
+### Setup Loadbalancer and Ingress
+
+Basically follow [this tutorial](https://www.digitalocean.com/community/tutorials/how-to-set-up-an-nginx-ingress-with-cert-manager-on-digitalocean-kubernetes).
+
+tl;dr:
+```sh
+$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/mandatory.yaml
+$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/provider/cloud-generic.yaml
+```
+And create an ingress service in namespace `staging`:
+```sh
+# you should change the domain name according to your needs
+$ kubectl apply -f staging/ingress.yaml
+```
+
 #### Legacy data migration
 
 This setup is completely optional and only required if you have data on a server
diff --git a/staging/ingress.yaml b/staging/ingress.yaml
new file mode 100644
index 000000000..fa23a9957
--- /dev/null
+++ b/staging/ingress.yaml
@@ -0,0 +1,13 @@
+apiVersion: extensions/v1beta1
+kind: Ingress
+metadata:
+  name: ingress
+  namespace: staging
+spec:
+  rules:
+  - host: master.nitro.human-connection.org
+    http:
+      paths:
+      - backend:
+          serviceName: nitro-web
+          servicePort: 3000
diff --git a/staging/service-web.yaml b/staging/service-web.yaml
index ad2b9678b..333983b72 100644
--- a/staging/service-web.yaml
+++ b/staging/service-web.yaml
@@ -12,5 +12,3 @@ spec:
       targetPort: 3000
   selector:
     workload.user.cattle.io/workloadselector: deployment-staging-web
-  type: LoadBalancer
-  externalTrafficPolicy: Cluster