potiuk commented on issue #36571:
URL: https://github.com/apache/airflow/issues/36571#issuecomment-1879761764

   Yeah. It's just strange changing provider version fixes it - but yeah it 
could be caused also by some changes to provider dependencies between those two 
versions:
   
   ```bash
   [jarek:~/code/airflow] [apache-airflow] 
change-airflow-folder-detection-in-breeze+ 1 ± git diff 
providers-cncf-kubernetes/7.4.2..providers-cncf-kubernetes/7.12.0 -- 
airflow/providers/cncf/kubernetes/provider.yaml
   ```
   
   ```diff
   diff --git a/airflow/providers/cncf/kubernetes/provider.yaml 
b/airflow/providers/cncf/kubernetes/provider.yaml
   index 11a661e63e..f0b35ca392 100644
   --- a/airflow/providers/cncf/kubernetes/provider.yaml
   +++ b/airflow/providers/cncf/kubernetes/provider.yaml
   @@ -22,7 +22,17 @@ description: |
        `Kubernetes <https://kubernetes.io/>`__
   
    suspended: false
   +source-date-epoch: 1703288121
    versions:
   +  - 7.12.0
   +  - 7.11.0
   +  - 7.10.0
   +  - 7.9.0
   +  - 7.8.0
   +  - 7.7.0
   +  - 7.6.0
   +  - 7.5.1
   +  - 7.5.0
      - 7.4.2
      - 7.4.1
      - 7.4.0
   @@ -65,7 +75,8 @@ versions:
      - 1.0.0
   
    dependencies:
   -  - apache-airflow>=2.4.0
   +  - aiofiles>=23.2.0
   +  - apache-airflow>=2.6.0
      - asgiref>=3.5.2
      - cryptography>=2.0.0
      # The Kubernetes API is known to introduce problems when upgraded to a 
MAJOR version. Airflow Core
   @@ -100,7 +111,6 @@ integrations:
    operators:
      - integration-name: Kubernetes
        python-modules:
   -      - airflow.providers.cncf.kubernetes.operators.kubernetes_pod
          - airflow.providers.cncf.kubernetes.operators.pod
          - airflow.providers.cncf.kubernetes.operators.spark_kubernetes
          - airflow.providers.cncf.kubernetes.operators.resource
   @@ -337,3 +347,6 @@ config:
            type: string
            example: ~
            default: ""
   +
   +executors:
   +  - airflow.providers.cncf.kubernetes.kubernetes_executor.KubernetesExecutor
   ```


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