allow configuring leader-lease-renew-deadline

[rahulait]

Description

We currently configure leader-lease-renew-deadline with installs using OLM bundle. This change allows us to configure the same with helm installs as well.

See #2767 (comment)

Checklist

• No secrets, sensitive information, or unrelated changes
• Lint checks passing (make lint)
• Generated assets in-sync (make validate-generated-assets)
• Go mod artifacts in-sync (make validate-modules)
• Test cases are added for new code paths

Testing

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: QUIET

Plan: Enterprise

Run ID: 7731b840-8683-467f-8ca3-b86e88ed968f

📥 Commits

Reviewing files that changed from the base of the PR and between 9f85a2a and 0d25508.

📒 Files selected for processing (2)

• deployments/gpu-operator/templates/operator.yaml
• deployments/gpu-operator/values.yaml

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

📝 Walkthrough

Walkthrough

The GPU Operator Helm chart now documents an optional leader-election renewal deadline. When .Values.operator.leaderElection.renewDeadline is set, the operator Deployment template adds --leader-lease-renew-deadline with the configured value.

Priority: ⬇️ Low

Merge Risk: ⚪ Minimal · up to 0d255

The optional Helm setting is documented and rendered consistently without introducing a merge-blocking risk.

---

_{Comment @coderabbitai help to get the list of available commands.}

[devin-ai-integration]

Devin Review found 1 potential issue.

[rahulait]

/cherry-pick release-26.7

[github-actions]

🤖 Backport PR created for release-26.7: #2902 ✅