[doc] Fix minUnavailable typo in PDB by frivoire · Pull Request #8898 · elastic/cloud-on-k8s

frivoire · 2025-11-06T16:05:45Z

Hello,

This is a simple typo in the description of the PDB:
The minUnavailable concept doesn't exists in K8S, it's either minAvailable or maxUnavailable.

Thus this PR to fix this error everywhere ~~I've~~ grep found it ;)

prodsecmachine · 2025-11-06T16:05:58Z

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

github-actions · 2025-11-06T16:06:48Z

🔍 Preview links for changed docs

docs/reference/api-reference/main.md

barkbay

Thanks for your contribution!

We should not update the manifests that have been already released. Could you please revert your changes in hack/upgrade-test-harness/testdata/** and docs/reference/api-reference/3* ?

frivoire · 2025-12-16T20:26:40Z

Sorry for delay, I missed the notif ...

We should not update the manifests that have been already released. Could you please revert your changes in hack/upgrade-test-harness/testdata/** and docs/reference/api-reference/3* ?

I have to admit that I'm pretty surprised by this request (rationale: if there is a typo in a documentation, let's fix it in all impacted versions, even if already released, because those versioned docs are still being read by users of those versions, we are just documenting better the effective behavior of those past releases without changing the code here 🙄)
But I'm not maintainer here, so I've just push the partial revert 🙇

Is the PR ready to be merged now ?

barkbay · 2025-12-17T07:40:26Z

upgrade-test-harness is intended for upgrade testing, not for documentation purposes, that's why I think we should keep it as what has been installed by users.
The docs/reference/api-reference change is maybe more debatable; my concern is that this content is supposed to be generated automatically and copied from the previous release branches, which are not updated by your PR. Given that a new release is around the corner, I think updating only main for now is acceptable.

barkbay · 2025-12-17T07:46:00Z

buildkite test this please

barkbay · 2025-12-17T08:28:37Z

buildkite test this please

frivoire · 2025-12-17T12:58:35Z

Thanks for merging 👍

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [eck-operator](https://github.com/elastic/cloud-on-k8s) | minor | `3.2.0` → `3.3.0` | --- ### Release Notes <details> <summary>elastic/cloud-on-k8s (eck-operator)</summary> ### [`v3.3.0`](https://github.com/elastic/cloud-on-k8s/releases/tag/v3.3.0) [Compare Source](elastic/cloud-on-k8s@v3.2.0...v3.3.0) ##### Elastic Cloud on Kubernetes 3.3.0 - [Quickstart guide](https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s#eck-quickstart) ##### Release Highlights ##### AutoOps Integration (Enterprise feature) ECK now supports integration with Elastic AutoOps through a new `AutoOpsAgentPolicy` custom resource. This allows you to instrument multiple Elasticsearch clusters at once for automated health monitoring and performance recommendations. The [AutoOps documentation](https://www.elastic.co/docs/deploy-manage/monitor/autoops) provides more details. ##### Elastic Package Registry Integration ECK now supports deploying and managing Elastic Package Registry (EPR) through a new `PackageRegistry` custom resource. This is particularly useful for air-gapped environments, enabling Kibana to reference a self-hosted registry instead of the public one. The [package registry documentation](https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/package-registry) provides more details. ##### Multiple Stack Configuration Policies composition support (Enterprise feature) ECK now includes support for multiple Stack Config Policies targeting the same Elasticsearch cluster or Kibana instance, using a weight-based priority system for deterministic policy composition. The [stack config policy documentation](https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/elastic-stack-configuration-policies) provides more details. ##### Features and enhancements - AutoOpsAgentPolicy support [#8941](elastic/cloud-on-k8s#8941) (issue: [#8789](elastic/cloud-on-k8s#8789)) - ElasticPackageRegistry support [#8800](elastic/cloud-on-k8s#8800) (issue: [#8925](elastic/cloud-on-k8s#8925)) - Stack Config Policies composition support [#8917](elastic/cloud-on-k8s#8917) - Use standard Kibana labels and Helm labels on the ECK Operator pod [#8840](elastic/cloud-on-k8s#8840) (issue: [#8584](elastic/cloud-on-k8s#8584)) - Add service customization support for Elasticsearch remote cluster server [#8892](elastic/cloud-on-k8s#8892) - Removal of Elasticsearch 6.x support from codebase [#8979](elastic/cloud-on-k8s#8979) ##### Fixes - Upgrade master StatefulSets last when performing a version upgrade of Elasticsearch [#8871](elastic/cloud-on-k8s#8871) (issue: [#8429](elastic/cloud-on-k8s#8429)) - Fix race condition for pre-existing Stack Config Policy [#8928](elastic/cloud-on-k8s#8928) (issue: [#8912](elastic/cloud-on-k8s#8912)) - Do not set Kibana server.name [#8930](elastic/cloud-on-k8s#8930) (issue: [#8929](elastic/cloud-on-k8s#8929)) - Do not write `elasticsearch.k8s.elastic.co/managed-remote-clusters` when not necessary [#8932](elastic/cloud-on-k8s#8932) (issue: [#8781](elastic/cloud-on-k8s#8781)) - Cleanup orphaned secret mounts when removed from StackConfigPolicy [#8937](elastic/cloud-on-k8s#8937) (issue: [#8921](elastic/cloud-on-k8s#8921)) - Avoid duplicate error logging for generate GET operations on a GVK [#8957](elastic/cloud-on-k8s#8957) - Remove single master at a time upscale restriction [#8940](elastic/cloud-on-k8s#8940) (issue: [#8939](elastic/cloud-on-k8s#8939)) - AutoOps: Ignore deprecated ES clusters [#9008](elastic/cloud-on-k8s#9008) (issue: [#9000](elastic/cloud-on-k8s#9000)) - AutoOps: Require 9.2.1 for AutoOps agent [#9007](elastic/cloud-on-k8s#9007) (issue: [#9000](elastic/cloud-on-k8s#9000)) - Multi-SCP: Flip weight semantics - higher weight takes precedence [#9046](elastic/cloud-on-k8s#9046) ##### Documentation improvements - Update Google Cloud LoadBalancer recipe for new requirements [#8843](elastic/cloud-on-k8s#8843) - Fix minUnavailable typo in PDB documentation [#8898](elastic/cloud-on-k8s#8898) - Use GKE ComputeClass instead of DaemonSet for GKE AutoPilot [#8982](elastic/cloud-on-k8s#8982) - Adjust `vm.max_map_count` to [`1048576`](elastic/cloud-on-k8s@1048576) in GKE AutoPilot recipes [#8986](elastic/cloud-on-k8s#8986) - Remove support for Stack 7.17. [#9038](elastic/cloud-on-k8s#9038) ##### Dependency updates - Go 1.25.2 => 1.25.6 - github.com/KimMachineGun/automemlimit v0.7.4 => v0.7.5 - github.com/elastic/go-ucfg v0.8.9-0.20250307075119-2a22403faaea => v0.8.9-0.20251017163010-3520930bed4f - github.com/gkampitakis/go-snaps v0.5.15 => v0.5.19 - github.com/google/go-containerregistry v0.20.6 => v0.20.7 - github.com/googlecloudplatform/compute-class-api => v0.0.0-20251208134148-ae2e7936c1f8 - github.com/prometheus/common v0.67.1 => v0.67.5 - github.com/spf13/cobra v1.10.1 => v1.10.2 - go.elastic.co/apm/v2 v2.7.1 => v2.7.2 - go.uber.org/zap v1.27.0 => v1.27.1 - golang.org/x/crypto v0.40.0 => v0.46.0 - k8s.io/api v0.34.1 => v0.35.0 - k8s.io/apimachinery v0.34.1 => v0.35.0 - k8s.io/client-go v0.34.1 => v0.35.0 - k8s.io/utils v0.0.0-20250604170112-4c0f3b243397 => v0.0.0-20251002143259-bc988d571ff4 - sigs.k8s.io/controller-runtime v0.22.2 => v0.22.4 - sigs.k8s.io/controller-tools v0.19.0 => v0.20.0 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://gitea.alexlebens.dev/alexlebens/infrastructure/pulls/3682 Co-authored-by: Renovate Bot <renovate-bot@alexlebens.net> Co-committed-by: Renovate Bot <renovate-bot@alexlebens.net>

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [elastic/cloud-on-k8s](https://github.com/elastic/cloud-on-k8s) | minor | `v3.2.0` → `v3.3.0` | --- ### Release Notes <details> <summary>elastic/cloud-on-k8s (elastic/cloud-on-k8s)</summary> ### [`v3.3.0`](https://github.com/elastic/cloud-on-k8s/releases/tag/v3.3.0) [Compare Source](elastic/cloud-on-k8s@v3.2.0...v3.3.0) ### Elastic Cloud on Kubernetes 3.3.0 - [Quickstart guide](https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s#eck-quickstart) ##### Release Highlights ##### AutoOps Integration (Enterprise feature) ECK now supports integration with Elastic AutoOps through a new `AutoOpsAgentPolicy` custom resource. This allows you to instrument multiple Elasticsearch clusters at once for automated health monitoring and performance recommendations. The [AutoOps documentation](https://www.elastic.co/docs/deploy-manage/monitor/autoops) provides more details. ##### Elastic Package Registry Integration ECK now supports deploying and managing Elastic Package Registry (EPR) through a new `PackageRegistry` custom resource. This is particularly useful for air-gapped environments, enabling Kibana to reference a self-hosted registry instead of the public one. The [package registry documentation](https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/package-registry) provides more details. ##### Multiple Stack Configuration Policies composition support (Enterprise feature) ECK now includes support for multiple Stack Config Policies targeting the same Elasticsearch cluster or Kibana instance, using a weight-based priority system for deterministic policy composition. The [stack config policy documentation](https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/elastic-stack-configuration-policies) provides more details. ##### Features and enhancements - AutoOpsAgentPolicy support [#8941](elastic/cloud-on-k8s#8941) (issue: [#8789](elastic/cloud-on-k8s#8789)) - ElasticPackageRegistry support [#8800](elastic/cloud-on-k8s#8800) (issue: [#8925](elastic/cloud-on-k8s#8925)) - Stack Config Policies composition support [#8917](elastic/cloud-on-k8s#8917) - Use standard Kibana labels and Helm labels on the ECK Operator pod [#8840](elastic/cloud-on-k8s#8840) (issue: [#8584](elastic/cloud-on-k8s#8584)) - Add service customization support for Elasticsearch remote cluster server [#8892](elastic/cloud-on-k8s#8892) - Removal of Elasticsearch 6.x support from codebase [#8979](elastic/cloud-on-k8s#8979) ##### Fixes - Upgrade master StatefulSets last when performing a version upgrade of Elasticsearch [#8871](elastic/cloud-on-k8s#8871) (issue: [#8429](elastic/cloud-on-k8s#8429)) - Fix race condition for pre-existing Stack Config Policy [#8928](elastic/cloud-on-k8s#8928) (issue: [#8912](elastic/cloud-on-k8s#8912)) - Do not set Kibana server.name [#8930](elastic/cloud-on-k8s#8930) (issue: [#8929](elastic/cloud-on-k8s#8929)) - Do not write `elasticsearch.k8s.elastic.co/managed-remote-clusters` when not necessary [#8932](elastic/cloud-on-k8s#8932) (issue: [#8781](elastic/cloud-on-k8s#8781)) - Cleanup orphaned secret mounts when removed from StackConfigPolicy [#8937](elastic/cloud-on-k8s#8937) (issue: [#8921](elastic/cloud-on-k8s#8921)) - Avoid duplicate error logging for generate GET operations on a GVK [#8957](elastic/cloud-on-k8s#8957) - Remove single master at a time upscale restriction [#8940](elastic/cloud-on-k8s#8940) (issue: [#8939](elastic/cloud-on-k8s#8939)) - AutoOps: Ignore deprecated ES clusters [#9008](elastic/cloud-on-k8s#9008) (issue: [#9000](elastic/cloud-on-k8s#9000)) - AutoOps: Require 9.2.1 for AutoOps agent [#9007](elastic/cloud-on-k8s#9007) (issue: [#9000](elastic/cloud-on-k8s#9000)) - Multi-SCP: Flip weight semantics - higher weight takes precedence [#9046](elastic/cloud-on-k8s#9046) ##### Documentation improvements - Update Google Cloud LoadBalancer recipe for new requirements [#8843](elastic/cloud-on-k8s#8843) - Fix minUnavailable typo in PDB documentation [#8898](elastic/cloud-on-k8s#8898) - Use GKE ComputeClass instead of DaemonSet for GKE AutoPilot [#8982](elastic/cloud-on-k8s#8982) - Adjust `vm.max_map_count` to [`1048576`](elastic/cloud-on-k8s@1048576) in GKE AutoPilot recipes [#8986](elastic/cloud-on-k8s#8986) - Remove support for Stack 7.17. [#9038](elastic/cloud-on-k8s#9038) ##### Dependency updates - Go 1.25.2 => 1.25.6 - github.com/KimMachineGun/automemlimit v0.7.4 => v0.7.5 - github.com/elastic/go-ucfg v0.8.9-0.20250307075119-2a22403faaea => v0.8.9-0.20251017163010-3520930bed4f - github.com/gkampitakis/go-snaps v0.5.15 => v0.5.19 - github.com/google/go-containerregistry v0.20.6 => v0.20.7 - github.com/googlecloudplatform/compute-class-api => v0.0.0-20251208134148-ae2e7936c1f8 - github.com/prometheus/common v0.67.1 => v0.67.5 - github.com/spf13/cobra v1.10.1 => v1.10.2 - go.elastic.co/apm/v2 v2.7.1 => v2.7.2 - go.uber.org/zap v1.27.0 => v1.27.1 - golang.org/x/crypto v0.40.0 => v0.46.0 - k8s.io/api v0.34.1 => v0.35.0 - k8s.io/apimachinery v0.34.1 => v0.35.0 - k8s.io/client-go v0.34.1 => v0.35.0 - k8s.io/utils v0.0.0-20250604170112-4c0f3b243397 => v0.0.0-20251002143259-bc988d571ff4 - sigs.k8s.io/controller-runtime v0.22.2 => v0.22.4 - sigs.k8s.io/controller-tools v0.19.0 => v0.20.0 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).  Reviewed-on: https://gitea.alexlebens.dev/alexlebens/infrastructure/pulls/3685 Co-authored-by: Renovate Bot <renovate-bot@alexlebens.net> Co-committed-by: Renovate Bot <renovate-bot@alexlebens.net>

Fix minUnavailable typo in PDB

8309214

botelastic bot added the triage label Nov 6, 2025

frivoire changed the title ~~Fix minUnavailable typo in PDB~~ [doc] Fix minUnavailable typo in PDB Nov 6, 2025

barkbay reviewed Nov 27, 2025

View reviewed changes

barkbay added the >docs Documentation label Nov 27, 2025

botelastic bot removed the triage label Nov 27, 2025

barkbay added triage v3.3.0 labels Nov 27, 2025

botelastic bot removed the triage label Nov 27, 2025

Revert some (hack/* & docs/3*)

2ee0e0c

Merge branch 'main' into typo-pdb-minUnavailable

95cf878

barkbay approved these changes Dec 17, 2025

View reviewed changes

barkbay merged commit e02a29c into elastic:main Dec 17, 2025
10 checks passed

frivoire deleted the typo-pdb-minUnavailable branch December 17, 2025 13:02

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[doc] Fix minUnavailable typo in PDB#8898

[doc] Fix minUnavailable typo in PDB#8898
barkbay merged 3 commits intoelastic:mainfrom
frivoire:typo-pdb-minUnavailable

frivoire commented Nov 6, 2025

Uh oh!

prodsecmachine commented Nov 6, 2025 •

edited

Loading

Uh oh!

github-actions bot commented Nov 6, 2025 •

edited

Loading

Uh oh!

barkbay left a comment

Uh oh!

frivoire commented Dec 16, 2025 •

edited

Loading

Uh oh!

barkbay commented Dec 17, 2025

Uh oh!

barkbay commented Dec 17, 2025

Uh oh!

barkbay commented Dec 17, 2025

Uh oh!

Uh oh!

frivoire commented Dec 17, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

frivoire commented Nov 6, 2025

Uh oh!

prodsecmachine commented Nov 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Snyk checks have passed. No issues have been found so far.

Uh oh!

github-actions bot commented Nov 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔍 Preview links for changed docs

Uh oh!

barkbay left a comment

Choose a reason for hiding this comment

Uh oh!

frivoire commented Dec 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

barkbay commented Dec 17, 2025

Uh oh!

barkbay commented Dec 17, 2025

Uh oh!

barkbay commented Dec 17, 2025

Uh oh!

Uh oh!

frivoire commented Dec 17, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

prodsecmachine commented Nov 6, 2025 •

edited

Loading

github-actions bot commented Nov 6, 2025 •

edited

Loading

frivoire commented Dec 16, 2025 •

edited

Loading