1.2.1 release highlights
edit1.2.1 release highlights
editThis is a patch release to address some issues found after the 1.2.0 release. See 1.2.0 release highlights for the full highlights of the 1.2.x series.
Fixes
editSupport for Kibana 7.9.0
editSupport has been added for managing secure settings for Kibana 7.9.0 which expects the keystore to be located at a different path from previous versions.
APM Server and Beats not starting up when referenced Kibana has TLS disabled
editAPM Server and Beats resources should no longer fail to start if the Kibana referenced using kibanaRef
has TLS disabled.
Elasticsearch failing to start under certain conditions
editHaving the Istio CNI plugin enabled or enabling automountServiceAccountToken
in the pod template should no longer prevent the Elasticsearch containers from failing to start with the error message /usr/local/bin/docker-entrypoint.sh: line 49: /usr/share/elasticsearch/bin/elasticsearch-env-from-file: No such file or directory
.
Known issues
edit-
Elasticsearch transform nodes are not automatically labelled by the operator. If you need to identify transform nodes, use the
podTemplate
of thenodeSet
to add your own label. - If you want to try out Workplace Search, use the ECK trial licensing mechanism instead of clicking on the Start a Free Trial button on the Enterprise Search splash screen.