1.3.0

Features

• Allow deployment into a new or existing virtual network. When deploying into an existing virtual network, the resource group in which the virtual network resides must be in the same location as the target location for the deployment. Master, data and client nodes, as well as a kibana instance are all dynamically assigned IP addresses. The internal load balancer requires the user to specify an available IP address in the subnet, as this is used to connect to the cluster by both Kibana and the external load balancer (if one is selected).
• Set the default url in Sense to the IP address of the internal load balancer when plugins and kibana are installed
• Allow specifying a hostname prefix with which to prefix all nodes within the cluster. This is primarily to allow a deployment into an existing virtual network that contains an already deployed cluster; since master nodes are configured by hostname in the elasticsearch configuration, hostnames need to be different across different clusters.
• Send basic user information details to Elastic to understand who is using the template. These are required in the UI definition but are not in the deployment template. Details will only be sent when there is an email address.
• Conditionally show master node VM size configuration only when data nodes are not master eligible
• Conditionally show client node VM size configuration only when client node count is at least 1.
• Conditionally show kibana node VM size configuration only when install kibana is selected
• Validate admin username in the UI definition to prevent specifying a username that is invalid for a Ubuntu Administrator account.
• Update Microsoft.Storage components to use the 2016-01-01 api version
• Update Microsoft.Network components to use the 2016-03-30 api version