# Azure Market Place - Elastic Stack for V6.3?

**URL:** https://discuss.elastic.co/t/azure-market-place-elastic-stack-for-v6-3/143359
**Category:** Elasticsearch
**Created:** [August 7, 2018, 3:20pm UTC](https://discuss.elastic.co/t/azure-market-place-elastic-stack-for-v6-3/143359 "2018-08-07T15:20:28Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![djl2](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@djl2](https://discuss.elastic.co/u/djl2)
#### Post date: [August 7, 2018, 3:20pm UTC](https://discuss.elastic.co/t/azure-market-place-elastic-stack-for-v6-3/143359/1 "2018-08-07T15:20:28Z")

</div>

Do you plan to update the Elastic Stack - (Elasticsearch, Kibana, X-Pack) for v6.3 soon? The current template only supports up to v6.2.4.

> **[elastic/azure-marketplace](https://github.com/elastic/azure-marketplace)**
>
> azure-marketplace - Elasticsearch Azure Marketplace offering + ARM template

Also, I tried manually updating my nodes to v6.3.1 using apt-get, but got this message--

```
Reading state information... Done
elasticsearch is already the newest version (6.2.4).
    0 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.

```

Will the v6.3.1 packages be added soon?

Thanks.

---

<div class="post-metadata">

### Author: ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)
#### Post date: [August 7, 2018, 11:15pm UTC](https://discuss.elastic.co/t/azure-market-place-elastic-stack-for-v6-3/143359/2 "2018-08-07T23:15:28Z")

</div>

@djl2 Azure Marketplace and the ARM template support up to 6.3.1, with 6.3.1 being the default version:

> <https://github.com/elastic/azure-marketplace/blob/master/src/mainTemplate.json#L22-L49>

Here's what the portal looks like:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/9/c94b019026aa1e8fb85ba9271a050cc9d174cbbd.png)

The [release notes for 6.3.1 can be found in the GitHub repository](https://github.com/elastic/azure-marketplace/releases/tag/6.3.1).

---

<div class="post-metadata">

### Author: ![djl2](https://avatars.discourse-cdn.com/v4/letter/d/e8c25b/32.png) [@djl2](https://discuss.elastic.co/u/djl2)
#### Post date: [August 9, 2018, 2:36pm UTC](https://discuss.elastic.co/t/azure-market-place-elastic-stack-for-v6-3/143359/3 "2018-08-09T14:36:58Z")

</div>

Oddly enough, when I click on my old link on my Azure Dashboard to the Elasticsearch Market Place cluster, it still only shows v6.2.4 as the latest version.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/7/37f2bdc11c1c5361d8c1af72694bb47ad654e002.png)

But if search for the ES cluster and bring up the Market Place ES Cluster fresh, I see v6.3.1. The links look identical too.

Anyway, thanks for the reply.

A couple more questions--

I originally forked the v6.2.4 templates and modified them quite a bit in order to deploy as single Nodes to Availability Zones and Scale Sets.

Without looking at all the v6.3.1 ARM templates changes, should I be able to simply add v6.3.1 to the mainTemplate.json and expect the newer versions to deploy? Did things change a lot in the templates in terms of how v6.3.1 is deployed?

Also, what's the easiest way to upgrade an existing v6.2.4 cluster? I tried using apt-get but it said that the latest packages were v6.2.4.

TIA

---

<div class="post-metadata">

### Author: ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)
#### Post date: [August 9, 2018, 10:01pm UTC](https://discuss.elastic.co/t/azure-market-place-elastic-stack-for-v6-3/143359/4 "2018-08-09T22:01:50Z")

</div>

> [@djl2](#):
>
> I originally forked the v6.2.4 templates and modified them quite a bit in order to deploy as single Nodes to Availability Zones and Scale Sets.

We have an [open issue for VM Scale sets](https://github.com/elastic/azure-marketplace/issues/30) - if you'd like to contribute back a PR for this feature, that would be very welcome!

> [@djl2](#):
>
> Without looking at all the v6.3.1 ARM templates changes, should I be able to simply add v6.3.1 to the mainTemplate.json and expect the newer versions to deploy? Did things change a lot in the templates in terms of how v6.3.1 is deployed?

There are a few changes related to [the opening of X-Pack in 6.3.0](https://www.elastic.co/products/x-pack/open); the distribution downloaded and installed for 6.3.0+ includes X-Pack features in the package, so X-Pack as a separate plugin to install does not exist.

There are also several other changes related to larger disks, shard allocation awareness, SSL/TLS for HTTP and Transport layers of Elasticsearch that may make it beneficial to apply the AZ and VMSS changes on top of.

> [@djl2](#):
>
> Also, what's the easiest way to upgrade an existing v6.2.4 cluster? I tried using apt-get but it said that the latest packages were v6.2.4.

The template uses the Debian package so would advise using this for the upgrade. [You can perform a rolling upgrade from 6.2.4 to 6.3.2 (latest).](https://www.elastic.co/guide/en/elasticsearch/reference/current/rolling-upgrades.html#rolling-upgrades) A few things to note:

- the template uses [`monit`](https://mmonit.com/) to monitor the Elasticsearch process, so should be interacted with using monit e.g.

- It is highly recommended that you backup your data before performing the upgrade. You may want to use the azure-repository plugin for this if you haven't installed already.

- The Debian package should leave your elasticsearch.yml configuration intact, but I would recommend making a copy anyway, in case.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 6, 2018, 10:02pm UTC](https://discuss.elastic.co/t/azure-market-place-elastic-stack-for-v6-3/143359/5 "2018-09-06T22:02:00Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
