From 31a3301f69f78b28fc809e52cd43a33c8ccb2fe4 Mon Sep 17 00:00:00 2001 From: Julien Mailleret Date: Thu, 17 Oct 2019 19:10:09 +0200 Subject: [PATCH 1/2] [elasticsearch] fix deprecated note related to https://github.com/elastic/helm-charts/pull/333/files#r335988708 --- elasticsearch/README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/elasticsearch/README.md b/elasticsearch/README.md index e17a4d677..552f54ad5 100644 --- a/elasticsearch/README.md +++ b/elasticsearch/README.md @@ -16,7 +16,6 @@ This helm chart is a lightweight way to configure and run our official [Elastics * This repo includes a number of [example](./examples) configurations which can be used as a reference. They are also used in the automated testing of this chart * Automated testing of this chart is currently only run against GKE (Google Kubernetes Engine). If you are using a different Kubernetes provider you will likely need to adjust the `storageClassName` in the `volumeClaimTemplate` -* The default storage class for GKE is `standard` which by default will give you `pd-ssd` type persistent volumes. This is network attached storage and will not perform as well as local storage. If you are using Kubernetes version 1.10 or greater you can use [Local PersistentVolumes](https://cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/local-ssd) for increased performance * The chart deploys a statefulset and by default will do an automated rolling update of your cluster. It does this by waiting for the cluster health to become green after each instance is updated. If you prefer to update manually you can set [`updateStrategy: OnDelete`](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#on-delete) * It is important to verify that the JVM heap size in `esJavaOpts` and to set the CPU/Memory `resources` to something suitable for your cluster * To simplify chart and maintenance each set of node groups is deployed as a separate helm release. Take a look at the [multi](./examples/multi) example to get an idea for how this works. Without doing this it isn't possible to resize persistent volumes in a statefulset. By setting it up this way it makes it possible to add more nodes with a new storage size then drain the old ones. It also solves the problem of allowing the user to determine which node groups to update first when doing upgrades or changes. @@ -264,7 +263,7 @@ make #### KIND - Kubernetes -It is also possible to run this chart using a Kubernetes [KIND (Kubernetes in Docker)](https://github.com/kubernetes-sigs/kind) cluster: +It is also possible to run this chart using a Kubernetes [KIND (Kubernetes in Docker)](https://github.com/kubernetes-sigs/kind) cluster: ``` cd examples/kubernetes-kind From a5e9a5eeaf5dd51089cccdd51cbbed173f729d33 Mon Sep 17 00:00:00 2001 From: Julien Mailleret Date: Fri, 18 Oct 2019 08:05:15 +0200 Subject: [PATCH 2/2] Update elasticsearch/README.md Co-Authored-By: Michael Russell --- elasticsearch/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/elasticsearch/README.md b/elasticsearch/README.md index 552f54ad5..d37a2ef39 100644 --- a/elasticsearch/README.md +++ b/elasticsearch/README.md @@ -15,7 +15,7 @@ This helm chart is a lightweight way to configure and run our official [Elastics ## Usage notes and getting started * This repo includes a number of [example](./examples) configurations which can be used as a reference. They are also used in the automated testing of this chart -* Automated testing of this chart is currently only run against GKE (Google Kubernetes Engine). If you are using a different Kubernetes provider you will likely need to adjust the `storageClassName` in the `volumeClaimTemplate` +* Automated testing of this chart is currently only run against GKE (Google Kubernetes Engine). * The chart deploys a statefulset and by default will do an automated rolling update of your cluster. It does this by waiting for the cluster health to become green after each instance is updated. If you prefer to update manually you can set [`updateStrategy: OnDelete`](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#on-delete) * It is important to verify that the JVM heap size in `esJavaOpts` and to set the CPU/Memory `resources` to something suitable for your cluster * To simplify chart and maintenance each set of node groups is deployed as a separate helm release. Take a look at the [multi](./examples/multi) example to get an idea for how this works. Without doing this it isn't possible to resize persistent volumes in a statefulset. By setting it up this way it makes it possible to add more nodes with a new storage size then drain the old ones. It also solves the problem of allowing the user to determine which node groups to update first when doing upgrades or changes.