[
https://issues.apache.org/jira/browse/FLINK-21840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303148#comment-17303148
]
Yang Wang commented on FLINK-21840:
-----------------------------------
See the discussion here FLINK-16601. We could introduce a config option to
control whether to use the master or slave node for generation {{NodePort URL}}.
Currently, you could use the following command to work around.
{{./bin/flink run -d --target remote -Drest.address=xxx -Drest.port=xxx
examples/streaming/StateMachineExample.jar}}
> can't submit flink k8s session job with
> kubernetes.rest-service.exposed.type=NodePort
> -------------------------------------------------------------------------------------
>
> Key: FLINK-21840
> URL: https://issues.apache.org/jira/browse/FLINK-21840
> Project: Flink
> Issue Type: Bug
> Components: Runtime / REST
> Affects Versions: 1.12.2
> Environment: flink on native kubernetes with session mode
> Reporter: hayden zhou
> Priority: Major
>
> I have created a flink session cluster by `kubernetes-session` command with
> -Dkubernetes.rest-service.exposed.type=NodePort options, because we don't
> want to expose the rest service external.
> when I submit flink job by `flink run --target kubernetes-session xxx` i
> found this command will automatically find the Kubernetes ApiServer address
> as the Node address. But my ApiService address IP is not in the node ips of
> k8s cluster. can I specific a node IP explicitly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)