add_be_host_mapping_list_config

[ico01]

What type of PR is this：

• [ ] BugFix
• [x] Feature
• [ ] Enhancement
• [ ] Refactor
• [ ] UT
• [x] Doc
• [ ] Tool

Which issues of this PR fixes ：

Fixes #

Problem Summary(Required) ：

Usage Note for StarRocks BE Host Mapping Configuration on Kubernetes

Overview:

When running Starrocks on Kubernetes environments, the internal service names of StarRocks backend (BE) nodes might differ from their corresponding external IPs or domain names. To facilitate seamless connectivity, we support configuring a mapping between these internal service names and their external counterparts using the starrocks.be.host.mapping.list configuration.

Configuration:

The starrocks.be.host.mapping.list property allows users to specify a list of mappings between the external IPs or domain names and internal service names of StarRocks BE nodes.

Format:

<external_ip>:<port>,<internal_service_name>:<port>;...

Example:

For instance, suppose the following mappings are required:

• External IP 20.11.12.13:9060 maps to internal service name starrocks-cdc-cn-0.starrocks-cdc-cn-search.starrocks.svc.cluster.local:9060.
• External IP 21.11.12.13:9060 maps to internal service name starrocks-cdc-cn-1.starrocks-cdc-cn-search.starrocks.svc.cluster.local:9060.

You can specify these mappings as:

starrocks.be.host.mapping.list = "20.11.12.13:9060,starrocks-cdc-cn-0.starrocks-cdc-cn-search.starrocks.svc.cluster.local:9060;21.11.12.13:9060,starrocks-cdc-cn-1.starrocks-cdc-cn-search.starrocks.svc.cluster.local:9060"

Checklist:

• [x] I have added test cases for my bug fix or my new feature
• [x] This pr will affect users' behaviors
• [x] This pr needs user documentation (for new or modified features or behaviors)
• [x] I have added documentation for my new feature or new function

[CLAassistant]

All committers have signed the CLA.

[ico01]

@banmoy @wyb i need review

[ico01]

@starrocks-xupeng @starrocks-robot