Fix leader election config in the helm chart

[chotiwat]

What type of PR is this?

/kind bug

What this PR does / why we need it:

The default leader election for kube-scheduler will try to acquire the kube-system/kube-scheduler lease, which is what the default scheduler uses. This prevents our custom scheduler from ever acquiring the leader lease until the leader loses the lease, at which point it could cause undesirable behavior by stealing the lease from the default scheduler. We should be using a separate lease if we want to run the custom scheduler alongside the default scheduler.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

The Helm chart has been updated to use a separate lease from the default scheduler for leader election (when enabled). This allows the deployed scheduler to run alongside the default one. The new lease name will be the same as the `scheduler.name` value.

[k8s-ci-robot]

Hi @chotiwat. 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. Regular contributors should join the org to skip this step.

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.

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.

[netlify]

✅ Deploy Preview for kubernetes-sigs-scheduler-plugins canceled.

Name	Link
🔨 Latest commit	57333b5
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-scheduler-plugins/deploys/6722d72e17add40008285903

[chotiwat]

Based on:

• https://github.com/aws-samples/custom-scheduler-eks/blob/01a576e2aa45b1bf779ea1750a541b6ecb6beb9e/deploy/charts/custom-scheduler-eks/templates/configmap.yaml#L31-L32
• https://kubernetes.io/docs/reference/config-api/kube-scheduler-config.v1/#LeaderElectionConfiguration

[Huang-Wei]

/ok-to-test

[Huang-Wei]

@chotiwat thanks for the PR. Could you add a brief stanza in the release-notes section in the PR description?

[chotiwat]

Done @Huang-Wei

[Huang-Wei]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chotiwat, Huang-Wei

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Huang-Wei]

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