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.
This commit is contained in:
Robert Schäfer 2019-02-01 01:08:19 +01:00
parent 7b981c06d0
commit e8b212f5cc
3 changed files with 1 additions and 6 deletions

View File

@ -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
```

View File

@ -12,5 +12,3 @@ spec:
targetPort: 4000
selector:
workload.user.cattle.io/workloadselector: deployment-staging-backend
type: LoadBalancer
externalTrafficPolicy: Cluster

View File

@ -15,5 +15,3 @@ spec:
targetPort: 7474
selector:
workload.user.cattle.io/workloadselector: deployment-staging-neo4j
type: ClusterIP