[
https://issues.apache.org/jira/browse/FLINK-20324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238477#comment-17238477
]
Yang Wang commented on FLINK-20324:
-----------------------------------
[~lublinsky] Thanks for creating this ticket. Even though we already have a
plan to support the advanced feature via pod template, I agree with you that we
may need to make some common feature having separate Flink config options. It
is more convenient for our users. And these features are very important when we
want to put native K8s integration in production.
Let't try to sort out these features and reach a consensus before getting back
to the PR.
* Environment for JobManager/TaskManager
** We already could support this. You could find the config options here[1].
They are same as Yarn/Mesos deployment.
* Secrets mount
** We already have this ability in 1.12[2]. Right?
* PVC, ConfigMap mount
** I like the spark style for volume mount[3]. Then we could support PVC,
ConfigMap, hostpath, etc. It is more flexible. WDYT?
[1].
[https://ci.apache.org/projects/flink/flink-docs-master/ops/config.html#forwarding-environment-variables]
[2].
[https://ci.apache.org/projects/flink/flink-docs-master/ops/deployment/native_kubernetes.html#using-secrets]
[3].
[https://spark.apache.org/docs/latest/running-on-kubernetes.html#using-kubernetes-volumes]
> Support customizing of containers for native kubernetes setup
> --------------------------------------------------------------
>
> Key: FLINK-20324
> URL: https://issues.apache.org/jira/browse/FLINK-20324
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes
> Affects Versions: 1.11.2
> Environment: Kubernetes
> Reporter: Boris Lublinsky
> Priority: Major
> Fix For: 1.12.0, 1.11.2
>
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> A common requirement for Flink applications is usage of custom resources
> (Environment variables, PVCs, Secrets, configMaps, etc). For example, usage
> of NFS-based checkpointing, require mounting NFS volumes, access to databases
> might require environment variables and secrets, the ability to safely remove
> cluster manager deployment might require owner's reference, etc.
> All of these resources can be added to created pods using Pod decorators
> already defined by Flink. So implementation of such support is as simple as
> implementing of new decorators and wiring them correctly to the appropriate
> factories.
>
> An implementation of such support is provided in this pull request
> [https://github.com/apache/flink/pull/14005]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
