patryk126p commented on issue #23727:
URL: https://github.com/apache/airflow/issues/23727#issuecomment-1143556459
not yet, sorry
--
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
patryk126p commented on issue #23727:
URL: https://github.com/apache/airflow/issues/23727#issuecomment-1135443024
Sounds like this may be it. Once we have a window when we can attempt moving
to 2.3 again I will try this command. But in the meantime can such info be
added to some migration
patryk126p commented on issue #23727:
URL: https://github.com/apache/airflow/issues/23727#issuecomment-1134202626
@dstandish are you asking just for import statement? If yes then here it is:
```
from kubernetes.client.models import (
V1Container,
V1ObjectMeta,
patryk126p commented on issue #23727:
URL: https://github.com/apache/airflow/issues/23727#issuecomment-1132480598
It's 1.21.9 on EKS
--
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
patryk126p commented on issue #23727:
URL: https://github.com/apache/airflow/issues/23727#issuecomment-1131418985
From inside container (same docker images were used for all components in
helm chart):
```
$ pip freeze | grep -E "airflow|kubernetes"
apache-airflow==2.3.0
patryk126p commented on issue #23727:
URL: https://github.com/apache/airflow/issues/23727#issuecomment-1131233034
Here is the complete set of imports from all custom operators/sensors/hooks
(somme of the imports are for type hints only):
```
import base64
import json
import
patryk126p commented on issue #23727:
URL: https://github.com/apache/airflow/issues/23727#issuecomment-1131196192
@dstandish we are not using kubernetes pod operators nor specifying
`full_pod_spec`. When it comes to `executor_config` we use something like this:
```
{
patryk126p commented on issue #23727:
URL: https://github.com/apache/airflow/issues/23727#issuecomment-1129783435
We have no startup_probes defined and we are using the default pod template
file that comes with the Helm chart - we only overwrite some options (resources
limits and requests)
