seanghaeli commented on code in PR #72542:
URL: https://github.com/apache/airflow/pull/72542#discussion_r4275816729
##########
providers/amazon/docs/operators/eks.rst:
##########
@@ -205,6 +205,36 @@ Note: An Amazon EKS Cluster with underlying compute
infrastructure is required.
:start-after: [START howto_operator_eks_pod_operator]
:end-before: [END howto_operator_eks_pod_operator]
+.. _howto/operator:EksPodExecOperator:
+
+Execute a command in an existing Pod on Amazon EKS
+==================================================
+
+To execute a command in a running container without managing the Pod
lifecycle, use
+:class:`~airflow.providers.amazon.aws.operators.eks.EksPodExecOperator`.
+
+This operator requires ``apache-airflow-providers-cncf-kubernetes>=10.22.0``.
+Existing EKS operators remain available with older supported versions of the
Kubernetes provider.
+
+As with ``EksPodOperator``, ``kubernetes_conn_id`` defaults to
``kubernetes_default`` and can be
+set to another Kubernetes connection. If the default connection contains
``kube_config`` or
+``cluster_context``, use a separate connection without those settings, since
EKS generates its own kubeconfig.
+
+The Pod must already exist and be running. The operator streams command
output, waits for the exit code,
+and does not create, restart, or delete the Pod.
+
+The AWS identity must have permission to call ``eks:DescribeCluster`` and be
authorized to access the
+EKS cluster. Kubernetes RBAC must allow ``get`` on ``pods`` and ``pods/exec``.
Review Comment:
Should say `get` and `create` on `pods/exec`. `create` is needed too or else
the task fails with `AttributeError`
--
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]
