Start migration to leases for leader election

[johngmyers]

Issue

N/A

Description

Configures leader election to use both ConfigMaps and Leases.

Migration to leases is long overdue. The most recent version of controller-runtime appears to not support using only ConfigMaps.

Checklist

• Added tests that cover your change (if possible)
• Added/modified documentation as required (such as the README.md, or the docs directory)
• Manually tested
• Made sure the title of the PR is a good description that can go into the release notes

BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯

• Backfilled missing tests for code in same general area 🎉
• Refactored something and made the world a better place 🌟

[codecov-commenter]

Codecov Report

Base: 54.01% // Head: 54.01% // No change to project coverage 👍

Coverage data is based on head (33dd23d) compared to base (d9c2a77).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2993   +/-   ##
=======================================
  Coverage   54.01%   54.01%           
=======================================
  Files         144      144           
  Lines        8312     8312           
=======================================
  Hits         4490     4490           
  Misses       3494     3494           
  Partials      328      328           

Impacted Files	Coverage Δ
pkg/config/runtime_config.go	0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[kishorj]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johngmyers, kishorj

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 [kishorj]

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

[sj26]

I have a fresh install of the aws load balancer controller on a fresh eks cluster but it's stuck at this log entry:

Searching around I see a lot of the same problem, but no clear guidance on solutions or diagnostics.

How do I diagnose where this is going wrong?

kubectl version
Client Version: v1.30.7
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.32.2-eks-bc803b4

helm list --namespace kube-system
NAME                            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                                   APP VERSION
aws-load-balancer-controller    kube-system     1               2025-03-20 14:22:57.85533 +1100 AEDT    deployed        aws-load-balancer-controller-1.12.0     v2.12.0

Sorry if this is the wrong place. Please point at docs if there is somewhere I need to look, for future travellers as well 🙏

Edit: Turns out this may have been a red herring - it seems like the controller got past that state but doesn't log that the lease is obtained, or the logs are presented out of order.