diff --git a/readme.md b/readme.md index f4daeca..023c459 100755 --- a/readme.md +++ b/readme.md @@ -96,22 +96,30 @@ http://192.168.99.100:30000/#!/overview?namespace=default We can also validate the status by using the commandline. Run the following command: ``` -kubectl get svc +kubectl get service ``` A table should show up with the following conent: - NAME | TYPE | CLUSTER-IP | EXTERNAL-IP | PORT(S) | AGE ---------|---------------|-----------------|----------------|------------|---------- -kubernetes | ClusterIP | 10.0.0.1 | | 443/TCP | 27d -laravel-api | LoadBalancer | 10.0.0.11 | | 80:32676/TCP | 4m +hello-minikube | NodePort | 10.98.64.133 | | 8080:30271/TCP | 2d +kubernetes | ClusterIP | 10.96.0.1 | | 443/TCP | 2d +laravel-project | NodePort | 10.105.178.73 | | 80:32469/TCP | 10m +nginx-http | ClusterIP | 10.100.126.245 | | 80/TCP | 20h +The laravel project should be listed here between the different other images. -The laravel project should be listed here between the different other images. Use the port name and open the browser to validate if the image is working accordingly: +You can also use the following command to get an detailed overview of the laravel service: ``` -http://192.168.99.100:32676/ +curl $(minikube service laravel-project --url) +``` + +Use the port name and open the browser to validate if the image is working accordingly: + +``` +http://192.168.99.100:32469/ ``` In case you want to debug, you can use the following command to see the events generated by Kubernetes: