Releases: elastic/azure-marketplace
6.2.4
6.2.2
Features
- #168 (4784f63) Add support for Elasticsearch and Kibana 6.2.2
- #168 (4784f63) Add support for Elasticsearch and Kibana 5.6.8
- #168 (9034d87) Add support for Elasticsearch 2.4.6 and Kibana 4.6.6
Enhancements
- #168 (1fe8205) Allow Elasticsearch heap size to be specified as an input parameter
- #168 (0fce0d4) Enable bootstrap memory lock
Bug fixes
Deprecations
6.2.1
Elasticsearch and Kibana 6.0 on Azure
This release adds support for deploying Elasticsearch and Kibana 6.0 to Azure! the default Elasticsearch and Kibana version in this template version is 6.2.1
Features
-
#165 Add support for Elasticsearch and Kibana 6.x
Adds the 6.x versions of Elasticsearch and Kibana to the template.
A unique bootstrap password can be provided to the template to set the
bootstrap.password
in the elasticsearch keystore. If not supplied, a unique value is generated within the ARM template, using theuniqueString()
function seeded with the resourceGroup id, deployment name and securityAdminPassword.Add
securityLogstashPassword
parameter to use for thelogstash_system
built-in user account in Elasticsearch 5.2.0+.
Enhancements
-
#165 Add
nofail
to the default mount options as recommended in the docs -
#165 Remove sudo calls within the scripts. Must be run as root already and using sudo does not transfer environment variables.
-
#165 Increase retries to 60 to wait a total of 5 minutes for an Elasticsearch node to come up
-
#165 Comment out conf-enabled include in monit configuration to suppress the superfluous warning written to stderr.
-
#165 Update 14.04 SKU for Elasticsearch 2.x
-
#165 Remove java8 apt package patching
oracle-java8-installer
apt package has now been updated to use 161 so use the package as is
Bug fixes
-
#165 Write log files to
/var/log/elasticsearch
.When unspecified, Elasticsearch 6.x will attempt to write log files to
/usr/share/elasticsearch/logs
which the elasticsearch user under which the service runs does not have access to do. -
#165 Always set
path.data
, even for master and client nodes.When unspecified, Elasticsearch 6.x will attempt to write data to
/usr/share/elasticsearch/data
which the elasticsearch user under which the service runs does not have access to do. -
#165 Check that the
elastic
user has been set up.This guards against an edge case where
securityBootstrapPassword
is the same assecurityAdminPassword
in 6.x, orsecurityAdminPassword
is the same as the default password in 5.x
Deprecations
-
#165 Remove
kibana4_server
generated password.Better alignment of the
es_kibana
user in 2.x and the built-inkibana
user in 5.x+.In 2.x, the es_kibana user is now assigned the
kibana4_server
role and thekibana4
role
is removed. Kibana will use thees_kibana
user credentials when interacting with Elasticsearch. -
#165 Disallow
Standard_A0
andStandard_A1
SKUs for Kibana VM. Both SKUs have insufficient RAM to run the Kibana optimizer process. -
#165 Remove EOL'ed 2.x versions
Remove the ability to deploy 2.x versions of Elasticsearch
and associated Kibana that are no longer supported by Elastic
5.6.6
Features
- #161 Add support for Elasticsearch and Kibana 5.6.6
Enhancements
- #160 Update Ubuntu SKUs to newer 14.04-LTS and 16.04-LTS releases
Bug fixes
- #159 Patch oracle-java8-installer apt package to download 8u162. The package attempts to download version 8u151 which is no longer listed on the Oracle Java downloads website.
5.6.5
Features
- #156 Add support for Elasticsearch and Kibana 5.6.5
Bug fixes
- #150 Run
sudo apt-get update
before installing any packages - #155 When selecting
gateway
as theloadBalancerType
, only set anonymous access when X-Pack plugins are installed. Thanks @ravitejag!
5.6.3
5.6.2
5.5.1
Features
- #140 Add support for Elasticsearch and Kibana 5.5.1
Enhancements
- #138 Remove hardcoded Azure regions list from the template; the
location
parameter will accept a value ofResourceGroup
to deploy resources to the same location as the resource group, or will accept any other string value. The template will rely on the Azure template validation to validate that this string value is a valid Azure region string e.g."australia southeast"
Bug Fixes
- #138 Fix a regression whereby resources were always being deployed to the same Azure region as the resource group. Now, resources will be deployed to the Azure region specified by the
location
parameter, defaulting to the same Azure region as the Resource Group (as before).