Merge pull request #21 from shazChaudhry/6.4.3

Upgraded to 6.4.3

README.md

@@ -49,7 +49,7 @@ SSH in to the master node of the Docker Swarm cluster allocated to running Elast
   * `cd docker-elastic`
 
 * Deploy Elastic stack by running the following commands:
-  * `export ELASTIC_VERSION=6.4.0`
+  * `export ELASTIC_VERSION=6.4.3`
   * `docker network create --driver overlay elastic`
   * `docker stack deploy --compose-file docker-compose.yml elastic` _(This will deploy a reverse proxy, logstash, Kibana and 2x Elasticsearch instances in Master / data nodes configuration. Please note that Elasticsearch is configured to start as a global service which means data nodes will be scalled out automatically as soon as new nodes are added to the docker swarm cluster. Here is an explaination on various Elasticsearch cluster nodes: https://discuss.elastic.co/t/node-types-in-an-elasticsearch-cluster/25488)_
 * Check status of the stack services by running the following commands:
@@ -62,7 +62,7 @@ SSH in to the master node of the Docker Swarm cluster allocated to running Elast
 SSH in to the master node of the Docker Swarm cluster allocated to running containerized custom applicatins and beats. Clone this repo and change directory as per the instructions in the previous section
 
 Execute the following commands to deploy filebeat and metricbeat:
-  * `export ELASTIC_VERSION=6.4.0`
+  * `export ELASTIC_VERSION=6.4.3`
   * `docker network create --driver overlay elastic`
   * Edit "filebeat-docker-compose.yml" file. Change environment variables for Kibana and Elasticseaerch hosts
   * `docker stack deploy --compose-file filebeat-docker-compose.yml filebeat`  _(Filebeat starts as a global service on all docker swarm nodes. It is only configured to picks up container logs for all services at '`/var/lib/docker/containers/*/*.log`' (container stdout and stderr logs) and forward thtem to Elasticsearch. These logs will then be available under filebeat index in Kibana. You will need to add additional configurations for other log locations. You may wish to read [Docker Reference Architecture: Docker Logging Design and Best Practices](https://success.docker.com/article/docker-reference-architecture-docker-logging-design-and-best-practices))_

deployStack.sh

@@ -1,4 +1,4 @@
 #!/bin/bash
 
 docker network create --driver overlay elastic
-ELASTIC_VERSION=6.3.2 docker stack deploy -c docker-compose.yml elastic
+ELASTIC_VERSION=6.4.3 docker stack deploy -c docker-compose.yml elastic

docker-compose.yml

@@ -34,7 +34,7 @@ services:
       - BIND_PORTS=9200
 
   elasticsearch:
-    image: docker.elastic.co/elasticsearch/elasticsearch:${ELASTIC_VERSION:-6.3.2}
+    image: docker.elastic.co/elasticsearch/elasticsearch:${ELASTIC_VERSION:-6.4.3}
     # https://github.com/docker/swarmkit/issues/1951
     hostname: "{{.Node.Hostname}}-elasticsearch"
     environment:
@@ -62,7 +62,7 @@ services:
         - com.df.srcPort=9200
 
   logstash:
-    image: docker.elastic.co/logstash/logstash:${ELASTIC_VERSION:-6.3.2}
+    image: docker.elastic.co/logstash/logstash:${ELASTIC_VERSION:-6.4.3}
     hostname: "{{.Node.Hostname}}-logstash"
     environment:
       - XPACK_MONITORING_ELASTICSEARCH_URL=http://elasticsearch:9200
@@ -77,7 +77,7 @@ services:
         target: /usr/share/logstash/pipeline/logstash.conf
 
   kibana:
-    image: docker.elastic.co/kibana/kibana:${ELASTIC_VERSION:-6.3.2}
+    image: docker.elastic.co/kibana/kibana:${ELASTIC_VERSION:-6.4.3}
     hostname: "{{.Node.Hostname}}-kibana"
     environment:
       - ELASTICSEARCH_URL=http://elasticsearch:9200

filebeat-docker-compose.yml

@@ -5,7 +5,7 @@ services:
   # How to Tune Elastic Beats Performance: A Practical Example with Batch Size, Worker Count, and More
   # https://www.elastic.co/blog/how-to-tune-elastic-beats-performance-a-practical-example-with-batch-size-worker-count-and-more?blade=tw&hulk=social
   filebeat:
-    image: docker.elastic.co/beats/filebeat:${ELASTIC_VERSION:-6.3.2}
+    image: docker.elastic.co/beats/filebeat:${ELASTIC_VERSION:-6.4.3}
     # https://github.com/docker/swarmkit/issues/1951
     hostname: "{{.Node.Hostname}}-filebeat"
     # Need to override user so we can access the log files, and docker.sock

metricbeat-docker-compose.yml

@@ -3,7 +3,7 @@ version: "3.6"
 services:
 
   metricbeat:
-    image: docker.elastic.co/beats/metricbeat:${ELASTIC_VERSION:-6.3.2}
+    image: docker.elastic.co/beats/metricbeat:${ELASTIC_VERSION:-6.4.3}
     # https://github.com/docker/swarmkit/issues/1951
     hostname: "{{.Node.Hostname}}-metricbeat"
     user: root

packetbeat-docker-compose.yml

@@ -3,7 +3,7 @@ version: "3.6"
 services:
 
   packetbeat:
-    image: docker.elastic.co/beats/packetbeat:${ELASTIC_VERSION:-6.3.2}
+    image: docker.elastic.co/beats/packetbeat:${ELASTIC_VERSION:-6.4.3}
     # https://github.com/docker/swarmkit/issues/1951
     hostname: "{{.Node.Hostname}}-packetbeat"
     user: root