Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion config/crds/v1/all-crds.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4674,7 +4674,7 @@ spec:
The behavior depends on the license level.
With a Basic license or if podDisruptionBudget.spec is not empty:
The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.
In all other cases the default podDisruptionBudget sets `minUnavailable` equal to the total number of nodes minus 1.
In all other cases the default podDisruptionBudget sets `minAvailable` equal to the total number of nodes minus 1.
With an Enterprise license and if podDisruptionBudget.spec is empty:
The default budget is split into multiple budgets, each targeting a specific node role type allowing additional disruptions
for certain roles according to the health status of the cluster.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -9622,7 +9622,7 @@ spec:
The behavior depends on the license level.
With a Basic license or if podDisruptionBudget.spec is not empty:
The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.
In all other cases the default podDisruptionBudget sets `minUnavailable` equal to the total number of nodes minus 1.
In all other cases the default podDisruptionBudget sets `minAvailable` equal to the total number of nodes minus 1.
With an Enterprise license and if podDisruptionBudget.spec is empty:
The default budget is split into multiple budgets, each targeting a specific node role type allowing additional disruptions
for certain roles according to the health status of the cluster.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -4716,7 +4716,7 @@ spec:
The behavior depends on the license level.
With a Basic license or if podDisruptionBudget.spec is not empty:
The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.
In all other cases the default podDisruptionBudget sets `minUnavailable` equal to the total number of nodes minus 1.
In all other cases the default podDisruptionBudget sets `minAvailable` equal to the total number of nodes minus 1.
With an Enterprise license and if podDisruptionBudget.spec is empty:
The default budget is split into multiple budgets, each targeting a specific node role type allowing additional disruptions
for certain roles according to the health status of the cluster.
Expand Down
2 changes: 1 addition & 1 deletion deploy/eck-stack/charts/eck-elasticsearch/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,7 @@ volumeClaimDeletePolicy: ""

# Settings to limit the disruption when pods need to be rescheduled for some reason such as upgrades or routine maintenance.
# By default, if not set, the operator sets a budget that doesn't allow any pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.
# In all other cases the default PodDisruptionBudget sets `minUnavailable` equal to the total number of nodes minus 1.
# In all other cases the default PodDisruptionBudget sets `minAvailable` equal to the total number of nodes minus 1.
# To completely disable the pod disruption budget set `disabled` to true.
#
# podDisruptionBudget:
Expand Down
2 changes: 1 addition & 1 deletion docs/reference/api-reference/3_0_0.md
Original file line number Diff line number Diff line change
Expand Up @@ -1093,7 +1093,7 @@ ElasticsearchSpec holds the specification of an Elasticsearch cluster.
| *`transport`* __[TransportConfig](#transportconfig)__ | Transport holds transport layer settings for Elasticsearch. |
| *`nodeSets`* __[NodeSet](#nodeset) array__ | NodeSets allow specifying groups of Elasticsearch nodes sharing the same configuration and Pod templates. |
| *`updateStrategy`* __[UpdateStrategy](#updatestrategy)__ | UpdateStrategy specifies how updates to the cluster should be performed. |
| *`podDisruptionBudget`* __[PodDisruptionBudgetTemplate](#poddisruptionbudgettemplate)__ | PodDisruptionBudget provides access to the default Pod disruption budget for the Elasticsearch cluster.<br>The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.<br>In all other cases the default PodDisruptionBudget sets `minUnavailable` equal to the total number of nodes minus 1.<br>To disable, set `PodDisruptionBudget` to the empty value (`{}` in YAML). |
| *`podDisruptionBudget`* __[PodDisruptionBudgetTemplate](#poddisruptionbudgettemplate)__ | PodDisruptionBudget provides access to the default Pod disruption budget for the Elasticsearch cluster.<br>The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.<br>In all other cases the default PodDisruptionBudget sets `minAvailable` equal to the total number of nodes minus 1.<br>To disable, set `PodDisruptionBudget` to the empty value (`{}` in YAML). |
| *`auth`* __[Auth](#auth)__ | Auth contains user authentication and authorization security settings for Elasticsearch. |
| *`secureSettings`* __[SecretSource](#secretsource) array__ | SecureSettings is a list of references to Kubernetes secrets containing sensitive configuration options for Elasticsearch. |
| *`serviceAccountName`* __string__ | ServiceAccountName is used to check access from the current resource to a resource (for ex. a remote Elasticsearch cluster) in a different namespace.<br>Can only be used if ECK is enforcing RBAC on references. |
Expand Down
2 changes: 1 addition & 1 deletion docs/reference/api-reference/3_1_0.md
Original file line number Diff line number Diff line change
Expand Up @@ -1093,7 +1093,7 @@ ElasticsearchSpec holds the specification of an Elasticsearch cluster.
| *`transport`* __[TransportConfig](#transportconfig)__ | Transport holds transport layer settings for Elasticsearch. |
| *`nodeSets`* __[NodeSet](#nodeset) array__ | NodeSets allow specifying groups of Elasticsearch nodes sharing the same configuration and Pod templates. |
| *`updateStrategy`* __[UpdateStrategy](#updatestrategy)__ | UpdateStrategy specifies how updates to the cluster should be performed. |
| *`podDisruptionBudget`* __[PodDisruptionBudgetTemplate](#poddisruptionbudgettemplate)__ | PodDisruptionBudget provides access to the default Pod disruption budget for the Elasticsearch cluster.<br>The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.<br>In all other cases the default PodDisruptionBudget sets `minUnavailable` equal to the total number of nodes minus 1.<br>To disable, set `PodDisruptionBudget` to the empty value (`{}` in YAML). |
| *`podDisruptionBudget`* __[PodDisruptionBudgetTemplate](#poddisruptionbudgettemplate)__ | PodDisruptionBudget provides access to the default Pod disruption budget for the Elasticsearch cluster.<br>The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.<br>In all other cases the default PodDisruptionBudget sets `minAvailable` equal to the total number of nodes minus 1.<br>To disable, set `PodDisruptionBudget` to the empty value (`{}` in YAML). |
| *`auth`* __[Auth](#auth)__ | Auth contains user authentication and authorization security settings for Elasticsearch. |
| *`secureSettings`* __[SecretSource](#secretsource) array__ | SecureSettings is a list of references to Kubernetes secrets containing sensitive configuration options for Elasticsearch. |
| *`serviceAccountName`* __string__ | ServiceAccountName is used to check access from the current resource to a resource (for ex. a remote Elasticsearch cluster) in a different namespace.<br>Can only be used if ECK is enforcing RBAC on references. |
Expand Down
2 changes: 1 addition & 1 deletion docs/reference/api-reference/3_2_0.md
Original file line number Diff line number Diff line change
Expand Up @@ -1093,7 +1093,7 @@ ElasticsearchSpec holds the specification of an Elasticsearch cluster.
| *`transport`* __[TransportConfig](#transportconfig)__ | Transport holds transport layer settings for Elasticsearch. |
| *`nodeSets`* __[NodeSet](#nodeset) array__ | NodeSets allow specifying groups of Elasticsearch nodes sharing the same configuration and Pod templates. |
| *`updateStrategy`* __[UpdateStrategy](#updatestrategy)__ | UpdateStrategy specifies how updates to the cluster should be performed. |
| *`podDisruptionBudget`* __[PodDisruptionBudgetTemplate](#poddisruptionbudgettemplate)__ | PodDisruptionBudget provides access to the default Pod disruption budget(s) for the Elasticsearch cluster.<br>The behavior depends on the license level.<br>With a Basic license or if podDisruptionBudget.spec is not empty:<br> The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.<br> In all other cases the default podDisruptionBudget sets `minUnavailable` equal to the total number of nodes minus 1.<br>With an Enterprise license and if podDisruptionBudget.spec is empty:<br> The default budget is split into multiple budgets, each targeting a specific node role type allowing additional disruptions<br> for certain roles according to the health status of the cluster.<br> Example:<br> All data roles (excluding frozen): allows disruptions only when the cluster is green.<br> All other roles: allows disruptions only when the cluster is yellow or green.<br>To disable, set `podDisruptionBudget` to the empty value (`{}` in YAML). |
| *`podDisruptionBudget`* __[PodDisruptionBudgetTemplate](#poddisruptionbudgettemplate)__ | PodDisruptionBudget provides access to the default Pod disruption budget(s) for the Elasticsearch cluster.<br>The behavior depends on the license level.<br>With a Basic license or if podDisruptionBudget.spec is not empty:<br> The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.<br> In all other cases the default podDisruptionBudget sets `minAvailable` equal to the total number of nodes minus 1.<br>With an Enterprise license and if podDisruptionBudget.spec is empty:<br> The default budget is split into multiple budgets, each targeting a specific node role type allowing additional disruptions<br> for certain roles according to the health status of the cluster.<br> Example:<br> All data roles (excluding frozen): allows disruptions only when the cluster is green.<br> All other roles: allows disruptions only when the cluster is yellow or green.<br>To disable, set `podDisruptionBudget` to the empty value (`{}` in YAML). |
| *`auth`* __[Auth](#auth)__ | Auth contains user authentication and authorization security settings for Elasticsearch. |
| *`secureSettings`* __[SecretSource](#secretsource) array__ | SecureSettings is a list of references to Kubernetes secrets containing sensitive configuration options for Elasticsearch. |
| *`serviceAccountName`* __string__ | ServiceAccountName is used to check access from the current resource to a resource (for ex. a remote Elasticsearch cluster) in a different namespace.<br>Can only be used if ECK is enforcing RBAC on references. |
Expand Down
2 changes: 1 addition & 1 deletion docs/reference/api-reference/main.md
Original file line number Diff line number Diff line change
Expand Up @@ -1093,7 +1093,7 @@ ElasticsearchSpec holds the specification of an Elasticsearch cluster.
| *`transport`* __[TransportConfig](#transportconfig)__ | Transport holds transport layer settings for Elasticsearch. |
| *`nodeSets`* __[NodeSet](#nodeset) array__ | NodeSets allow specifying groups of Elasticsearch nodes sharing the same configuration and Pod templates. |
| *`updateStrategy`* __[UpdateStrategy](#updatestrategy)__ | UpdateStrategy specifies how updates to the cluster should be performed. |
| *`podDisruptionBudget`* __[PodDisruptionBudgetTemplate](#poddisruptionbudgettemplate)__ | PodDisruptionBudget provides access to the default Pod disruption budget(s) for the Elasticsearch cluster.<br>The behavior depends on the license level.<br>With a Basic license or if podDisruptionBudget.spec is not empty:<br> The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.<br> In all other cases the default podDisruptionBudget sets `minUnavailable` equal to the total number of nodes minus 1.<br>With an Enterprise license and if podDisruptionBudget.spec is empty:<br> The default budget is split into multiple budgets, each targeting a specific node role type allowing additional disruptions<br> for certain roles according to the health status of the cluster.<br> Example:<br> All data roles (excluding frozen): allows disruptions only when the cluster is green.<br> All other roles: allows disruptions only when the cluster is yellow or green.<br>To disable, set `podDisruptionBudget` to the empty value (`{}` in YAML). |
| *`podDisruptionBudget`* __[PodDisruptionBudgetTemplate](#poddisruptionbudgettemplate)__ | PodDisruptionBudget provides access to the default Pod disruption budget(s) for the Elasticsearch cluster.<br>The behavior depends on the license level.<br>With a Basic license or if podDisruptionBudget.spec is not empty:<br> The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.<br> In all other cases the default podDisruptionBudget sets `minAvailable` equal to the total number of nodes minus 1.<br>With an Enterprise license and if podDisruptionBudget.spec is empty:<br> The default budget is split into multiple budgets, each targeting a specific node role type allowing additional disruptions<br> for certain roles according to the health status of the cluster.<br> Example:<br> All data roles (excluding frozen): allows disruptions only when the cluster is green.<br> All other roles: allows disruptions only when the cluster is yellow or green.<br>To disable, set `podDisruptionBudget` to the empty value (`{}` in YAML). |
| *`auth`* __[Auth](#auth)__ | Auth contains user authentication and authorization security settings for Elasticsearch. |
| *`secureSettings`* __[SecretSource](#secretsource) array__ | SecureSettings is a list of references to Kubernetes secrets containing sensitive configuration options for Elasticsearch. |
| *`serviceAccountName`* __string__ | ServiceAccountName is used to check access from the current resource to a resource (for ex. a remote Elasticsearch cluster) in a different namespace.<br>Can only be used if ECK is enforcing RBAC on references. |
Expand Down
2 changes: 1 addition & 1 deletion hack/upgrade-test-harness/testdata/v2100/crds.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2543,7 +2543,7 @@ spec:
minItems: 1
type: array
podDisruptionBudget:
description: PodDisruptionBudget provides access to the default Pod disruption budget for the Elasticsearch cluster. The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`. In all other cases the default PodDisruptionBudget sets `minUnavailable` equal to the total number of nodes minus 1. To disable, set `PodDisruptionBudget` to the empty value (`{}` in YAML).
description: PodDisruptionBudget provides access to the default Pod disruption budget for the Elasticsearch cluster. The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`. In all other cases the default PodDisruptionBudget sets `minAvailable` equal to the total number of nodes minus 1. To disable, set `PodDisruptionBudget` to the empty value (`{}` in YAML).
properties:
metadata:
description: ObjectMeta is the metadata of the PDB. The name and namespace provided here are managed by ECK and will be ignored.
Expand Down
2 changes: 1 addition & 1 deletion hack/upgrade-test-harness/testdata/v2111/crds.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2718,7 +2718,7 @@ spec:
minItems: 1
type: array
podDisruptionBudget:
description: PodDisruptionBudget provides access to the default Pod disruption budget for the Elasticsearch cluster. The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`. In all other cases the default PodDisruptionBudget sets `minUnavailable` equal to the total number of nodes minus 1. To disable, set `PodDisruptionBudget` to the empty value (`{}` in YAML).
description: PodDisruptionBudget provides access to the default Pod disruption budget for the Elasticsearch cluster. The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`. In all other cases the default PodDisruptionBudget sets `minAvailable` equal to the total number of nodes minus 1. To disable, set `PodDisruptionBudget` to the empty value (`{}` in YAML).
properties:
metadata:
description: ObjectMeta is the metadata of the PDB. The name and namespace provided here are managed by ECK and will be ignored.
Expand Down
2 changes: 1 addition & 1 deletion hack/upgrade-test-harness/testdata/v2121/crds.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4456,7 +4456,7 @@ spec:
description: |-
PodDisruptionBudget provides access to the default Pod disruption budget for the Elasticsearch cluster.
The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.
In all other cases the default PodDisruptionBudget sets `minUnavailable` equal to the total number of nodes minus 1.
In all other cases the default PodDisruptionBudget sets `minAvailable` equal to the total number of nodes minus 1.
To disable, set `PodDisruptionBudget` to the empty value (`{}` in YAML).
properties:
metadata:
Expand Down
2 changes: 1 addition & 1 deletion hack/upgrade-test-harness/testdata/v2130/crds.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4477,7 +4477,7 @@ spec:
description: |-
PodDisruptionBudget provides access to the default Pod disruption budget for the Elasticsearch cluster.
The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.
In all other cases the default PodDisruptionBudget sets `minUnavailable` equal to the total number of nodes minus 1.
In all other cases the default PodDisruptionBudget sets `minAvailable` equal to the total number of nodes minus 1.
To disable, set `PodDisruptionBudget` to the empty value (`{}` in YAML).
properties:
metadata:
Expand Down
2 changes: 1 addition & 1 deletion hack/upgrade-test-harness/testdata/v2140/crds.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4543,7 +4543,7 @@ spec:
description: |-
PodDisruptionBudget provides access to the default Pod disruption budget for the Elasticsearch cluster.
The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.
In all other cases the default PodDisruptionBudget sets `minUnavailable` equal to the total number of nodes minus 1.
In all other cases the default PodDisruptionBudget sets `minAvailable` equal to the total number of nodes minus 1.
To disable, set `PodDisruptionBudget` to the empty value (`{}` in YAML).
properties:
metadata:
Expand Down
2 changes: 1 addition & 1 deletion hack/upgrade-test-harness/testdata/v2150/crds.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4498,7 +4498,7 @@ spec:
description: |-
PodDisruptionBudget provides access to the default Pod disruption budget for the Elasticsearch cluster.
The default budget doesn't allow any Pod to be removed in case the cluster is not green or if there is only one node of type `data` or `master`.
In all other cases the default PodDisruptionBudget sets `minUnavailable` equal to the total number of nodes minus 1.
In all other cases the default PodDisruptionBudget sets `minAvailable` equal to the total number of nodes minus 1.
To disable, set `PodDisruptionBudget` to the empty value (`{}` in YAML).
properties:
metadata:
Expand Down
Loading