simplify validation by removing redundant check

Signed-off-by: Nader Ziada <[email protected]>

Author: nader-ziada

docs/operate.md

@@ -74,12 +74,12 @@ Optional variables
 
 ## Configuring the KEDA HTTP Add-on Operator
 
-## Leader Election Timing
+### Leader Election Timing
 
 When running multiple replicas of the operator for high availability, you can configure the leader election timing parameters:
 
 - **`KEDA_HTTP_OPERATOR_LEADER_ELECTION_LEASE_DURATION`** - Duration that non-leader candidates will wait to force acquire leadership. Default: `15s` (Kubernetes default)
-- **`KEDA_HTTP_OPERATOR_LEADER_ELECTION_RENEW_DEADLINE`** - Duration that the acting leader will retry refreshing leadership before giving up. Default: `10s` (Kubernetes default)
+- **`KEDA_HTTP_OPERATOR_LEADER_ELECTION_RENEW_DEADLINE`** - Duration that the acting leader will retry renewing leadership before giving up. Default: `10s` (Kubernetes default)
 - **`KEDA_HTTP_OPERATOR_LEADER_ELECTION_RETRY_PERIOD`** - Duration the LeaderElector clients should wait between tries of actions. Default: `2s` (Kubernetes default)
 
 Example usage in deployment:

pkg/util/env_resolver.go

@@ -101,9 +101,6 @@ func ValidateLeaderElectionConfig(leaseDuration, renewDeadline, retryPeriod *tim
 	if renew <= retry {
 		return fmt.Errorf("renew deadline (%v) must be greater than retry period (%v)", renew, retry)
 	}
-	if lease <= retry {
-		return fmt.Errorf("lease duration (%v) must be greater than retry period (%v)", lease, retry)
-	}
 
 	return nil
 }