operator edp-keycloak-operator (1.24.0) (#5904)

Signed-off-by: Sergiy Kulanov <[email protected]>

Author: SergK

operators/edp-keycloak-operator/1.24.0/manifests/client-secret-authorization-sample_v1_secret.yaml

@@ -0,0 +1,6 @@
+apiVersion: v1
+data:
+  client-secret-key: cGFzc3dvcmQ=
+kind: Secret
+metadata:
+  name: client-secret-authorization-sample

operators/edp-keycloak-operator/1.24.0/manifests/client-secret-policy-sample_v1_secret.yaml

@@ -0,0 +1,6 @@
+apiVersion: v1
+data:
+  client-secret-key: cGFzc3dvcmQ=
+kind: Secret
+metadata:
+  name: client-secret-policy-sample

operators/edp-keycloak-operator/1.24.0/manifests/edp-keycloak-operator-manager-config_v1_configmap.yaml

@@ -0,0 +1,18 @@
+apiVersion: v1
+data:
+  controller_manager_config.yaml: "apiVersion: controller-runtime.sigs.k8s.io/v1alpha1\nkind:
+    ControllerManagerConfig\nhealth:\n  healthProbeBindAddress: :8081\nmetrics:\n
+    \ bindAddress: 127.0.0.1:8080\nwebhook:\n  port: 9443\nleaderElection:\n  leaderElect:
+    true\n  resourceName: edp-keycloak-operator-lock\n#   leaderElectionReleaseOnCancel
+    defines if the leader should step down volume \n#   when the Manager ends. This
+    requires the binary to immediately end when the\n#   Manager is stopped, otherwise,
+    this setting is unsafe. Setting this significantly\n#   speeds up voluntary leader
+    transitions as the new leader don't have to wait\n#   LeaseDuration time first.\n#
+    \  In the default scaffold provided, the program ends immediately after \n#   the
+    manager stops, so would be fine to enable this option. However, \n#   if you are
+    doing or is intended to do any operation such as perform cleanups \n#   after
+    the manager stops then its usage might be unsafe.\n#   leaderElectionReleaseOnCancel:
+    true\n"
+kind: ConfigMap
+metadata:
+  name: edp-keycloak-operator-manager-config