[
https://issues.apache.org/jira/browse/AIRFLOW-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205335#comment-17205335
]
ASF GitHub Bot commented on AIRFLOW-6585:
-----------------------------------------
boring-cyborg[bot] commented on pull request #11219:
URL: https://github.com/apache/airflow/pull/11219#issuecomment-701949674
Congratulations on your first Pull Request and welcome to the Apache Airflow
community! If you have any issues or are unsure about any anything please check
our Contribution Guide
(https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst)
Here are some useful points:
- Pay attention to the quality of your code (flake8, pylint and type
annotations). Our [pre-commits](
https://github.com/apache/airflow/blob/master/STATIC_CODE_CHECKS.rst#prerequisites-for-pre-commit-hooks)
will help you with that.
- In case of a new feature add useful documentation (in docstrings or in
`docs/` directory). Adding a new operator? Check this short
[guide](https://github.com/apache/airflow/blob/master/docs/howto/custom-operator.rst)
Consider adding an example DAG that shows how users should use it.
- Consider using [Breeze
environment](https://github.com/apache/airflow/blob/master/BREEZE.rst) for
testing locally, itโs a heavy docker but it ships with a working Airflow and a
lot of integrations.
- Be patient and persistent. It might take some time to get a review or get
the final approval from Committers.
- Please follow [ASF Code of
Conduct](https://www.apache.org/foundation/policies/conduct) for all
communication including (but not limited to) comments on Pull Requests, Mailing
list and Slack.
- Be sure to read the [Airflow Coding style](
https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#coding-style-and-best-practices).
Apache Airflow is a community-driven project and together we are making it
better ๐.
In case of doubts contact the developers at:
Mailing List: d...@airflow.apache.org
Slack: https://s.apache.org/airflow-slack
----------------------------------------------------------------
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:
us...@infra.apache.org
> Timestamp bug in RefreshKubeConfigLoader
> ----------------------------------------
>
> Key: AIRFLOW-6585
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6585
> Project: Apache Airflow
> Issue Type: Bug
> Components: executor-kubernetes, executors, hooks
> Affects Versions: 1.10.7
> Reporter: Jan Brusch
> Assignee: Jan Brusch
> Priority: Major
>
> When using the KubernetesPodOperator on an aws kubernetes cluster, the
> aws-iam-authenticator is used to obtain 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.
> Upon further review this is only a problem with python version <= 3.6. But
> that should not keep the issue from being fixed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
