kubernetes
/
examples
mirror of https://github.com/kubernetes/examples.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fixed paths in Elasticsearch production cluster README. (#110)

This commit is contained in:
Jay Taylor 2017-10-16 14:00:26 -07:00 committed by Ahmet Alp Balkan
parent 1fd5c2d6f9
commit 8f598113c8
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
staging/elasticsearch/production_cluster/README.md
View File

@ -19,27 +19,27 @@ This example uses [this pre-built image](https://github.com/pires/docker-elastic
## Deploy ## Deploy
``` ```
kubectl create -f examples/elasticsearch/production_cluster/service-account.yaml kubectl create -f staging/elasticsearch/production_cluster/service-account.yaml
kubectl create -f examples/elasticsearch/production_cluster/es-discovery-svc.yaml kubectl create -f staging/elasticsearch/production_cluster/es-discovery-svc.yaml
kubectl create -f examples/elasticsearch/production_cluster/es-svc.yaml kubectl create -f staging/elasticsearch/production_cluster/es-svc.yaml
kubectl create -f examples/elasticsearch/production_cluster/es-master-rc.yaml kubectl create -f staging/elasticsearch/production_cluster/es-master-rc.yaml
``` ```
Wait until `es-master` is provisioned, and Wait until `es-master` is provisioned, and
``` ```
kubectl create -f examples/elasticsearch/production_cluster/es-client-rc.yaml kubectl create -f staging/elasticsearch/production_cluster/es-client-rc.yaml
``` ```
Wait until `es-client` is provisioned, and Wait until `es-client` is provisioned, and
``` ```
kubectl create -f examples/elasticsearch/production_cluster/es-data-rc.yaml kubectl create -f staging/elasticsearch/production_cluster/es-data-rc.yaml
``` ```
Wait until `es-data` is provisioned. Wait until `es-data` is provisioned.
Now, I leave up to you how to validate the cluster, but a first step is to wait for containers to be in ```RUNNING``` state and check the Elasticsearch master logs: Now, I leave up to you how to validate the cluster, but a first step is to wait for containers to be in `RUNNING` state and check the Elasticsearch master logs:
``` ```
$ kubectl get pods $ kubectl get pods