This is an automated email from the ASF dual-hosted git repository.

eladkal pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new 8542cdd1c5 docs: Link to `EksPodOperator` from `KubernetesPodOperator` 
docs (#33168)
8542cdd1c5 is described below

commit 8542cdd1c550d85558ac4eeb1c83f378ad7eed8a
Author: raphaelauv <[email protected]>
AuthorDate: Mon Aug 7 15:11:07 2023 +0200

    docs: Link to `EksPodOperator` from `KubernetesPodOperator` docs (#33168)
---
 docs/apache-airflow-providers-cncf-kubernetes/operators.rst | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/docs/apache-airflow-providers-cncf-kubernetes/operators.rst 
b/docs/apache-airflow-providers-cncf-kubernetes/operators.rst
index 7b7a77b4f7..bf46c2954e 100644
--- a/docs/apache-airflow-providers-cncf-kubernetes/operators.rst
+++ b/docs/apache-airflow-providers-cncf-kubernetes/operators.rst
@@ -26,10 +26,11 @@ The 
:class:`~airflow.providers.cncf.kubernetes.operators.kubernetes_pod.Kubernet
 you to create and run Pods on a Kubernetes cluster.
 
 .. note::
-  If you use `Google Kubernetes Engine 
<https://cloud.google.com/kubernetes-engine/>`__, consider
-  using the
-  :ref:`GKEStartPodOperator <howto/operator:GKEStartPodOperator>` operator as 
it
-  simplifies the Kubernetes authorization process.
+  If you use a managed Kubernetes consider using a specialize KPO operator as 
it simplifies the Kubernetes authorization process :
+
+  - :ref:`GKEStartPodOperator <howto/operator:GKEStartPodOperator>` operator 
for `Google Kubernetes Engine <https://cloud.google.com/kubernetes-engine/>`__,
+
+  - :ref:`EksPodOperator <howto/operator:EksPodOperator>` operator for `AWS 
Elastic Kubernetes Engine <https://aws.amazon.com/eks/>`__.
 
 .. note::
   The :doc:`Kubernetes executor 
<apache-airflow:core-concepts/executor/kubernetes>` is **not** required to use 
this operator.

Reply via email to