Support BENCHMARK_OPERATOR_NAMESPACE for OpenShift CI (#1184)

When set, use BENCHMARK_OPERATOR_NAMESPACE for workload/operator namespace
so CI can leave NAMESPACE as the job namespace for the result secret.
Fixes permission error: framework cannot write secret in benchmark-operator
on the build cluster.

Co-authored-by: Arpit Sharma <arpsharm@arpsharm-thinkpadx1carbongen9.bengluru.csb>

Author: arpsharm

benchmark_runner/main/environment_variables.py

@@ -136,9 +136,13 @@ def __init__(self):
             'hammerdb': 4.0
         }
 
-        # Set namespace based on workload
+        # Set namespace based on workload.
+        # BENCHMARK_OPERATOR_NAMESPACE is used when set (e.g. OpenShift CI) so the app targets that
+        # namespace for workload/operator while NAMESPACE can remain the job namespace for the framework.
         base_workload = self._environment_variables_dict['workload'].split('_')[0]
-        if EnvironmentVariables.get_env('NAMESPACE'):
+        if EnvironmentVariables.get_env('BENCHMARK_OPERATOR_NAMESPACE'):
+            self._environment_variables_dict['namespace'] = EnvironmentVariables.get_env('BENCHMARK_OPERATOR_NAMESPACE')
+        elif EnvironmentVariables.get_env('NAMESPACE'):
             self._environment_variables_dict['namespace'] = EnvironmentVariables.get_env('NAMESPACE')
         elif base_workload in self._environment_variables_dict['workload_namespaces']:
             default_namespace = self._environment_variables_dict['workload_namespaces'][base_workload]