mgorsk1 opened a new issue #16850:
URL: https://github.com/apache/airflow/issues/16850


   **Description**
   
   Since Airflow 2 we get a lot of customization options for pods spawned using 
`KubernetesPodOperator`. There is, however, one area in which nothing has 
changed and it's `xcom_sidecar_container`. Currently, all of the specs for it 
are hardcoded in `PodDefaults` class.
   
   This issue is meant to start discussion and to possibly shape the end 
solution enabling configuration of xcom side container.
   
   **Use case / motivation**
   
   We are running on self-hosted k8s with own docker repository (JFrog 
artifactory) and in our current setup we are required to spawn pods using full 
path to the repo - we cannot do `docker pull alpine` but need to do `docker 
pull arficatory.domain/registry/alpine`.
   
   Currently we workaround this by subclassing KubernetesPodOperator and 
overriding this method:
   
   ```
       def create_pod_request_obj(self) -> k8s.V1Pod:
           pod = super(KubernetesPodOperator, self).create_pod_request_obj()
   
           for container in pod.spec.containers:
               if container.image == 'alpine':
                   container.image = 'artifactory.domain/registry/alpine'
   ```
   
   but it's not very elegant solution.
   
   **Are you willing to submit a PR?**
   
   Yes, but could use some points, discussion on what would be the acceptable 
target solution.
   
   **Related Issues**
   
   n/a
   


-- 
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