You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Aitozi (Jira)" <ji...@apache.org> on 2022/04/30 13:31:00 UTC

[jira] [Commented] (FLINK-27461) Add a convenient way to set userAgent for the kubeclient

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

Aitozi commented on FLINK-27461:
--------------------------------

cc [~wangyang0918] WDYT ? 

> Add a convenient way to set userAgent for the kubeclient
> --------------------------------------------------------
>
>                 Key: FLINK-27461
>                 URL: https://issues.apache.org/jira/browse/FLINK-27461
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / Kubernetes
>            Reporter: Aitozi
>            Priority: Major
>
> Currently, we construct the kubeclient from the kubeconfig file or from the context. However, If we have to set the user agent for the okttp client it will be a little hard. 
> We use the kubernetes cluster with different team, we need to distinguish the request for k8s guys to monitor the apiserver requests. We usually set the user agent for different groups. The fabric client expose a way to extract config from the property or enviroments. But the key for the user agent is bundled with the client version, it's not so convenient. Can we support to set the user agent by a dedicated flink option.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)