You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Aitozi (Jira)" <ji...@apache.org> on 2022/02/24 14:38:00 UTC
[jira] [Created] (FLINK-26356) Revisit the create of RestClusterClient
Aitozi created FLINK-26356:
------------------------------
Summary: Revisit the create of RestClusterClient
Key: FLINK-26356
URL: https://issues.apache.org/jira/browse/FLINK-26356
Project: Flink
Issue Type: Sub-task
Components: Kubernetes Operator
Reporter: Aitozi
The clusterClient is built as below. The config is mixed up with the FlinkDeploymentSpec and local default config.
{code:java}
final int port = config.getInteger(RestOptions.PORT);
final String host =
config.getString(
RestOptions.ADDRESS, String.format("%s-rest.%s", clusterId, namespace));
final String restServerAddress = String.format("http://%s:%s", host, port); {code}
But the {{RestOptions.ADDRESS}} is generated at the entrypoint when the HA is enabled, so the option can not obtain from the FlinkDeploymentSpec.
Furthermore, the default rest url is not suitable for all the service type. I think we should extract the rest endpoint from the Flink external service.
One more concern is that, if the operator manage the multiple namespace, the rest url of \{{serviceName.namespace}} may not enough, it can not access across the namespace.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)