ashb commented on code in PR #46860:
URL: https://github.com/apache/airflow/pull/46860#discussion_r1961608501


##########
providers/cncf/kubernetes/src/airflow/providers/cncf/kubernetes/pod_generator.py:
##########
@@ -341,18 +350,45 @@ def construct_pod(
                     run_id=run_id,
                 ),
             ),
-            spec=k8s.V1PodSpec(
-                containers=[
-                    k8s.V1Container(
-                        name="base",
-                        args=args,
-                        image=image,
-                        env=[k8s.V1EnvVar(name="AIRFLOW_IS_K8S_EXECUTOR_POD", 
value="True")],
-                    )
-                ]
-            ),
         )
 
+        podspec = k8s.V1PodSpec(
+            containers=[main_container],
+        )
+
+        if content_json_for_volume:
+            input_file_path = "/tmp/execute/input.json"
+            execute_volume = V1Volume(
+                name="execute-volume",
+                empty_dir=V1EmptyDirVolumeSource(),
+            )
+
+            execute_volume_mount = V1VolumeMount(
+                name="execute-volume",
+                mount_path="/tmp/execute",
+                read_only=False,
+            )
+
+            init_container = k8s.V1Container(
+                name="init-container",
+                image="busybox",
+                command=["/bin/sh", "-c", f"echo '{content_json_for_volume}' > 
{input_file_path}"],
+                volume_mounts=[execute_volume_mount],
+            )

Review Comment:
   Okay there isn't any way (configmap would be the only one, but we don't 
really want to do that) I can find
   
   So I think rather than doing this as an init container it might be better if 
we put the input in a env var instead? 🤔 



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to