fix(maxprocs): treat ConfigureMaxProcs error as non-fatal (#7655)

When KEDA runs in environments where /sys/fs/cgroup/cpu.max is not
readable (e.g. EKS auto-mode, restricted SecurityContexts), maxprocs.Set()
returns a permission error and KEDA crashes on startup.

The Go runtime handles GOMAXPROCS sensibly without explicit configuration,
so this error should not be fatal. Log it as a warning and continue
startup.

Fixes #7653

Signed-off-by: ManvithaP-hub <62259625+ManvithaP-hub@users.noreply.github.com>

Author: ManvithaP-hub

cmd/adapter/main.go

@@ -288,10 +288,8 @@ func main() {
 		return
 	}
 
-	err = kedautil.ConfigureMaxProcs(setupLog)
-	if err != nil {
-		setupLog.Error(err, "failed to set max procs")
-		return
+	if err := kedautil.ConfigureMaxProcs(setupLog); err != nil {
+		setupLog.Info("failed to set max procs, using default GOMAXPROCS", "error", err)
 	}
 
 	kedaProvider, err := cmd.makeProvider(ctx)

cmd/operator/main.go

@@ -124,10 +124,8 @@ func main() {
 	ctrl.SetLogger(zap.New(zap.UseFlagOptions(&opts)))
 	ctx := ctrl.SetupSignalHandler()
 
-	err := kedautil.ConfigureMaxProcs(setupLog)
-	if err != nil {
-		setupLog.Error(err, "failed to set max procs")
-		os.Exit(1)
+	if err := kedautil.ConfigureMaxProcs(setupLog); err != nil {
+		setupLog.Info("failed to set max procs, using default GOMAXPROCS", "error", err)
 	}
 
 	namespaces, err := kedautil.GetWatchNamespaces()

cmd/webhooks/main.go

@@ -78,12 +78,9 @@ func main() {
 
 	ctrl.SetLogger(zap.New(zap.UseFlagOptions(&opts)))
 
-	err := kedautil.ConfigureMaxProcs(setupLog)
-	if err != nil {
-		setupLog.Error(err, "failed to set max procs")
-		os.Exit(1)
+	if err := kedautil.ConfigureMaxProcs(setupLog); err != nil {
+		setupLog.Info("failed to set max procs, using default GOMAXPROCS", "error", err)
 	}
-
 	ctx := ctrl.SetupSignalHandler()
 
 	cfg := ctrl.GetConfigOrDie()