-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Improvement]: AMS server-expose-host should be adapted to domain name scenarios. #1922
Comments
Regarding enabling AMS to correctly expose its access endpoints when deployed in a K8S environment, the following changes will be made to the config. Currently:
New plan:
Changes:
|
Hi,It seems that opening separate endpoint configurations for each service can indeed solve the problem in the K8S environment. However, in more complex network environments, different optimizers may need to connect to AMS using different URIs, so perhaps we can think about the problem from the perspective of the optimizer. For example, we can open configurations for different optimizer groups and set the address they use when connecting to AMS. I think this solution may be more flexible. |
You're right, it may be more appropriate to support setting the access address from the perspective of the Optimizer Group. |
This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible. |
This issue has been closed because it has not received any activity in the last 14 days since being marked as 'stale' |
Search before asking
What would you like to be improved?
Currently, the value of AMS
server-expose-host
is an IP address, which must be readable from the network card.This way of exposing the AMS access address only works when all components are in the same interconnected network environment. It cannot be used in other network structures, such as accessing through a domain name or with a proxy. This situation is quite common, such as in a K8S cluster. Therefore, it is necessary to redesign the way AMS exposes its access address.
The expose-host may be used in the following places:
We may need a new way to separately expose the HTTP access endpoint, Table Thrift endpoint, and Optimizer Thrift endpoint.
How should we improve?
No response
Are you willing to submit PR?
Subtasks
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: