Skip to content

Commit ac384dc

Browse files
islinwbahmetb
authored andcommitted
Update README.md (#78)
fixed typos
1 parent 0616300 commit ac384dc

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

staging/storage/mysql-galera/README.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -30,14 +30,14 @@ Create the service and replication controller for the first node:
3030

3131
### Create services and controllers for the remaining nodes
3232

33-
Repeat the same previous steps for ```pxc-node2``` and ```pxc-node3```
33+
Repeat the same previous steps for ```pxc-node2``` and ```pxc-node3```.
3434

35-
When complete, you should be able connect with a MySQL client to the IP address
36-
service ```pxc-cluster``` to find a working cluster
35+
When completed, you should be able to connect with a MySQL client to the IP address
36+
service ```pxc-cluster``` to find a working cluster.
3737

3838
### An example of creating a cluster
3939

40-
Shown below are examples of Using ```kubectl``` from within the ```./examples/storage/mysql-galera``` directory, the status of the lauched replication controllers and services can be confirmed
40+
Shown below are examples of Using ```kubectl``` from within the ```./examples/storage/mysql-galera``` directory, the status of the lauched replication controllers and services can be confirmed:
4141

4242
```
4343
$ kubectl create -f examples/storage/mysql-galera/pxc-cluster-service.yaml
@@ -92,7 +92,7 @@ The cluster should be ready for use!
9292

9393
### Connecting to the cluster
9494

95-
Using the name of ```pxc-cluster``` service running interactively using ```kubernetes exec```, it is possible to connect to any of the pods using the mysql client on the pod's container to verify the cluster size, which should be ```3```. In this example below, pxc-node3 replication controller is chosen, and to find out the pod name, ```kubectl get pods``` and ```awk``` are employed:
95+
Using the name of ```pxc-cluster``` service running interactively using ```kubectl exec```, it is possible to connect to any of the pods using the mysql client on the pod's container to verify the cluster size, which should be ```3```. In this example below, pxc-node3 replication controller is chosen, and to find out the pod name, ```kubectl get pods``` and ```awk``` are employed:
9696

9797
```
9898
$ kubectl get pods|grep pxc-node3|awk '{ print $1 }'

0 commit comments

Comments
 (0)