[Feature]: Update `manager.yaml` to resolve multi operator controllers in the same cluster

Duplicates

I have searched the existing issues

Summary 💡

The current configuration of the operator controller manager contains labels that cause incorrect pod references when multiple operator controller managers are present. The labels need to be updated to ensure proper identification and management of pods by different operator controllers.

:construction: track operators:

[x] zncdatadev/commons-operator#28
[x] zncdatadev/listener-operator#73
[x] zncdatadev/secret-operator#77
[x] zncdatadev/trino-operator#109 (trino)
[x] zncdatadev/zookeeper-operator#51
[x] zncdatadev/hdfs-operator#43
[x] zncdatadev/kafka-operator/pull/53
[x] zncdatadev/hbase-operator/pull/40
[x] zncdatadev/superset-operator/pull/41
[x] zncdatadev/dolphinscheduler-operator/pull/44
[x] zncdatadev/spark-k8s-operator/pull/90
[x] zncdatadev/hive-operator/pull/92

Examples 🌈

The following changes are proposed to the config/manager/manager.yaml file to correct the label issue:

diff --git a/config/manager/manager.yaml b/config/manager/manager.yaml
index 38a0b8e..2ebb1c3 100644
--- a/config/manager/manager.yaml
+++ b/config/manager/manager.yaml
@@ -18,23 +18,25 @@ metadata:
   namespace: system
   labels:
     control-plane: controller-manager
-    app.kubernetes.io/name: deployment
+    app.kubernetes.io/name: hdfs-operator
     app.kubernetes.io/instance: controller-manager
     app.kubernetes.io/component: manager
-    app.kubernetes.io/created-by: hdfs-operator
+    app.kubernetes.io/created-by: operator-lifecycle-manager
     app.kubernetes.io/part-of: hdfs-operator
     app.kubernetes.io/managed-by: kustomize
 spec:
   selector:
     matchLabels:
-      control-plane: controller-manager
+      control-plane: hdfs-operator
+      app.kubernetes.io/name: hdfs-operator
   replicas: 1
   template:
     metadata:
       annotations:
         kubectl.kubernetes.io/default-container: manager
       labels:
-        control-plane: controller-manager
+        control-plane: hdfs-operator
+        app.kubernetes.io/name: hdfs-operator
     spec:
       # TODO(user): Uncomment the following code to configure the nodeAffinity expression

Motivation 🔦

When multiple operator controller managers are deployed in the same cluster, the current labels in the configuration file cause conflicts due to ambiguous references. Specifically, the labels control-plane: controller-manager and app.kubernetes.io/name: deployment are too generic and can lead to pods being incorrectly managed by the wrong operator controller. By updating the labels to more specific values such as control-plane: hdfs-operator and app.kubernetes.io/name: hdfs-operator, we can ensure that pods are correctly referenced and managed by the appropriate operator controller manager, thus preventing conflicts and ensuring the stability of the deployment.

zncdatadev / trino-operator