add profiler to kiali server

crd-docs/cr/kiali.io_v1alpha1_kiali.yaml

@@ -464,6 +464,8 @@ spec:
           skip_verify: false
           tls_enabled: false
     port: 20001
+    profiler:
+      enabled: false
     web_fqdn: ""
     web_history_mode: ""
     web_port: ""

crd-docs/crd/kiali.io_kialis.yaml

@@ -1357,6 +1357,13 @@ spec:
                   port:
                     description: "The port that the server will bind to in order to receive console and API requests."
                     type: integer
+                  profiler:
+                    description: "Controls the internal profiler used to debug the internals of Kiali"
+                    type: object
+                    properties:
+                      enabled:
+                        description: "When 'true', the profiler will be enabled and accessible at /debug/pprof/ on the Kiali endpoint."
+                        type: boolean
                   web_fqdn:
                     description: "Defines the public domain where Kiali is being served. This is the 'domain' part of the URL (usually it's a fully-qualified domain name). For example, `kiali.example.org`. When empty, Kiali will try to guess this value from HTTP headers. On non-OpenShift clusters, you must populate this value if you want to enable cross-linking between Kiali instances in a multi-cluster setup."
                     type: string

deploy/kiali/kiali_cr_dev.yaml

@@ -28,3 +28,7 @@ spec:
     service_type: $SERVICE_TYPE
     logger:
       log_level: info
+
+  server:
+    profiler:
+      enabled: true

roles/default/kiali-deploy/defaults/main.yml

@@ -348,6 +348,8 @@ kiali_defaults:
           skip_verify: false
           tls_enabled: false
     port: 20001
+    profiler:
+      enabled: false
     web_fqdn: ""
     web_history_mode: ""
     web_port: ""