You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Airflow 2.x generic pipeline mods. See also #3166.
- Changed processor airflow and jinja2 template airflow to comply with Airflow 2.x.
- Added new location of KubernetesPodOperator library in Airflow 2.x to test Pipeline for processor airflow.
- Added cpu and memory limits fields in airflow 2.x fashion as well.
- Added documentation related to Airflow 2 support and Elyra 4 for readthedocs.
- Also mentioning what does not yet work in Elyra 4, e.g. custom components.
- tests_kubernetes.py fixed lint-server E226 missing whitespace around arithmetic operator
Signed-off-by: Sven Thoms <[email protected]>
Copy file name to clipboardExpand all lines: docs/source/getting_started/tutorials.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,10 +38,12 @@ Learn how to [run runtime-specific pipelines on Kubeflow Pipelines](https://gith
38
38
#### Run generic pipelines on Apache Airflow
39
39
40
40
Learn how to [run generic pipelines on Apache Airflow](https://github.com/elyra-ai/examples/tree/main/pipelines/run-generic-pipelines-on-apache-airflow). This tutorial requires an Apache Airflow deployment in a local environment or on the cloud.
41
+
If you want to run generic pipelines in Airflow 2.x, you have to use Elyra 4. In Elyra 4, generic pipeline support for Airflow 1 is removed.
41
42
42
43
#### Run runtime-specific pipelines on Apache Airflow
43
44
44
45
Learn how to [run runtime-specific pipelines on Apache Airflow](https://github.com/elyra-ai/examples/tree/main/pipelines/run-pipelines-on-apache-airflow). This tutorial requires an Apache Airflow deployment in a local environment or on the cloud.
46
+
If you want to run generic components (R, Python, ipynb Notebooks) in runtime-specific pipelines in Airflow 2.x, you have to use Elyra 4. In Elyra 4, generic pipeline support for Airflow 1 is removed and custom Airflow components are not yet supported.
Copy file name to clipboardExpand all lines: docs/source/recipes/configure-airflow-as-a-runtime.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,8 @@ Pipelines in Elyra can be run locally in JupyterLab, or remotely on Kubeflow Pip
24
24
**Note: Support for Apache Airflow is experimental.**
25
25
26
26
This document outlines how to set up a new Elyra-enabled Apache Airflow environment or add Elyra support to an existing deployment.
27
+
You can submit pipelines with generic components to Airflow 2.x from Elyra 4 on.
28
+
Generic components DAG code generation support for Airflow 1.x is removed in Elyra 4.
27
29
28
30
This guide assumes a general working knowledge of and administration of a Kubernetes cluster.
29
31
@@ -42,8 +44,10 @@ AND
42
44
OR
43
45
44
46
- An existing Apache Airflow cluster
45
-
- Ensure Apache Airflow is at least v1.10.8 and below v2.0.0. Other versions might work but have not been tested.
47
+
- Ensure Apache Airflow is at least v1.10.8 and below v2.0.0. This applies to Elyra < 4.
48
+
- Ensure Apache Airflow is at least v2.7.0. This applies to Elyra 4.
46
49
- Apache Airflow is configured to use the Kubernetes Executor.
50
+
- Apache Airflow must be configured to use git-sync, which is configurable both in [Airflow 1](https://airflow.apache.org/docs/apache-airflow/1.10.12/configurations-ref.html?highlight=git%20sync#git-repo) as well as in [Airflow 2](https://airflow.apache.org/docs/helm-chart/stable/parameters-ref.html#airflow)
47
51
- Ensure the KubernetesPodOperator is installed and available in the Apache Airflow deployment
Copy file name to clipboardExpand all lines: docs/source/user_guide/best-practices-custom-pipeline-components.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,8 @@ See the [Kubeflow Pipelines documentation](https://www.kubeflow.org/docs/compone
40
40
### Apache Airflow components
41
41
42
42
#### Requirements
43
+
Apache Airflow components are currently only supported for Airflow < 2 and in Elyra < 4.
44
+
Elyra 4 starts with generic components support (R, Python, ipync Notebooks), not (yet) custom components, for Airflow 2.x.
43
45
44
46
##### Configure fully qualified package names for custom operator classes
45
47
@@ -161,4 +163,4 @@ The missing component definition is stored in a [Machine Learning Exchange](http
161
163
162
164
#### Component catalogs not listed here
163
165
164
-
Check the [component catalog connector directory](https://github.com/elyra-ai/examples/blob/main/component-catalog-connectors/connector-directory.md) if the referenced catalog type is not listed here.
166
+
Check the [component catalog connector directory](https://github.com/elyra-ai/examples/blob/main/component-catalog-connectors/connector-directory.md) if the referenced catalog type is not listed here.
Copy file name to clipboardExpand all lines: docs/source/user_guide/pipeline-components.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,15 +28,15 @@ The same pipeline could be implemented using a single component that performs al
28
28
29
29
#### Generic components
30
30
31
-
Elyra includes three _generic components_ that allow for the processing of Jupyter notebooks, Python scripts, and R scripts. These components are called generic because they can be included in pipelines for any supported runtime type: local/JupyterLab, Kubeflow Pipelines, and Apache Airflow. Components are exposed in the pipeline editor via the palette.
31
+
Elyra includes three _generic components_ that allow for the processing of Jupyter notebooks, Python scripts, and R scripts. These components are called generic because they can be included in pipelines for any supported runtime type: local/JupyterLab, Kubeflow Pipelines, and Apache Airflow 2.x. Components are exposed in the pipeline editor via the palette.
32
32
33
33

34
34
35
35
Note: Refer to the [_Best practices_ topic in the _User Guide_](best-practices-file-based-nodes.md) to learn more about special considerations for generic components.
36
36
37
37
#### Custom components
38
38
39
-
_Custom components_ are commonly only implemented for one runtime type, such as Kubeflow Pipelines or Apache Airflow. (The local runtime type does not support custom components.)
39
+
_Custom components_ are commonly only implemented for one runtime type, such as Kubeflow Pipelines or Apache Airflow < 2. (The local runtime type does not support custom components). Custom components, due to their being supported only for Airflow 1.x, are only supported on Elyra < 4.
40
40
41
41

42
42
@@ -63,9 +63,9 @@ Elyra includes connectors for the following component catalog types:
63
63
64
64
Example: A URL component catalog that is configured using the `http://myserver:myport/mypath/my_component.yaml` URL makes the `my_component.yaml` component file available to Elyra.
65
65
66
-
-[_Apache Airflow package catalogs_](#apache-airflow-package-catalog) provide access to Apache Airflow operators that are stored in Apache Airflow built distributions.
66
+
-[_Apache Airflow package catalogs_](#apache-airflow-package-catalog) provide access to Apache Airflow operators that are stored in Apache Airflow built distributions. This is currently only supported for Airflow < 2.
67
67
68
-
-[_Apache Airflow provider package catalogs_](#apache-airflow-provider-package-catalog) provide access to Apache Airflow operators that are stored in Apache Airflow provider packages.
68
+
-[_Apache Airflow provider package catalogs_](#apache-airflow-provider-package-catalog) provide access to Apache Airflow operators that are stored in Apache Airflow provider packages. This is currently only supported for Airflow < 2.
69
69
70
70
Refer to section [Built-in catalog connector reference](#built-in-catalog-connector-reference) for details about these connectors.
71
71
@@ -438,6 +438,7 @@ Examples (CLI):
438
438
439
439
The [Apache Airflow package catalog connector](https://github.com/elyra-ai/elyra/tree/main/elyra/pipeline/airflow/package_catalog_connector) provides access to operators that are stored in Apache Airflow [built distributions](https://packaging.python.org/en/latest/glossary/#term-built-distribution):
440
440
- Only the [wheel distribution format](https://packaging.python.org/en/latest/glossary/#term-Wheel) is supported.
441
+
- Only Airflow < 2 is supported. Use of that functionality is not working in Elyra >=4, which is no longer supporting Airflow 1.x.
441
442
- The specified URL must be retrievable using an HTTP `GET` request. `http`, `https`, and `file`[URI schemes](https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml) are supported.
442
443
- In secured environments where SSL server authenticity can only be validated using certificates based on private public key infrastructure (PKI) with root and optionally intermediate certificate authorities (CAs) that are not publicly trusted, you must define environment variable `TRUSTED_CA_BUNDLE_PATH` in the environment where JupyterLab/Elyra is running. The variable value must identify an existing [Privacy-Enhanced Mail (PEM) file](https://en.wikipedia.org/wiki/Privacy-Enhanced_Mail).
443
444
@@ -454,6 +455,7 @@ Examples:
454
455
#### Apache Airflow provider package catalog
455
456
The [Apache Airflow provider package catalog connector](https://github.com/elyra-ai/elyra/tree/main/elyra/pipeline/airflow/provider_package_catalog_connector) provides access to operators that are stored in [Apache Airflow provider packages](https://airflow.apache.org/docs/apache-airflow-providers/):
456
457
- Only the [wheel distribution format](https://packaging.python.org/en/latest/glossary/#term-Wheel) is supported.
458
+
- Only Airflow < 2 and operators for Airflow < 2 are supported. Use of that functionality is not working in Elyra >=4, which is no longer supporting Airflow 1.x.
457
459
- The specified URL must be retrievable using an HTTP `GET` request. `http`, `https`, and `file`[URI schemes](https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml) are supported.
458
460
- In secured environments where SSL server authenticity can only be validated using certificates based on private public key infrastructure (PKI) with root and optionally intermediate certificate authorities (CAs) that are not publicly trusted, you must define environment variable `TRUSTED_CA_BUNDLE_PATH` in the environment where JupyterLab/Elyra is running. The variable value must identify an existing [Privacy-Enhanced Mail (PEM) file](https://en.wikipedia.org/wiki/Privacy-Enhanced_Mail).
0 commit comments