[3.2] Add release notes #8844
Draft
[3.2] Add release notes #8844
+48
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
rhr323
added
>docs
🔍 Preview links for changed docs |
pebrc
reviewed
Oct 15, 2025
|
|
||
| #### 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. |
There was a problem hiding this comment.
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. |
|
|
||
| #### 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. |
There was a problem hiding this comment.
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
...draft...