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

[peterabarr]

Expected Behavior

Currently the calico-typha PDB is controlled by the Installation custom resource from Tigera Operator. I would like an option to be able to configure it so that it can use unhealthyPodEvictionPolicy.

Current Behavior

It does not seem possible to add new fields to the calico-typha PDB.

Possible Solution

Steps to Reproduce (for bugs)

1. 2. 3. 4.

Context

I want to try out unhealthyPodEvictionPolicy as it's a new feature but currently it doesn't seem possible with the calico-typha PDB.

Your Environment

• Calico version: v3.28.1
• Orchestrator version (e.g. kubernetes, mesos, rkt): Kubernetes 1.30
• Operating System and version: Linux
• Link to your project (optional):

[caseydavenport]

@peterabarr have you tried creating a second PDB that selects Typha? I haven't tried it myself, but the API seems to suggest that you can have multiple PDBs selecting the same pods.