KIRY4 edited a comment on issue #14714:
URL: https://github.com/apache/airflow/issues/14714#issuecomment-879794991


   Hello @kaxil  ! We have a similar problem. But there are some differences. 
We are using Azure Kubernetes Service and for dags logs plugins and our 
custom_operators we are using Kubernetes PVC's with Azure file shares under the 
hood. Also we are using community Helm chart: 
https://github.com/airflow-helm/charts/tree/main/charts/airflow
   
   After uploading custom operator on mounted as PV/PVC Azure file shares I 
expect to have it accessible from Airflow DAGs.
   I have 2 folders: /opt/airflow/plugins and /opt/airflow/custom_operator.
   
   Examples of imports (for test I jumped into Web POD):
   
   From plugins/ I can call custom opertor like - from table_migration_operator 
import TableMigrationOperator
   From custom_operator/ - from custom_operator.save_result_operator import 
SaveResultOperator
   <img width="1484" alt="image" 
src="https://user-images.githubusercontent.com/42247943/125605632-82e702f0-92c7-42c5-8752-cd66b9d22f88.png";>
   Inside POD from Python everything works fine.
   
   
   What I'm getting in UI:
   <img width="642" alt="image" 
src="https://user-images.githubusercontent.com/42247943/125605859-a6c170c9-c61d-4d29-9514-e32a9b2c9d42.png";>
   
   
   
    
   
   Both ways are not working in UI until webserver will not be restarted 
(restart pod with webserver). After the restart everything is fine.
   
   Airflow versions: 2.1.0 and 2.1.1
   
   
PATH=/home/airflow/.local/bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
   
   
PYTHONPATH=/opt/airflow:/opt/airflow/dags:/opt/airflow/logs:/opt/airflow/plugins:/opt/airflow/custom_operator:/opt/airflow/jars
   
   AIRFLOW__WEBSERVER__RELOAD_ON_PLUGIN_CHANGE=True


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