Skip to content

Commit

Permalink
Aligning the liqo demo namespace with the one used in the documentation
Browse files Browse the repository at this point in the history
  • Loading branch information
frisso authored and adamjensenbot committed Dec 10, 2020
1 parent 627c45c commit fbe66f7
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,20 +60,20 @@ kubectl get nodes -o wide
Let's use those resources. Deploy the [Google microservice Shop](https://github.com/liqotech/microservices-demo/blob/master/release/kubernetes-manifests.yaml) application via:

```bash
kubectl create namespace demo-liqo
kubectl label namespace demo-liqo liqo.io/enabled=true
kubectl apply -f https://get.liqo.io/app.yaml -n demo-liqo
kubectl create namespace liqo-demo
kubectl label namespace liqo-demo liqo.io/enabled=true
kubectl apply -f https://get.liqo.io/app.yaml -n liqo-demo
```

You can observe that:

* Your application is correctly working by exposing the application frontend port and later connecting with a browser to [localhost:8000](localhost:8000). To expose the pod port:
```bash
kubectl port-forward -n demo-liqo service/frontend 8080:80
kubectl port-forward -n liqo-demo service/frontend 8080:80
```
* Your application is transparently deployed across two different clusters:
```bash
kubectl get pods -n demo-liqo -o wide
kubectl get pods -n liqo-demo -o wide
```

To get more information about how to install Liqo in your own clusters and configure it, you can check out the [Liqo Documentation](https://doc.liqo.io/user/).
Expand Down

0 comments on commit fbe66f7

Please sign in to comment.