- 7.1.1 as the default stack version
- Helm 2.14.0 as the tested version. Helm 2.14.0 has some extra validation built in which caused an issue with an invalid field in the filebeat chart.
- #146 - @Crazybus - Add instructions for how to enable snapshots
- #151 - @natebwangsut - Added an option to add annotations(s) to service resource
- #140 - @Crazybus - Remove fsGroup from container level security context
- 7.1.0 as the default stack version
- Promotion from alpha to beta status
- Filebeat chart added
- #119 - @kimxogus - Wait for new master election before stopping the pod to prevent master status being temporarily lost during rolling upgrades #63
- #109 - @lancespeelmon - Add support for k8s priorityclass
- #109 - @lancespeelmon - Add support for k8s priorityclass
- #134 - @Crazybus - Explicitly set the targetPort to the defined http port
- #117 - @tylerjl - Add initial filebeat chart
- #122 - @Crazybus - Add ci jobs for filebeat
- #121 - @Crazybus - Add integration tests and other tweaks
- #129 - @tylerjl - Add usage notes for filebeat
- 7.0.1 as the default stack version
- Contributing guide, release process, changelog and issue templates added in #111
- Automated testing for Kubernetes 1.10 dropped because it is no longer available in GKE
- Helm client version bumped to 2.13.1
- #100 - @kuisathaverat - Remove deprecated zen ping unicast hosts setting
- #114 - @Crazybus - Make persistent volumes optional
- #115 - @Crazybus - Added an integration test for upgrading from the previous release and testing rolling upgrades
- #107 - @Crazybus - Make the health check path configurable to support webroots and other customizations.
- #96 - @Crazybus - 7.0.0 as the default stack version
- #94 - @kimxogus - Remove hardcoded storageClassName
If you were using the default Elasticsearch version from the previous release (6.6.2-alpha1) you will first need to upgrade to Elasticsearch 6.7.1 before being able to upgrade to 7.0.0. You can do this by adding this to your values file:
esMajorVersion: 6
imageTag: 6.7.1
If you are upgrading an existing cluster that did not override the default storageClassName you will now need to specify the storageClassName. This only affects existing clusters and was changed in #94. The advantage of this is that now the helm chart will just use the default storageClassName rather than needing to override it for any providers where it is not called standard.
volumeClaimTemplate:
storageClassName: "standard"