Webhook leader election timings are not configurable via Helm chart

[AxcelBlaze003]

What happened?

• ✋ I have searched the open/closed issues and my issue is not listed.

Webhook leader election timings are not configurable via Helm chart

Problem

The Spark Operator webhook enables leader election, but the Helm chart does not expose configuration for the leader election timing parameters (leaseDuration, renewDeadline, and retryPeriod).

In Kubernetes environments where API server requests may occasionally take longer to complete, the default leader election timings may not be sufficient. This can cause lease renewal requests to time out, resulting in leader election loss and webhook shutdown.

During leader election renewal, the webhook may encounter errors such as:

Failed to update lock optimistically: Client.Timeout exceeded while awaiting headers
error retrieving resource lock: context deadline exceeded
failed to renew lease: context deadline exceeded
Failed to start manager: leader election lost

Expected behavior

The Helm chart should expose the webhook leader election timing parameters so that operators can tune them according to their cluster characteristics while preserving the existing default behavior.

Example configuration:

webhook:
  leaderElection:
    enable: true
    leaseDuration: 15s
    renewDeadline: 10s
    retryPeriod: 2s

Motivation

Making these parameters configurable improves the stability of the webhook in clusters with slower API servers or higher control-plane latency without changing the default behavior for existing users.

Reproduction Code

No response

Actual behavior

No response

Environment & Versions

• Kubernetes Version:
• Spark Operator Version:
• Apache Spark Version:

Additional context

No response

Impacted by this bug?

Give it a 👍 We prioritize the issues with most 👍

[github-actions]

🎉 Welcome to the Kubeflow Spark Operator! 🎉

Thanks for opening your first issue! We're happy to have you as part of our community 🚀

Here's what happens next:

• Our team will review your issue soon!
• If you'd like to contribute to this issue, check out our Contributing Guide for repo-specific guidelines and the Kubeflow Contributor Guide for general community standards.

Join the community:

• Slack: Join our #kubeflow-spark-on-kubernetes Slack channel.

Feel free to ask questions in the comments if you need any help or clarification!
Thanks again for contributing to Kubeflow! 🙏