5.4.0

Features

#122 Add support for Elasticsearch and Kibana 5.4.0. This brings Machine Learning beta to X-Pack 🤖

5.3.2

Features

#121 Add support for Elasticsearch and Kibana 5.3.2. Deprecate support for 5.3.1 (superseded patch version).

5.1.2

Features

• #120 Support for Elasticsearch and Kibana 5.3.1
• #119 Re-enable ingest role on master and data nodes. Dedicated master nodes can sometimes fail to startup because of local exporter settings for monitoring.

Bug fixes

• #119 Additional resiliency around failures in creating RAID 0 array

5.1.1

Misc

Update password.parameters.json and ssh.parameters.json with all valid parameters

5.1.0

Features

• #117 Allow HTTPS communication for Kibana by providing a certificate and private key
• #104 Support for Elasticsearch and Kibana 5.2.2
• #109 Support for Elasticsearch and Kibana 5.3.0
• #105 Disable ingest role on master only nodes; set only on data nodes, unless client nodes are present, in which case, set on client nodes only.
• #96 mark additional plugins installed as mandatory in elasticsearch.yml

Bug fixes

• #100 Quote all string parameters to VM scripts, including passwords (thank you @artfulhacker 🤗)
• #115 Fix disk mounting. Do not run disk utility script for master only or client only nodes. When a data node does not have any datadisks attached, use the temporary disk mounted by Azure at /mnt as the value for path.data.

Misc

• #103 tags all resources provisioned by the template with a unique identifier to allow the Azure Infrastructure to understand the origin of resources deployed.

5.0.1

We were setting security.encryptionKey for 2.x installations of kibana.

5.0 support

• 5.0 support throughout, both kibana and elasticsearch complete with x-pack.
• Node restart resiliency fixes, moved to monit for now. Thank you @ajhewett ! #71
• Add node.max_local_storage_nodes:1 as further safeguard
• kibana NSG issue on 5601 introduced in previous release.

ty @niemyjski for test driving 5.0 template!

1.5.4

The network security group was not properly attached to the jumpbox and kibana nic's due to the configuration was added at the wrong indentation level:

9d2e756

1.5.3

Fix Marketo API call …
Concatenating the curl parameters does not cause --date-encodeurl to be
evaluated. We now just pass them directly to curl. There's also no need
to check values ahead of time as it's okay to send them up empty.

1.5.2

Remove azure plugin as option from the UI since it relies on folks specifying keys and doing it correctly. Which has proven to increase failure rates if left open.