[jira] [Commented] (AIRFLOW-5117) Airflow K8S not working with EKS when not deployed in cluster

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014350#comment-17014350 ] 

ASF GitHub Bot commented on AIRFLOW-5117:
-----------------------------------------

Bruschkov commented on pull request #7153: [AIRFLOW-5117] Fixed Bug with ISO-8601 Timestamps
URL: https://github.com/apache/airflow/pull/7153
 
 
   #JIRA
   https://issues.apache.org/jira/browse/AIRFLOW-5117
   
   # Description
   When using the KubernetesPodOperator on an aws kubernetes cluster, the aws-iam-authenticator is used to obatin kubernetes authentication tokens. The aws tokens contain ISO-8601 formatted timestamps, which couldn't be parsed in case of a "Z" (Zulu Time) timezone. This PR fixes this problem by converting the "Z" timezone into a regular +0000 format.
   
   # Test Coverage
   Not Needed, very minor fix
   
 
----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Airflow K8S not working with EKS when not deployed in cluster
> -------------------------------------------------------------
>
>                 Key: AIRFLOW-5117
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5117
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: executors, hooks
>    Affects Versions: 1.10.4
>            Reporter: QP Hou
>            Assignee: QP Hou
>            Priority: Major
>             Fix For: 1.10.7
>
>
> When Airflow scheduler or worker is not deployed in K8S cluster, all K8S API call will fail with 401 error after running for about 14min.
> This is due to EKS enforces a 15min timeout for all API tokens but the official k8S python client doesn't support token refresh.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)