seanghaeli commented on code in PR #74399: URL: https://github.com/apache/airflow/pull/74399#discussion_r4287637290
########## providers/amazon/docs/executors/eks-executor.rst: ########## @@ -0,0 +1,213 @@ + .. Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + .. http://www.apache.org/licenses/LICENSE-2.0 + + .. Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. + +.. |executorName| replace:: EKS + +.. _eks_executor: + +================ +AWS EKS Executor +================ + +The EKS executor runs each Airflow task in its own pod on an Amazon EKS cluster. + +It extends the Kubernetes executor from the ``cncf.kubernetes`` provider, so pod scheduling, +pod templates, per-task pod overrides, log handling and requirements such as a database +backend other than SQLite are all as described in +:doc:`apache-airflow-providers-cncf-kubernetes:kubernetes_executor`. What it adds is +authentication: it builds the Kubernetes client for your EKS cluster from an Airflow AWS +connection, so the scheduler needs no kubeconfig file and you do not have to refresh cluster +credentials yourself. + +For a quick start guide please see :ref:`here <eks_setup_guide>`. + +Requirements +------------ + +The executor needs ``apache-airflow-providers-cncf-kubernetes`` version 10.24.0 or Review Comment: Yes, it's checked at import time. Added a line in the doc that states this. -- 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]
