airflow-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Lane <>
Subject Re: Pod template substitutions not working
Date Sat, 06 Feb 2021 02:02:29 GMT
FWIW, I was able to get a template working, though I’m still left with some questions. First,
I upgraded to Airflow 2.0.0 largely because I saw it had logging statements. Second, I was
only able to specify a pod_template_file in the scheduler config. The KubernetesPodOperator
parameter doesn’t work. Similarly, overriding the pod image does not work by using the KPO’s
image constructor parameter. I had to use the executor_config/pod_override method.

Am I missing the point of having those parameters in the KPO constructor? Are these legacy
parameters that don’t work anymore and should be removed?


From: Peter Lane <>
Reply-To: "" <>
Date: Thursday, February 4, 2021 at 5:55 PM
To: "" <>
Subject: Re: Pod template substitutions not working

Hi Daniel,

Thanks for responding. Sorry for the months-long delay. Had other stuff I had to focus on.

I am using Airflow 1.10.12.

Here is a link to a public repo with the scheduler logs and template file:<>

The Pod gives me the message “Failed to pull image "dummy_image": rpc error: code = Unknown
desc = repository not found: does not exist or no pull access”.  The
most recent run was an excerpt from this example:<>
It’s in the repo as well as My understanding was that this should work as
well with the template, substituting the image parameter for the dummy base image in the template.
I also included my scheduler config YAML if that helps. Any help would be appreciated.


From: Daniel Imberman <>
Reply-To: "" <>
Date: Monday, December 7, 2020 at 11:37 AM
To: "" <>
Cc: "" <>
Subject: Re: Pod template substitutions not working

[Warning External Email]
Hi Peter,

What version of airflow are you using? Can you post a link to your pod_template_file and the
via Newton Mail<>

On Tue, Dec 1, 2020 at 4:19 PM, Peter Lane <> wrote:
I am having a terribly difficult time getting Airflow to run on Kubernetes (OpenShift, to
be exact. My current hurdle is that I am able to specify a custom worker pod template, but
the default container image is not being replaced when I set the AIRFLOW__KUBERNETES__WORKER_CONTAINER_REPOSITORY
and AIRFLOW__KUBERNETES__WORKER_CONTAINER_TAG in the deployment environment. I directly customized
the git-sync example, and my init container works fine. The base container image can’t get
pulled because the default value for the image (dummy_image) is still in the pod configuration.
Is there some magic flag I need to set or something to get this to work?


View raw message