[
https://issues.apache.org/jira/browse/FLINK-15662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17316045#comment-17316045
]
Yang Wang commented on FLINK-15662:
-----------------------------------
The read and connect timeout could be configured via environment variables and
java system properties. This PR[1] will add documentation about how to
configure Fabric8 Kubernetes client expert options[2].
For example, read and connect timeout could be set by using the following Flink
config options.
{code:java}
containerized.master.env.KUBERNETES_REQUEST_TIMEOUT: 60000
containerized.master.env.KUBERNETES_CONNECTION_TIMEOUT: 60000
{code}
Feel free to reopen this ticket if anyone still believes that we need to
introduce the Flink config options.
[1]. [https://github.com/apache/flink/pull/15480]
[2]. https://github.com/fabric8io/kubernetes-client#configuring-the-client
> Make K8s client timeouts configurable
> -------------------------------------
>
> Key: FLINK-15662
> URL: https://issues.apache.org/jira/browse/FLINK-15662
> Project: Flink
> Issue Type: Sub-task
> Components: Deployment / Kubernetes
> Reporter: Canbin Zheng
> Priority: Major
> Labels: starter
>
> Kubernetes clients used in the client-side submission and requesting worker
> pods should have configurable read and connect timeouts.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
