Skip to content

Allow configuring the calico-typha PodDisruptionBudget#4729

Open
caseydavenport wants to merge 5 commits into
tigera:masterfrom
caseydavenport:casey-typha-pdb-config
Open

Allow configuring the calico-typha PodDisruptionBudget#4729
caseydavenport wants to merge 5 commits into
tigera:masterfrom
caseydavenport:casey-typha-pdb-config

Conversation

@caseydavenport
Copy link
Copy Markdown
Member

@caseydavenport caseydavenport commented Apr 20, 2026

Adds a new Installation.Spec.TyphaPodDisruptionBudget field that lets users override minAvailable, maxUnavailable, and unhealthyPodEvictionPolicy on the operator-managed calico-typha PDB. Fields left unset keep the existing operator default of maxUnavailable: 1. The PDB's selector stays operator-controlled.

Also adds a generic PodDisruptionBudgetOverride type and a matching ApplyPodDisruptionBudgetOverrides helper alongside the existing ApplyDeploymentOverrides / ApplyDaemonSetOverrides / ApplyJobOverrides, so future components (e.g. tigera-apiserver) can reuse the same shape.

Fixes projectcalico/calico#9237

Added `Installation.Spec.TyphaPodDisruptionBudget` to allow configuring the `calico-typha` PodDisruptionBudget, including `unhealthyPodEvictionPolicy`.

@caseydavenport caseydavenport marked this pull request as ready for review May 13, 2026 17:57
@caseydavenport caseydavenport requested a review from a team as a code owner May 13, 2026 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feature request: Allow for the Calico Typha PDB to be configured with new fields

2 participants