[
https://issues.apache.org/jira/browse/FLINK-27483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532137#comment-17532137
]
Yang Wang commented on FLINK-27483:
-----------------------------------
Introducing a more general field configuration in the FlinkSessionJob spec
makes sense to me. But I have still a little concerns. Currently, we might have
an assumption that the kubernetes operator configurations(e.g. reconciliation
interval, timeout, etc.) for all the FlinkDeployment are same. Even though they
could be configured in the {{.spec.flinkConfiguration}}, they could not take
effect. I believe your proposal breaks(or maybe improve) the current behavior.
BTW, for the Flink supported filesystem(e.g. s3, oss, HDFS, etc.) artifact
fetcher, we also could not configure different authentication credentials for
each FlinkDeployment or FlinkSessionJob.
> Support adding custom HTTP header for HTTP based Jar fetch
> ----------------------------------------------------------
>
> Key: FLINK-27483
> URL: https://issues.apache.org/jira/browse/FLINK-27483
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Fuyao Li
> Priority: Major
>
> Hello Team,
> I noticed this https://issues.apache.org/jira/browse/FLINK-27161, which could
> enable users to specify a URL to fetch jars.
> In many cases, user might want to add some custom headers to fetch jars from
> remote private artifactory (like Oauth tokens, api-keys, etc).
> adding a field called artifactoryJarHeader will be very helpful.
> This field can be of array type.
> [key1, value1, key2, value2]
> It seems the current ArtifactManager doesn't support specify a custom header.
> Please correct me if I am wrong.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
