GitHub user potiuk added a comment to the discussion: DockerOperator SSL 
Verification

I converted it into a discussion. It looks like you have an issue with 
self-signed certificates for your infrastructure. That's what usually "failed 
to verify certificate: x509: certificate signed by unknown authority" unless 
you have some misconfiguration of your infrastructure and for example remove 
all "built-in" certificates that are coming either from system of yours or 
Python.

It's not really an "airflow" issue - it's more how you are configure SSL 
certificates used by Python packages to connect to the servers - you seem to 
have self-signed certificate or certificate signed by authority that is not in 
the "regular" certificates that Python uses. There are quite a few issues here 
and you can google it as well on how to make sure that Python certificates 
contain your self-signed certificates (look for self-signed here in the issues 
- you will likely find a few things you can try in your deployment - also if 
you ask for configuring self-signed certificates to be used by Python in Google.

Depending on Python version and operting system - there might be different 
solutions and different ways as far as I know.

Generally also better solution is to pay for a good certificate that is widely 
recognized by defaullt certification checks built-in. Paying for certificates 
or even using let's encrypt quickly rotating certificates on your server is a 
good approach. Especially if you consider thaat you are now trying to offload 
that to volunteers working in their free time mostly -  developing software 
that you can use for free.  It would seem resonable that your company can at 
least have some good certificates, or maybe instead find a way how to make 
their infrastructure works with such self-signed certificates for Python and 
all other tools. 

GitHub link: 
https://github.com/apache/airflow/discussions/54290#discussioncomment-14051093

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to