fix(chart): set unhealthyPodEvictionPolicy on the PDB

[DsThakurRawat]

Description

Sets unhealthyPodEvictionPolicy (default AlwaysAllow) on the chart's PodDisruptionBudget so unhealthy pods do not block voluntary evictions indefinitely. Rendered only on clusters >= 1.27 where the field is supported, and omitted when empty. Found via kube-linter on the fully-rendered chart.

Related Issue

None

Type of Change

/kind feature

Testing

• helm unittest --strict: 43/43 pass (5 runs), including 2 new PDB cases
• helm lint: clean
• helm template on kube 1.25/1.26 omits the field, on 1.29 renders it
• kube-linter finding that motivated this no longer fires; hack/verify-chart-drift.sh clean

Checklist

• make test passes
• make lint passes

Does this PR introduce a user-facing change?

NONE

Generative AI Usage Disclosure

• No AI tools were used
• AI tools were used (complete below)

How they were used:
AI assistance drafted the template stanza, values/docs rows, and unittest cases. Every line was verified by local runs before pushing: helm unittest (5x), lint, multi-version template renders, kube-linter, chart drift check.

[netlify]

✅ Deploy Preview for node-readiness-controller canceled.

Name	Link
🔨 Latest commit	d1b7ee0
🔍 Latest deploy log	https://app.netlify.com/projects/node-readiness-controller/deploys/6ab8ddad8b13c40008f1de5e

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: DsThakurRawat
Once this PR has been reviewed and has the lgtm label, please assign mrunalp for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kubernetes-prow]

Hi @DsThakurRawat. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[DsThakurRawat]

This looks good to me