Update "Deploying PHP Guestbook application with MongoDB" Tutorial to fix the following issues:
* #26765 - Ordered lists with wrong indexes * The wrong output of "kubectl get service frontend" on LoadBalancer Service Type example. * Fixing format Signed-off-by: Jailton Lopes <jailton@gmail.com>
This commit is contained in:
@@ -49,14 +49,15 @@ The manifest file, included below, specifies a Deployment controller that runs a
|
|||||||
1. Launch a terminal window in the directory you downloaded the manifest files.
|
1. Launch a terminal window in the directory you downloaded the manifest files.
|
||||||
1. Apply the MongoDB Deployment from the `mongo-deployment.yaml` file:
|
1. Apply the MongoDB Deployment from the `mongo-deployment.yaml` file:
|
||||||
|
|
||||||
```shell
|
|
||||||
kubectl apply -f https://k8s.io/examples/application/guestbook/mongo-deployment.yaml
|
|
||||||
```
|
|
||||||
<!---
|
<!---
|
||||||
for local testing of the content via relative file path
|
for local testing of the content via relative file path
|
||||||
kubectl apply -f ./content/en/examples/application/guestbook/mongo-deployment.yaml
|
kubectl apply -f ./content/en/examples/application/guestbook/mongo-deployment.yaml
|
||||||
-->
|
-->
|
||||||
|
|
||||||
|
```shell
|
||||||
|
kubectl apply -f https://k8s.io/examples/application/guestbook/mongo-deployment.yaml
|
||||||
|
```
|
||||||
|
|
||||||
1. Query the list of Pods to verify that the MongoDB Pod is running:
|
1. Query the list of Pods to verify that the MongoDB Pod is running:
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
@@ -84,15 +85,15 @@ The guestbook application needs to communicate to the MongoDB to write its data.
|
|||||||
|
|
||||||
1. Apply the MongoDB Service from the following `mongo-service.yaml` file:
|
1. Apply the MongoDB Service from the following `mongo-service.yaml` file:
|
||||||
|
|
||||||
```shell
|
|
||||||
kubectl apply -f https://k8s.io/examples/application/guestbook/mongo-service.yaml
|
|
||||||
```
|
|
||||||
|
|
||||||
<!---
|
<!---
|
||||||
for local testing of the content via relative file path
|
for local testing of the content via relative file path
|
||||||
kubectl apply -f ./content/en/examples/application/guestbook/mongo-service.yaml
|
kubectl apply -f ./content/en/examples/application/guestbook/mongo-service.yaml
|
||||||
-->
|
-->
|
||||||
|
|
||||||
|
```shell
|
||||||
|
kubectl apply -f https://k8s.io/examples/application/guestbook/mongo-service.yaml
|
||||||
|
```
|
||||||
|
|
||||||
1. Query the list of Services to verify that the MongoDB Service is running:
|
1. Query the list of Services to verify that the MongoDB Service is running:
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
@@ -122,15 +123,15 @@ The guestbook application has a web frontend serving the HTTP requests written i
|
|||||||
|
|
||||||
1. Apply the frontend Deployment from the `frontend-deployment.yaml` file:
|
1. Apply the frontend Deployment from the `frontend-deployment.yaml` file:
|
||||||
|
|
||||||
```shell
|
|
||||||
kubectl apply -f https://k8s.io/examples/application/guestbook/frontend-deployment.yaml
|
|
||||||
```
|
|
||||||
|
|
||||||
<!---
|
<!---
|
||||||
for local testing of the content via relative file path
|
for local testing of the content via relative file path
|
||||||
kubectl apply -f ./content/en/examples/application/guestbook/frontend-deployment.yaml
|
kubectl apply -f ./content/en/examples/application/guestbook/frontend-deployment.yaml
|
||||||
-->
|
-->
|
||||||
|
|
||||||
|
```shell
|
||||||
|
kubectl apply -f https://k8s.io/examples/application/guestbook/frontend-deployment.yaml
|
||||||
|
```
|
||||||
|
|
||||||
1. Query the list of Pods to verify that the three frontend replicas are running:
|
1. Query the list of Pods to verify that the three frontend replicas are running:
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
@@ -160,15 +161,15 @@ Some cloud providers, like Google Compute Engine or Google Kubernetes Engine, su
|
|||||||
|
|
||||||
1. Apply the frontend Service from the `frontend-service.yaml` file:
|
1. Apply the frontend Service from the `frontend-service.yaml` file:
|
||||||
|
|
||||||
```shell
|
|
||||||
kubectl apply -f https://k8s.io/examples/application/guestbook/frontend-service.yaml
|
|
||||||
```
|
|
||||||
|
|
||||||
<!---
|
<!---
|
||||||
for local testing of the content via relative file path
|
for local testing of the content via relative file path
|
||||||
kubectl apply -f ./content/en/examples/application/guestbook/frontend-service.yaml
|
kubectl apply -f ./content/en/examples/application/guestbook/frontend-service.yaml
|
||||||
-->
|
-->
|
||||||
|
|
||||||
|
```shell
|
||||||
|
kubectl apply -f https://k8s.io/examples/application/guestbook/frontend-service.yaml
|
||||||
|
```
|
||||||
|
|
||||||
1. Query the list of Services to verify that the frontend Service is running:
|
1. Query the list of Services to verify that the frontend Service is running:
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
@@ -215,7 +216,7 @@ If you deployed the `frontend-service.yaml` manifest with type: `LoadBalancer` y
|
|||||||
|
|
||||||
```
|
```
|
||||||
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
|
||||||
frontend ClusterIP 10.51.242.136 109.197.92.229 80:32372/TCP 1m
|
frontend LoadBalancer 10.51.242.136 109.197.92.229 80:32372/TCP 1m
|
||||||
```
|
```
|
||||||
|
|
||||||
1. Copy the external IP address, and load the page in your browser to view your guestbook.
|
1. Copy the external IP address, and load the page in your browser to view your guestbook.
|
||||||
|
|||||||
Reference in New Issue
Block a user