Skip to content

Commit 8091c0d

Browse files
thbkrkrthbkrkr
authored
[1.5] Release notes and highlights for 1.5.0 (#4313) (#4351)
1 parent bec2e04 commit 8091c0d

6 files changed

+147
-0
lines changed

‎docs/release-notes.asciidoc

+4
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@
66

77
This section summarizes the changes in each release.
88

9+
* <<release-notes-1.5.0>>
10+
* <<release-notes-1.4.1>>
911
* <<release-notes-1.4.0>>
1012
* <<release-notes-1.3.2>>
1113
* <<release-notes-1.3.1>>
@@ -22,6 +24,8 @@ This section summarizes the changes in each release.
2224

2325
--
2426

27+
include::release-notes/1.5.0.asciidoc[]
28+
include::release-notes/1.4.1.asciidoc[]
2529
include::release-notes/1.4.0.asciidoc[]
2630
include::release-notes/1.3.2.asciidoc[]
2731
include::release-notes/1.3.1.asciidoc[]

‎docs/release-notes/1.4.1.asciidoc

+18
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
:issue: https://github.com/elastic/cloud-on-k8s/issues/
2+
:pull: https://github.com/elastic/cloud-on-k8s/pull/
3+
4+
[[release-notes-1.4.1]]
5+
== {n} version 1.4.1
6+
7+
8+
9+
10+
11+
[[bug-1.4.1]]
12+
[float]
13+
=== Bug fixes
14+
15+
* Set webhook matchPolicy to Exact {pull}4271[#4271] (issue: {issue}4270[#4270])
16+
* [Helm] Unify role bindings {pull}4262[#4262]
17+
18+

‎docs/release-notes/1.5.0.asciidoc

+42
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
:issue: https://github.com/elastic/cloud-on-k8s/issues/
2+
:pull: https://github.com/elastic/cloud-on-k8s/pull/
3+
4+
[[release-notes-1.5.0]]
5+
== {n} version 1.5.0
6+
7+
[[breaking-1.5.0]]
8+
[float]
9+
=== Breaking changes
10+
11+
* Promote EnterpriseSearch Custom Resource Definition to v1 {pull}4284[#4284] (issue: {issue}4257[#4257])
12+
13+
14+
[[feature-1.5.0]]
15+
[float]
16+
=== New features
17+
18+
* [Autoscaling] Report overlapping policies {pull}4265[#4265]
19+
* [Autoscaling] Add setting to customize autoscaling API polling frequency {pull}4264[#4264]
20+
* [Autoscaling] Add scale down stabilization {pull}4250[#4250]
21+
* [Autoscaling] Add support for request/limit ratio {pull}4239[#4239] (issue: {issue}4006[#4006])
22+
* [Autoscaling] Add Elasticsearch autoscaling controller {pull}4173[#4173]
23+
* [Autoscaling] Add Elasticsearch API client {pull}4158[#4158]
24+
* [Autoscaling] Add autoscaling resource definition {pull}4148[#4148] (issue: {issue}4006[#4006])
25+
26+
[[enhancement-1.5.0]]
27+
[float]
28+
=== Enhancements
29+
30+
* Add support for VolumeClaimDeletePolicies for Elasticsearch clusters {pull}4050[#4050] (issue: {issue}2328[#2328])
31+
32+
[[bug-1.5.0]]
33+
[float]
34+
=== Bug fixes
35+
36+
* Fix OpenShift monitoring recipe {pull}4344[#4344]
37+
38+
[[deprecation-1.5.0]]
39+
[float]
40+
=== Deprecation
41+
42+
* OpenShift 3.11 support is deprecated in ECK 2.0. ECK 1.8 is the last version that supports OpenShift 3.11.

‎docs/release-notes/highlights-1.4.1.asciidoc

+41
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
[[release-highlights-1.4.1]]
2+
== 1.4.1 release highlights
3+
4+
[float]
5+
[id="{p}-141-fixes"]
6+
=== Fixes
7+
8+
This release addresses two issues related to the Helm chart for the ECK operator.
9+
10+
* On Kubernetes version 1.16 or higher, if the operator was installed using Helm and if the validating webhook was enabled, users were prevented from <<{p}-volume-claim-templates,increasing the storage size>> of Elasticsearch `volumeClaimTemplates` even if the underlying storage class allowed expansion.
11+
* When the ECK operator namespace was included in the <<{p}-install-helm-restricted,managed namespaces list>> a role binding was missing from the generated manifests.
12+
13+
[float]
14+
[id="{p}-141-known-issues"]
15+
=== Known issues
16+
17+
Elastic Agent currently writes its runtime state into the filesystem of its container. As a consequence, the identity of the Elastic Agent changes on container restarts and any internal state of applications run by that Elastic Agent is lost. As a workaround, you can mount the agent-data `hostPath` volume into the Elastic Agent container in the location where the process writes its runtime state. You also have to run the Elastic Agent as the root user to be able to access the `hostPath` volume, as shown in the following example:
18+
[source,yaml]
19+
----
20+
apiVersion: agent.k8s.elastic.co/v1alpha1
21+
kind: Agent
22+
metadata:
23+
name: elastic-agent
24+
spec:
25+
version: 7.11.1
26+
daemonSet:
27+
podTemplate:
28+
spec:
29+
containers:
30+
- name: agent
31+
securityContext:
32+
runAsUser: 0
33+
volumeMounts:
34+
- name: agent-data
35+
mountPath: /usr/share/elastic-agent/data/elastic-agent-9b2fec/run
36+
----
37+
The `mountPath` differs from version to version as it contains the hash of the version control system reference which was used to build Elastic Agent. You can find out which path to use by either inspecting the Docker image or by running a command against the container, as shown below:
38+
[source,sh]
39+
----
40+
docker run -ti --entrypoint bash docker.elastic.co/beats/elastic-agent:7.11.1 -c "ls /usr/share/elastic-agent/data"
41+
----

‎docs/release-notes/highlights-1.5.0.asciidoc

+38
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
[[release-highlights-1.5.0]]
2+
== 1.5.0 release highlights
3+
4+
[float]
5+
[id="{p}-150-new-and-notable"]
6+
=== New and notable
7+
8+
New and notable changes in version 1.5.0 of {n}. See <<release-notes-1.5.0>> for the full list of changes.
9+
10+
[float]
11+
[id="{p}-150-autoscaling-support"]
12+
==== Support for Autoscaling
13+
14+
ECK 1.5.0 introduces experimental support for link:https://www.elastic.co/guide/en/elasticsearch/reference/7.11/xpack-autoscaling.html[Autoscaling].
15+
16+
In this initial release, autoscaling monitors the storage usage of your Elasticsearch data nodes and the available memory capacity for your machine learning jobs. As your data grows, whether you’re expanding to new use cases or simply storing data for longer, autoscaling automatically adjusts resource capacity to ensure you can store your data, and that your machine learning jobs can execute — so you don’t have to worry about whether your deployment can support your requirements. Future releases will include autoscaling based on additional metrics and stack components (such as Kibana).
17+
18+
[float]
19+
[id="{p}-150-controlling-volume-claim-deletion"]
20+
==== Controlling volume claim deletion
21+
22+
ECK automatically deletes PersistentVolumeClaim resources if the owning Elasticsearch nodes are scaled down. The corresponding PersistentVolumes may be preserved, depending on the configured link:https://kubernetes.io/docs/concepts/storage/storage-classes/#reclaim-policy[storage class reclaim policy].
23+
24+
In addition, you can now control what ECK should do with the PersistentVolumeClaims if you delete the Elasticsearch cluster altogether through the new `volumeClaimDeletePolicy` attribute.
25+
26+
The possible values are `DeleteOnScaledownAndClusterDeletion` and `DeleteOnScaledownOnly`. By default `DeleteOnScaledownAndClusterDeletion` is in effect, which means that all PersistentVolumeClaims are deleted together with the Elasticsearch cluster. However, `DeleteOnScaledownOnly` keeps the PersistentVolumeClaims when deleting the Elasticsearch cluster. If you recreate a deleted cluster with the same name and node sets as before, the existing PersistentVolumeClaims will be adopted by the new cluster.
27+
28+
[float]
29+
[id="{p}-150-enterprisesearch-resource-version-promotion"]
30+
==== EnterpriseSearch resource version promotion
31+
32+
EnterpriseSearch resources have graduated to version `v1`. Old resources must be migrated to the new version to work with ECK 1.5.0. Resources created using an older version continue to run but the operator will not manage them.
33+
34+
[float]
35+
[id="{p}-150-known-issues"]
36+
=== Known issues
37+
38+
On Kubernetes version prior to 1.13 or on OpenShift 3.11, if the validating admission webhook is enabled, you might be prevented from upgrading the version of the EnterpriseSearch resources. This is due to a link:https://github.com/kubernetes/kubernetes/issues/73752[bug] in Kubernetes. As a workaround, you can temporarily disable the webhook to upgrade the EnterpriseSearch resources.

‎docs/release-notes/highlights.asciidoc

+4
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,8 @@
55
--
66
This section summarizes the most important changes in each release. For the full list, see <<eck-release-notes>>.
77

8+
* <<release-highlights-1.5.0>>
9+
* <<release-highlights-1.4.1>>
810
* <<release-highlights-1.4.0>>
911
* <<release-highlights-1.3.2>>
1012
* <<release-highlights-1.3.1>>
@@ -21,6 +23,8 @@ This section summarizes the most important changes in each release. For the full
2123

2224
--
2325

26+
include::highlights-1.5.0.asciidoc[]
27+
include::highlights-1.4.1.asciidoc[]
2428
include::highlights-1.4.0.asciidoc[]
2529
include::highlights-1.3.2.asciidoc[]
2630
include::highlights-1.3.1.asciidoc[]

0 commit comments

Comments
 (0)