[
https://issues.apache.org/jira/browse/FLINK-18725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199397#comment-17199397
]
Yang Wang commented on FLINK-18725:
-----------------------------------
The root cause is port {{30025}} in the azure machine may be occupied by some
other process(e.g. azure daemon, random port, etc.). So i suggest to use
{{ClusterIP}} in the internal service. Just like what we have described in the
document[1], only the rest service need to be exposed. I will create a PR for
this ticket.
[1].
[https://ci.apache.org/projects/flink/flink-docs-master/ops/deployment/kubernetes.html#deploy-job-cluster]
> "Run Kubernetes test" failed with "30025: provided port is already allocated"
> -----------------------------------------------------------------------------
>
> Key: FLINK-18725
> URL: https://issues.apache.org/jira/browse/FLINK-18725
> Project: Flink
> Issue Type: Test
> Components: Deployment / Kubernetes, Tests
> Affects Versions: 1.11.0, 1.11.1
> Reporter: Dian Fu
> Priority: Critical
> Labels: test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=4901&view=logs&j=08866332-78f7-59e4-4f7e-49a56faa3179&t=3e8647c1-5a28-5917-dd93-bf78594ea994
> {code}
> The Service "flink-job-cluster" is invalid: spec.ports[2].nodePort: Invalid
> value: 30025: provided port is already allocated
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
