6.2.3-r3 release

* Several improvements:
  * New Nami properties:
    * bindAddress: Useful to harden security on clusters.
    * isDedicatedNode: Whether the node should be configured as a dedicated node or not.
    * nodeType: Elasticserach node type when using dedicated nodes.
  * Remove unused property (enableRemoteConnection)
  * Improve 'Print Properties message'
This commit is contained in:
Bitnami Bot
2018-04-04 13:53:25 +00:00
parent eab4129b3c
commit 29f08eef14
3 changed files with 30 additions and 12 deletions

View File

@@ -3,21 +3,22 @@ LABEL maintainer "Bitnami <containers@bitnami.com>"
# Install required system packages and dependencies
RUN bitnami-pkg install java-1.8.161-0 --checksum eb289afc43eda33d5920294460dc256f6543318506ca5a540bba9073412cfd06
RUN bitnami-pkg unpack elasticsearch-6.2.3-1 --checksum 8d32c0eaf21df4ec1190b45a455faaa996ac32066a0b508cee23cc88f48a6461
RUN bitnami-pkg unpack elasticsearch-6.2.3-2 --checksum 203bf13485e98ff2db1dd20219f8447bca6c10dbb6754f4dcbf0fb582df60017
COPY rootfs /
ENV BITNAMI_APP_NAME="elasticsearch" \
BITNAMI_IMAGE_VERSION="6.2.3-r2" \
ELASTICSEARCH_CLIENT_NODE="" \
BITNAMI_IMAGE_VERSION="6.2.3-r3" \
ELASTICSEARCH_BIND_ADDRESS="" \
ELASTICSEARCH_CLUSTER_HOSTS="" \
ELASTICSEARCH_CLUSTER_NAME="elasticsearch-cluster" \
ELASTICSEARCH_HEAP_SIZE="1024m" \
ELASTICSEARCH_IS_DEDICATED_NODE="no" \
ELASTICSEARCH_NODE_NAME="" \
ELASTICSEARCH_NODE_PORT_NUMBER="9300" \
ELASTICSEARCH_NODE_TYPE="master" \
ELASTICSEARCH_PLUGINS="" \
ELASTICSEARCH_PORT_NUMBER="9200" \
ELASTICSEARCH_REMOTE_CONNECTION="true" \
PATH="/opt/bitnami/java/bin:/opt/bitnami/elasticsearch/bin:$PATH"
EXPOSE 9200 9300

View File

@@ -1,11 +1,12 @@
{
"bindAddress": "{{$global.env.ELASTICSEARCH_BIND_ADDRESS}}",
"clusterHosts": "{{$global.env.ELASTICSEARCH_CLUSTER_HOSTS}}",
"clusterName": "{{$global.env.ELASTICSEARCH_CLUSTER_NAME}}",
"enableRemoteConnection": "{{$global.env.ELASTICSEARCH_REMOTE_CONNECTION}}",
"isClientNode": "{{$global.env.ELASTICSEARCH_CLIENT_NODE}}",
"isDedicatedNode": "{{$global.env.ELASTICSEARCH_IS_DEDICATED_NODE}}",
"javaHeapSize": "{{$global.env.ELASTICSEARCH_HEAP_SIZE}}",
"nodeName": "{{$global.env.ELASTICSEARCH_NODE_NAME}}",
"nodePort": "{{$global.env.ELASTICSEARCH_NODE_PORT_NUMBER}}",
"nodeType": "{{$global.env.ELASTICSEARCH_NODE_TYPE}}",
"plugins": "{{$global.env.ELASTICSEARCH_PLUGINS}}",
"port": "{{$global.env.ELASTICSEARCH_PORT_NUMBER}}"
}

View File

@@ -168,24 +168,33 @@ elasticsearch:
Available variables:
- `ELASTICSEARCH_PLUGINS`: Comma, semi-colon or space separated list of plugins to install at initialization. No defaults
- `ELASTICSEARCH_CLUSTER_NAME`: The Elasticsearch Cluster Name. Default: **elasticsearch-cluster**
- `ELASTICSEARCH_CLUSTER_HOSTS`: List of elasticsearch hosts to set the cluster. Available separatos are ' ', ',' and ';'. No defaults.
- `ELASTICSEARCH_IS_DEDICATED_NODE`: Elasticsearch node to behave as a 'dedicated node'. Default: **no**
- `ELASTICSEARCH_NODE_TYPE`: Elasticsearch node type when behaving as a 'dedicated node'. Valid values: *master*, *data*, *coordinating* or *ingest*.
- `ELASTICSEARCH_NODE_NAME`: Elasticsearch node name. No defaults.
- `ELASTICSEARCH_BIND_ADDRESS`: Address/interface to bind by Elasticsearch. Default: **0.0.0.0**
- `ELASTICSEARCH_PORT_NUMBER`: Elasticsearch port. Default: **9200**
- `ELASTICSEARCH_NODE_PORT_NUMBER`: Elasticsearch Node to Node port. Default: **9300**
- `ELASTICSEARCH_CLUSTER_NAME`: The Elasticsearch Cluster Name. Default: **elasticsearch-cluster**
- `ELASTICSEARCH_CLUSTER_HOSTS`: List of elasticsearch hosts to set the cluster. Available separatos are ' ', ',' and ';' .No defaults.
- `ELASTICSEARCH_CLIENT_NODE`: Elasticsearch node to behave as a 'smart router' for Kibana app. Default: **false**
- `ELASTICSEARCH_NODE_NAME`: Elasticsearch node name. No defaults.
- `ELASTICSEARCH_PLUGINS`: Comma, semi-colon or space separated list of plugins to install at initialization. No defaults.
- `ELASTICSEARCH_HEAP_SIZE`: Memory used for the Xmx and Xms java heap values. Defaults to half of the host RAM.
## Setting up a cluster
A cluster can easily be setup with the Bitnami Elasticsearch Docker Image using the following environment variables
A cluster can easily be setup with the Bitnami Elasticsearch Docker Image using the following environment variables:
- `ELASTICSEARCH_CLUSTER_NAME`: The Elasticsearch Cluster Name. Default: **elasticsearch-cluster**
- `ELASTICSEARCH_CLUSTER_HOSTS`: List of elasticsearch hosts to set the cluster. Available separatos are ' ', ',' and ';' .No defaults.
- `ELASTICSEARCH_CLIENT_NODE`: Elasticsearch node to behave as a 'smart router' for Kibana app. Default: **false**
- `ELASTICSEARCH_NODE_NAME`: Elasticsearch node name. No defaults.
For larger cluster, you can setup 'dedicated nodes' using the following environment variables:
- `ELASTICSEARCH_IS_DEDICATED_NODE`: Elasticsearch node to behave as a 'dedicated node'. Default: **no**
- `ELASTICSEARCH_NODE_TYPE`: Elasticsearch node type when behaving as a 'dedicated node'. Valid values: *master*, *data*, *coordinating* or *ingest*.
Find more information about 'dedicated nodes' in the [official documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html).
### Step 1: Create a new network.
```bash
@@ -325,6 +334,13 @@ or using Docker Compose:
$ docker-compose start elasticsearch
```
# Notable Changes
## 6.2.3-r2 & 5.6.4-r6
- Elasticsearch container can be configured as a dedicated node with 4 different types: *master*, *data*, *coordinating* or *ingest*.
Previously it was only achievable by using a custom `elasticsearch_custom.yml` file. From now on, you can use the environment variables `ELASTICSEARCH_IS_DEDICATED_NODE` & `ELASTICSEARCH_NODE_TYPE` to configure it.
# Contributing
We'd love for you to contribute to this container. You can request new features by creating an [issue](https://github.com/bitnami/bitnami-docker-elasticsearch/issues), or submit a [pull request](https://github.com/bitnami/bitnami-docker-elasticsearch/pulls) with your contribution.