This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.

« 1.2.1 release highlights 1.1.2 release highlights »

› ›

1.2.0 release highlights

edit

1.2.0 release highlights

edit

New and notable

edit

New and notable changes in version 1.2.0 of Elastic Cloud on Kubernetes. Check Elastic Cloud on Kubernetes version 1.2.0 for the full list of changes.

Support for Elastic Enterprise Search

edit

ECK 1.2.0 introduces a new Custom Resource Definition (CRD) to easily deploy and orchestrate Elastic Enterprise Search on Kubernetes. With just a few lines of YAML configuration, you can launch an instance of App Search or Workplace Search (requires an Enterprise license or a trial) and connect it to an Elasticsearch cluster.

Support for Beats

edit

Deploying Beats on Kubernetes is straightforward using the new Beats CRD. You can deploy and manage data shippers such as Filebeat, Metricbeat, Auditbeat and others using ECK and effortlessly connect them to Elasticsearch and Kibana for storage and analysis.

Support for APM Agent central configuration

edit

APM Agent central configuration with ECK-managed Kibana and APM Servers is easier to configure. Simply add kibanaRef to the APM Server configuration and ECK will inject the required configuration to connect APM Server to the referenced Kibana.

Smaller and more secure operator image

edit

The operator container image is now much smaller and more secure thanks to switching to Distroless as the base image.

Known issues

edit

Elasticsearch transform nodes are not automatically labelled by the operator. If you need to identify transform nodes, use the podTemplate of the nodeSet 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.
The kibanaRef setting on Beats and APM Server custom resources require a Kibana secured by TLS. Unsecured Kibana references will prevent the resources from starting up. More information can be found in the issue.

« 1.2.1 release highlights 1.1.2 release highlights »