You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/08/17 18:21:00 UTC
[jira] [Updated] (FLINK-13380) Improve the usability of Flink
session cluster on Kubernetes
[ https://issues.apache.org/jira/browse/FLINK-13380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-13380:
-----------------------------------
Labels: pull-request-available (was: )
> 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
>
>
> 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
(v7.6.14#76016)