From e8b212f5ccdd2b4718755ea3dcffb9fbd75de514 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Robert=20Sch=C3=A4fer?= <git@roschaefer.de>
Date: Fri, 1 Feb 2019 01:08:19 +0100
Subject: [PATCH] Backend is accessible only from internal network

I think this is better. For development it might be interesting to have
access to the backend but I think one should do development with
docker-compose not minikube and such.
---
 README.md            | 3 +--
 services/backend.yml | 2 --
 services/neo4j.yml   | 2 --
 3 files changed, 1 insertion(+), 6 deletions(-)

diff --git a/README.md b/README.md
index 1c9212c07..1fbabb948 100644
--- a/README.md
+++ b/README.md
@@ -77,8 +77,7 @@ $ kubectl apply -f services/
 ## Access the services
 
 ```shell
-$ minikube service nitro-backend --namespace=staging
-$ minikube service nitro-web     --namespace=staging
+$ minikube service nitro-web --namespace=staging
 ```
 
 
diff --git a/services/backend.yml b/services/backend.yml
index 1654f884a..39cfca63a 100644
--- a/services/backend.yml
+++ b/services/backend.yml
@@ -12,5 +12,3 @@ spec:
       targetPort: 4000
   selector:
     workload.user.cattle.io/workloadselector: deployment-staging-backend
-  type: LoadBalancer
-  externalTrafficPolicy: Cluster
diff --git a/services/neo4j.yml b/services/neo4j.yml
index 65b7785b6..4ff0953a7 100644
--- a/services/neo4j.yml
+++ b/services/neo4j.yml
@@ -15,5 +15,3 @@ spec:
     targetPort: 7474
   selector:
     workload.user.cattle.io/workloadselector: deployment-staging-neo4j
-  type: ClusterIP
-