[
https://issues.apache.org/jira/browse/FLINK-14812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033444#comment-17033444
]
Eui Heo commented on FLINK-14812:
---------------------------------
This is resolved via
https://github.com/apache/flink-docker/commit/2454f908361e712ead26bced799db80d8cf02c69
> Add custom libs to Flink classpath with an environment variable.
> ----------------------------------------------------------------
>
> Key: FLINK-14812
> URL: https://issues.apache.org/jira/browse/FLINK-14812
> Project: Flink
> Issue Type: New Feature
> Components: Deployment / Kubernetes, Deployment / Scripts
> Reporter: Eui Heo
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> To use plugin library you need to add it to the flink classpath. The
> documentation explains to put the jar file in the lib path.
> https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/metrics.html#prometheus-orgapacheflinkmetricsprometheusprometheusreporter
> However, to deploy metric-enabled Flinks on a kubernetes cluster, we have the
> burden of creating and managing another container image. It would be more
> efficient to add the classpath using environment variables inside the
> constructFlinkClassPath function in the config.sh file.
> In particular, it seems inconvenient for me to create separate images to use
> the jars, even though the /opt/ flink/opt of the stock image already contains
> them.
> For example, there are metrics libs and file system libs:
> flink-azure-fs-hadoop-1.9.1.jar
> flink-s3-fs-hadoop-1.9.1.jar
> flink-metrics-prometheus-1.9.1.jar
> flink-metrics-influxdb-1.9.1.jar
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
