Proposal

Add new options for configuring the leader election lease, including:

KEDA_HTTP_OPERATOR_LEADER_ELECTION_LEASE_DURATION
KEDA_HTTP_OPERATOR_LEADER_ELECTION_RENEW_DEADLINE
KEDA_HTTP_OPERATOR_LEADER_ELECTION_RETRY_PERIOD

Something similar to kedacore/keda#3430

Use-Case

I have these errors when the GKE kube master is upgrading (currently 1.32.6):

failed to renew lease ns-keda/http-add-on.keda.sh: timed out waiting for the condition
error retrieving resource lock ns-keda/http-add-on.keda.sh: Get "https://192.168.64.1:443/apis/coordination.k8s.io/v1/namespaces/ns-keda/leases/http-add-on.keda.sh?timeout=5s": context deadline exceeded
Failed to update lock optimitically: Put "https://192.168.64.1:443/apis/coordination.k8s.io/v1/namespaces/ns-keda/leases/http-add-on.keda.sh?timeout=5s": net/http: request canceled (Client.Timeout exceeded while awaiting headers), falling back to slow path

This triggers a restart of the operator.

Is this a feature you are interested in implementing yourself?

No

Anything else?

No response