Skip to content

[3.2] Add release notes #8844

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
+48 −0
Draft

[3.2] Add release notes #8844

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2ad08f6
draft release notes
rhr323 Oct 13, 2025
c766ac5
added draft release highlights
rhr323 Oct 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/release-notes/breaking-changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,10 @@ Breaking changes can impact your Elastic applications, potentially disrupting no
% **Action**<br> Steps for mitigating deprecation impact.
% ::::

## 3.2.0 [elastic-cloud-kubernetes-320-breaking-changes]

There are no breaking changes for ECK 3.2

## 3.1.0 [elastic-cloud-kubernetes-310-breaking-changes]

There are no breaking changes for ECK 3.1
Expand Down
4 changes: 4 additions & 0 deletions docs/release-notes/deprecations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,10 @@ Review the deprecated functionality for Elastic Cloud on Kubernetes. While depre
% **Action**<br> Steps for mitigating deprecation impact.
% ::::

## 3.2.0 [elastic-cloud-kubernetes-320-deprecations]

There are no deprecations for ECK 3.2

## 3.1.0 [elastic-cloud-kubernetes-310-deprecations]

There are no deprecations for ECK 3.1
Expand Down
36 changes: 36 additions & 0 deletions docs/release-notes/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,42 @@ mapped_pages:
# Elastic Cloud on Kubernetes release notes [elastic-cloud-kubernetes-release-notes]
Review the changes, fixes, and more in each release of Elastic Cloud on Kubernetes.

## 3.2.0 [elastic-cloud-kubernetes-320-release-notes]

### Release Highlights

#### Automatic pod disruption budget (Enterprise feature)

ECK now offers better out-of-the-box pod disruption budgets that automatically keep your cluster available as pods move across nodes. The new policy calculates the number of pods per tier that can sustain replacement and automatically generates a pod-disruption budget for each tier, enabling the Elasticsearch cluster to vacate Kubernetes nodes more quickly, while considering cluster health, without interruption.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
ECK now offers better out-of-the-box pod disruption budgets that automatically keep your cluster available as pods move across nodes. The new policy calculates the number of pods per tier that can sustain replacement and automatically generates a pod-disruption budget for each tier, enabling the Elasticsearch cluster to vacate Kubernetes nodes more quickly, while considering cluster health, without interruption.
ECK now offers better out-of-the-box PodDisruptionBudgets that automatically keep your cluster available as Pods move across nodes. The new policy calculates the number of Pods per tier that can sustain replacement and automatically generates a PodDisruptionBudget for each tier, enabling the Elasticsearch cluster to vacate Kubernetes nodes more quickly, while considering cluster health, without interruption.

We tend to capitalize Kubernetes API object names in the docs.


#### User Password Generation (Enterprise feature)

ECK will now generate longer passwords by default for the administrative user of each Elasticsearch Cluster. The password is 24 characters in length by default (can be configured to a maximum of 72 characters), incorporating alphabetic and numeric characters, to make password complexity stronger.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
ECK will now generate longer passwords by default for the administrative user of each Elasticsearch Cluster. The password is 24 characters in length by default (can be configured to a maximum of 72 characters), incorporating alphabetic and numeric characters, to make password complexity stronger.
ECK will now generate longer passwords by default for the administrative user of each Elasticsearch cluster. The password is 24 characters in length by default (can be configured to a maximum of 72 characters), incorporating alphabetic and numeric characters, to make password complexity stronger.


### Features and enhancements [elastic-cloud-kubernetes-320-features-and-enhancements]

- Fix beats stack monitoring cert reload [#8833](https://github.com/elastic/cloud-on-k8s/pull/8833) (issue: [#5448](https://github.com/elastic/cloud-on-k8s/issues/5448))
- Allow configuration parameters for file-base generated passwords. [#8817](https://github.com/elastic/cloud-on-k8s/pull/8817) (issues: [#2795](https://github.com/elastic/cloud-on-k8s/issues/2795), [#8693](https://github.com/elastic/cloud-on-k8s/issues/8693))
- Add automemlimit to automatically set GOMEMLIMIT. [#8814](https://github.com/elastic/cloud-on-k8s/pull/8814) (issue: [#8790](https://github.com/elastic/cloud-on-k8s/issues/8790))
- Improving the default PDB implementation. [#8780](https://github.com/elastic/cloud-on-k8s/pull/8780) (issue: [#2936](https://github.com/elastic/cloud-on-k8s/issues/2936))

### Fixes [elastic-cloud-kubernetes-320-fixes]

- Allow elasticsearchRef.secretName for eck-stack/Kibana [#8822](https://github.com/elastic/cloud-on-k8s/pull/8822) (issue: [#8816](https://github.com/elastic/cloud-on-k8s/issues/8816))

### Documentation improvements [elastic-cloud-kubernetes-320-documentation-improvements]

- Fix broken Logstash samples [#8801](https://github.com/elastic/cloud-on-k8s/pull/8801)
- [DOC] Comment JVM heap settings [#8753](https://github.com/elastic/cloud-on-k8s/pull/8753)

### Miscellaneous [elastic-cloud-kubernetes-320-miscellaneous]

- fix(deps): update all ungrouped dependencies [#8826](https://github.com/elastic/cloud-on-k8s/pull/8826)
- chore(deps): update go to v1.25.1 [#8823](https://github.com/elastic/cloud-on-k8s/pull/8823)
- Bump github.com/go-viper/mapstructure/v2 from 2.3.0 to 2.4.0 in /hack/operatorhub [#8810](https://github.com/elastic/cloud-on-k8s/pull/8810)
- fix(deps): update all ungrouped dependencies [#8809](https://github.com/elastic/cloud-on-k8s/pull/8809)
- Upgrade k8s libraries [#8806](https://github.com/elastic/cloud-on-k8s/pull/8806)

## 3.1.0 [elastic-cloud-kubernetes-310-release-notes]

### Release Highlights
Expand Down
4 changes: 4 additions & 0 deletions docs/release-notes/known-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,10 @@ Known issues are significant defects or limitations that may impact your impleme

:::

## 3.2.0 [elastic-cloud-kubernetes-320-known-issues]

There are no known issues in ECK 3.2

## 3.1.0 [elastic-cloud-kubernetes-310-known-issues]

There are no known issues in ECK 3.1
Expand Down
Loading