From b7511a85de0fdb5a236076c49f1ffb728cccc4c1 Mon Sep 17 00:00:00 2001
From: John Mazzitelli <mazz@redhat.com>
Date: Mon, 2 May 2022 16:16:29 -0400
Subject: [PATCH] be able to set the allowAdHocContainers value

---
 kiali-operator/templates/deployment.yaml | 2 ++
 kiali-operator/values.yaml               | 4 ++++
 2 files changed, 6 insertions(+)

diff --git a/kiali-operator/templates/deployment.yaml b/kiali-operator/templates/deployment.yaml
index 32be341..ac775b7 100644
--- a/kiali-operator/templates/deployment.yaml
+++ b/kiali-operator/templates/deployment.yaml
@@ -69,6 +69,8 @@ spec:
           value: {{ .Values.allowAdHocKialiNamespace | quote }}
         - name: ALLOW_AD_HOC_KIALI_IMAGE
           value: {{ .Values.allowAdHocKialiImage | quote }}
+        - name: ALLOW_AD_HOC_CONTAINERS
+          value: {{ .Values.allowAdHocContainers | quote }}
         - name: PROFILE_TASKS_TASK_OUTPUT_LIMIT
           value: "100"
         - name: ANSIBLE_DEBUG_LOGS
diff --git a/kiali-operator/values.yaml b/kiali-operator/values.yaml
index ee34868..751ffb8 100644
--- a/kiali-operator/values.yaml
+++ b/kiali-operator/values.yaml
@@ -67,6 +67,10 @@ allowAdHocKialiNamespace: true
 # You may want to disable this if you do not want users to install their own Kiali images.
 allowAdHocKialiImage: false
 
+# allowAdHocContainers tells the operator to allow a user to be able to install additional pod containers to the Kiali pod.
+# In other words, it will allow the Kiali CR spec.deployment.additional_pod_containers_yaml to be configured by the user.
+allowAdHocContainers: false
+
 # For what a Kiali CR spec can look like, see:
 # https://github.com/kiali/kiali-operator/blob/master/deploy/kiali/kiali_cr.yaml
 cr: