[
https://issues.apache.org/jira/browse/FLINK-13380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann resolved FLINK-13380.
-----------------------------------
Fix Version/s: 1.9.1
Resolution: Done
Done via
1.10.0: 1bb6b053184a3551ec25223fe9e9e9120bd07bff
1.9.1: d8d609f10bb9a939b9fb6189405addea778ca16e
> Improve the usability of Flink session cluster on Kubernetes
> ------------------------------------------------------------
>
> Key: FLINK-13380
> URL: https://issues.apache.org/jira/browse/FLINK-13380
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes
> Reporter: Yun Tang
> Assignee: Yun Tang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0, 1.9.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Recently, I was launching a Flink session cluster on Kubernetes. However, I
> found current documentation of
> [flink-session-cluster-on-kubernetes|https://ci.apache.org/projects/flink/flink-docs-stable/ops/deployment/kubernetes.html#flink-session-cluster-on-kubernetes]
> and its entrypoint shell script lacks usability:
> * flink-conf.yaml is not supported to configure, user have to rebuild docker
> image.
> * No explicit documentation of how to submit jobs to session cluster. There
> existed some related question on
> [stackoverflow|https://stackoverflow.com/questions/56910990/flink-on-kubernetes-how-to-submit-jobs-to-session-clusters].
> I think we should add nodeport for 8081 port in deployment yaml.
> * Cannot view logs via Flink web UI.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
