[ 
https://issues.apache.org/jira/browse/FLINK-37893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18076524#comment-18076524
 ] 

Stefan Wang commented on FLINK-37893:
-------------------------------------

  Could a committer assign FLINK-37893 to me? Have a PR ready —
  https://github.com/apache/flink/pull/28047 — adds
  kubernetes.rest-service.port-name (default "rest") so service-mesh
  port-name policies can be honored without breaking existing deployments.

  JobManager's REST service hardcodes the port name to "rest"
  (Constants.REST_PORT_NAME). Service meshes that route by port name and
  organizations with port-name conventions can't align Flink's rest
  service with those policies. Adds kubernetes.rest-service.port-name
  (default "rest") plumbed through KubernetesJobManagerParameters and
  ServiceType#buildUpExternalRestService. 
ServiceType#getRestPortFromExternalService
  drops its name-filter — the rest Service always has exactly one port
  so the lookup can return that port directly; works for any configured
  name without plumbing it through the abstract getRestEndpoint.
  Default preserves existing behavior; purely additive.

> Kuberenetes Rest service's Port Name should be made configurable
> ----------------------------------------------------------------
>
>                 Key: FLINK-37893
>                 URL: https://issues.apache.org/jira/browse/FLINK-37893
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / Kubernetes
>    Affects Versions: 1.16.1, 1.17.1, 1.18.1, 1.20.0, 1.19.1
>            Reporter: Mayur Dhingra
>            Priority: Major
>              Labels: Kubernetes, pull-request-available, rest
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> While running Flink in Kubernetes mode, the Rest Service created by Flink 
> framework has the REST_PORT_NAME is a fixed constant value called "rest". 
> This should be made configurable by users via a configurable flink config. 
> Many organization like ours have a strict policy of defining port names and 
> current flink framework does not support it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to