[
https://issues.apache.org/jira/browse/AIRFLOW-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161191#comment-17161191
]
ASF GitHub Bot commented on AIRFLOW-5221:
-----------------------------------------
kuromt commented on pull request #7365:
URL: https://github.com/apache/airflow/pull/7365#issuecomment-660994892
@mik-laj Thanks.
I agree that maintaing many parameters in KubernetesPodOperator is not a
good way.
Let me confirm that the command is helper tool to generate API Object from
existing dag files for `pod` or `pod_template_file` parameter, right?
I am interested in the idea.
To help developing the command, should I create new PR?
----------------------------------------------------------------
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:
[email protected]
> Add host alias support to the KubernetesPodOperator
> ---------------------------------------------------
>
> Key: AIRFLOW-5221
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5221
> Project: Apache Airflow
> Issue Type: Improvement
> Components: operators
> Affects Versions: 1.10.4
> Reporter: Derrick Mink
> Assignee: kuromt
> Priority: Minor
>
> [https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/]
> The only wait to manage DNS entries for kubernetes pods is through hosts
> aliases
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
