Skip to content

Clarify eck pdb documentation surrounding enterprise feature. #4062

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
+3 −1
Open

Clarify eck pdb documentation surrounding enterprise feature. #4062

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
87a8854
Clarify eck pdb documentation surround enterprise feature.
naemono Nov 24, 2025
9b869e9
Update deploy-manage/deploy/cloud-on-k8s/pod-disruption-budget.md
naemono Nov 24, 2025
27d407d
Update per recommendations.
naemono Nov 25, 2025
01ed794
Merge branch 'clarify-eck-pdb-documentation' of github.com:naemono/do…
naemono Nov 25, 2025
029b29e
remove note
naemono Nov 25, 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: 3 additions & 1 deletion deploy-manage/deploy/cloud-on-k8s/pod-disruption-budget.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,12 +19,13 @@ In {{eck}} 3.1 and earlier, all clusters follow the [default PodDisruptionBudget
:::

## Advanced rules (Enterprise license required)

```{applies_to}
deployment:
eck: ga 3.2
```

In Elasticsearch clusters managed by ECK and licensed with an Enterprise license, a separate PDB is created for each type of `nodeSet` defined in the manifest. This setup allows Kubernetes upgrade or maintenance operations to be executed more quickly. Each PDB permits one Elasticsearch Pod per `nodeSet` to be disrupted at a time, provided the Elasticsearch cluster maintains the health status described in the following table:
In Elasticsearch clusters managed by ECK and licensed with an Enterprise license, PDBs are created based on Elasticsearch node roles, allowing Kubernetes upgrade or maintenance operations to be executed more quickly. Multiple `nodeSets` with the same roles, such as `master` or `ml`, are combined into a single PDB. Each PDB permits one Elasticsearch Pod to be disrupted at a time, provided the Elasticsearch cluster maintains the health status described in the following table.
Copy link
Collaborator

@shainaraskas shainaraskas Nov 25, 2025

Choose a reason for hiding this comment

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

Suggested change
In Elasticsearch clusters managed by ECK and licensed with an Enterprise license, PDBs are created based on Elasticsearch node roles, allowing Kubernetes upgrade or maintenance operations to be executed more quickly. Multiple `nodeSets` with the same roles, such as `master` or `ml`, are combined into a single PDB. Each PDB permits one Elasticsearch Pod to be disrupted at a time, provided the Elasticsearch cluster maintains the health status described in the following table.
In {{es}} clusters managed by ECK and licensed with an Enterprise license, PDBs are created based on {{es}} node roles, allowing Kubernetes upgrade or maintenance operations to be executed more quickly. Multiple `nodeSets` with the same roles, such as `master` or `ml`, are combined into a single PDB. Each PDB permits one {{es}} Pod to be disrupted at a time, provided the {{es}} cluster maintains the health status described in the following table.


| Role | Cluster health required | Notes |
|------|------------------------|--------|
Expand All @@ -40,6 +41,7 @@ In Elasticsearch clusters managed by ECK and licensed with an Enterprise license
Single-node clusters are not considered highly available and can always be disrupted regardless of license type.

## Default rules (Basic license) [default-pdb-rules]

:::{note}
In {{eck}} 3.1 and earlier, all clusters follow this behavior regardless of license type.
:::
Expand Down
Loading