Skip to content

Latest commit

 

History

History
211 lines (144 loc) · 14 KB

CHANGELOG.md

File metadata and controls

211 lines (144 loc) · 14 KB
Raw

Changelog

7.3.2 - 2019/09/19

  • 7.3.2 as the default stack version
  • Testing of GKE for 1.11 dropped and 1.14 added #287)
  • Make helper scripts python3 compatible #255 @cclauss

Elasticsearch

PR Author Title
#238 @Crazybus Update documentation and defaults for tmpl values
#245 @skitle Fixed indent on elasticsearch extraVolumes tpl. Was causing parsing errors.
#250 @tanordheim Update priorityClassName default values in READMEs
#261 @Crazybus Bump google terraform provider to the latest
#154 @Crazybus Keystore integration
#290 @Crazybus Drop version from chart label in service
#270 @GreenKnight15 ES Variable Port Name
#259 @Crazybus Set default runAsUser for pod security context
#265 @maximelenair Hardening of the pod permissions.

Kibana

PR Author Title
#250 @tanordheim Update priorityClassName default values in READMEs
#268 @accek fixed bogus request of 500 millibytes mem
#272 @rccrdpccl use same env variable as application
#291 @Crazybus Explicitly test for a 200 for readinessProbe

Filebeat

PR Author Title
#243 @Crazybus Add configurable nodeSelector and affinity spec
#248 @tanordheim Add priorityClassName to filebeat chart
#250 @tanordheim Update priorityClassName default values in READMEs

Metricbeat

PR Author Title
#243 @Crazybus Add configurable nodeSelector and affinity spec
#251 @Crazybus Fix default configuration for kubernetes module
#289 @Crazybus Remove default kube static metrics host to avoid co…
#254 @Azuka Enable events access to cluster role

7.3.0 - 2019/07/31

  • 7.3.0 as the default stack version

Elasticsearch

PR Author Title
#226 @MichaelMarieJulie Add configurable pods labels
#237 @MichaelSp Add back service.alpha.kubernetes.io/tolerate-unready-endpoints: "true"

Kibana

PR Author Title
#225 @plumcraft Add configurable pod labels
#230 @Crazybus Add subPath support to secretMounts

7.2.1-0 - 2019/07/18

  • #195 - @cclauss - Initial steps started to move all python2 code to python3
  • #205 - @Crazybus - Fixup and improve security example documentation

Elasticsearch

  • #171 - @naseemkullah - Run Elasticsearch as a non-root user
  • #197 - @tetianakravchenko - Add option to provide custom start/stop hooks
  • #206 - @Crazybus - Automatically detect esMajorVersion for default images
  • #203 - @Crazybus - Add testing for security context
  • #220 - @JorisAndrade - Add option to disable sysctlInitContainer

Kibana

  • #204 - @Crazybus - Make imagePullPolicy actually do something
  • #210 - @cliedeman - Add Kibana pod annotations
  • #217 - @Crazybus - Update healthCheckPath to mention basePath usage

Filebeat

  • #214 - @dugouchet - Add additional labels

Metricbeat

  • #127 - @Crazybus - Add metricbeat chart
  • #128 - @Crazybus - Add ci jobs for metricbeat

7.2.0 - 2019/07/01

  • 7.2.0 as the default stack version
  • Updated the beta status messaging and added proper descriptions to each chart #158
  • Add GKE 1.13 to automated testing suite #169 and #181

Elasticsearch

  • #123 - @kimxogus - Make the service configurable
  • #141 - @satchpx - Add capability to specify alternate scheduler
  • #161 - @Crazybus - Add configurable nodePort to the service spec
  • #170 - @Crazybus - Update security example docs to match reality
  • #182 - @hxquangnhat - Fix secretName field for secretMounts
  • #186 - @Crazybus - Fix pvc annotations with multiple fields
  • #189 - @gnatpat - Add resources to sidecar container

Kibana

  • #160 - @Crazybus - Add configurable nodePort to the service spec
  • #168 - @Crazybus - Always set server.host to the docker default
  • #172 - @naseemkullah - Run Kibana as the non-root kibana user (1000)
  • #182 - @hxquangnhat - Fix secretName field for secretMounts
  • #184 - @diegofernandes - Fix wildcard support for ingress

Filebeat

  • #182 - @hxquangnhat - Fix secretName field for secretMounts
  • #188 - @cclauss - Fix octal literal to work in both Python 2 and Python 3

7.1.1 - 2019/06/07

  • 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.

Elasticsearch

  • #146 - @Crazybus - Add instructions for how to enable snapshots

Kibana

  • #151 - @natebwangsut - Added an option to add annotations(s) to service resource

Filebeat

  • #140 - @Crazybus - Remove fsGroup from container level security context

7.1.0 - 2019/05/21

  • 7.1.0 as the default stack version
  • Promotion from alpha to beta status
  • Filebeat chart added

Elasticsearch

  • #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

Kibana

  • #109 - @lancespeelmon - Add support for k8s priorityclass
  • #134 - @Crazybus - Explicitly set the targetPort to the defined http port

Filebeat

  • #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-alpha1 - 2019/05/01

Elasticsearch

  • #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

Kibana

  • #107 - @Crazybus - Make the health check path configurable to support webroots and other customizations.

7.0.0-alpha1 - 2019/04/17

  • #96 - @Crazybus - 7.0.0 as the default stack version

Elasticsearch

  • #94 - @kimxogus - Remove hardcoded storageClassName

Notes

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 elastic#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"