[incubator/elasticsearch] Upgrade default elastic version

[calbach]

FEATURE_REQUEST: Upgrade elasticsearch chart's default Elastic Search version from 2.4 -> 5.5.

Which chart:
incubator/elasticsearch

The chart defaults to a docker image with an old Elastic Search version (2.4), but there may be topological changes which would need to be applied along with the version change (I'm not sure).

[calbach]

FWIW I tried naively upgrading the docker image to use Elastic 5.5.1 with the fabric8 plugin of the same version, and my 2 master nodes crash-looped on their readiness checks failing to find eachother. I didn't spend too much effort debugging this, but including my notes here in case someone else finds it useful.

Dockerfile:

FROM docker.elastic.co/elasticsearch/elasticsearch:5.5.1

RUN elasticsearch-plugin install io.fabric8:elasticsearch-cloud-kubernetes:5.5.1

bootstrap.mlockall was no longer recognized, so I had to comment that out:

--- a/incubator/elasticsearch/templates/elasticsearch-configmap.yaml
+++ b/incubator/elasticsearch/templates/elasticsearch-configmap.yaml
@@ -16,7 +16,7 @@ data:
     node.name: ${HOSTNAME}
 
     # see https://github.com/kubernetes/kubernetes/issues/3595
-    bootstrap.mlockall: ${BOOTSTRAP_MLOCKALL:false}
+    # bootstrap.mlockall: ${BOOTSTRAP_MLOCKALL:false}

[dvonthenen]

Looks like there is a pending PR #1794 updating ES to 5.4.

[icereval]

FYI, the PR has been merged, I've also made an ES 5.5 build available on docker hub.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close