Skip to content
This repository has been archived by the owner on Mar 30, 2023. It is now read-only.

6.3.1
Compare
Choose a tag to compare
@russcam russcam released this 17 Oct 01:07
· 156 commits to master since this release
6.3.1
90134df

Elasticsearch, Kibana and Logstash 6.3.1 🎈

This release adds support for deploying Elasticsearch and Kibana 6.3.1 to Azure!

Features

#209 Add support for Elasticsearch and Kibana 6.3.1

Add support for Elasticsearch and Kibana 6.3.1

#208 Configure shard allocation awareness over Fault and Update domains

When data, master and coordinating nodes are provisioned, they are added to an Availability Set and assigned a Fault and Update domain. These values are now added as node attributes and used to configure shard allocation awareness on the node.

#207 Larger disk options 💾

Since the beginning, a user has been able to configure the size of data disks to attach to each data node, to store data. Two new disk sizes have now been added, giving choices of

  • 128GB (Small)
  • 512GB (Medium)
  • 1024GB (Large)
  • 2048GB (XLarge)
  • 4095GB (XXLarge)

With the default remaining as Large. Disks smaller than 2199023255040 bytes (~2199 GB) are partitioned with fdisk, while those larger are partitioned with parted, since they cannot use DOS partition table format and
instead must use Guid Partition table format (GPT).

#212 Use shared storage account for Azure repository plugin

The shared storage account deployed as part of the template can now be configured for use with the Azure repository plugin, reducing the need to provision a separate storage account. To use, pass a value of Yes for
azureCloudPlugin parameter.

#216 Documentation 📝

More comprehensive documentation for the template has now been added to the elastic.co website. Be sure to check out the version that corresponds to the template version being deployed.

#206 Configure custom probe for Application Gateway

When Application Gateway is selected as the loadBalancerType and xPackPlugins is Yes, a custom health probe is configured that now also considers a 401 response as healthy. This removes the need to configure anonymous access to the cluster base path.

Breaking changes

  • #210 Update to Azure CLI 2.0 and remove support for Azure CLI 1.0

The template has been updated to now use Azure CLI 2.0 for integration testing. Support for Azure CLI 1.0 has now been removed since the last released version does not support newer API versions of resources.

  • #211 Remove user information from template

The template no longer requires the separate collection of user information, simplifying the number of parameters that need to be provided. This data can now be surfaced from Azure infrastructure.

Assets 2
Loading