[GitHub] [airflow] potiuk commented on issue #27577: Allow for templating of pod-template.yaml at service start time or pod creation

[GitBox <gi...@apache.org>]

potiuk commented on issue #27577:
URL: https://github.com/apache/airflow/issues/27577#issuecomment-1312955553

   You have not explained "WHEN" the pod_template would change. From what I understand, you want to do it at service deployment time. And seems this is what you want to do - either on service deployment time or based on some manually triggered  event (which would be some kind of event reconfiguring the whole cluster). What you really need is a solution for your deployment not "airflow feature".
   
   What I think you shuld do is to simply use whatever k8s already provides - you are really talking about config map that will be mounted as your pod_template_file:  https://kubernetes.io/docs/concepts/storage/volumes/#configmap
   
   You can mount this config map as a volume/folder available for all pods that need them and then you can use absolutely standard k8s mechanism to apply any changes to it (kubectl apply) including pre-processing it via jinja as you wish (you do not need sed, you can simply use jinja2 CLI for that https://pypi.org/project/jinja2-cli/
   
   Converting it into discussion, but I suggest you try this first and see if you can make it works.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org