Feature Description
In advanced deployment scenarios, the agent might be using a tunnel to reach kcp, in which case the URLs contained in APIExportEndpointSlices are not directly usable to the syncagent. For this scenario it would be nice to have support for host/port mapping, where I can tell the agent to generally replace host:port with another host:port.
Proposed Solution
Maybe add a new CLI flag to add a host/port mapping, which is then applied in the apiexport provider (from multicluster-runtime).
Alternative Solutions
No response
Want to contribute?
Additional Context
No response
Feature Description
In advanced deployment scenarios, the agent might be using a tunnel to reach kcp, in which case the URLs contained in APIExportEndpointSlices are not directly usable to the syncagent. For this scenario it would be nice to have support for host/port mapping, where I can tell the agent to generally replace host:port with another host:port.
Proposed Solution
Maybe add a new CLI flag to add a host/port mapping, which is then applied in the apiexport provider (from multicluster-runtime).
Alternative Solutions
No response
Want to contribute?
Additional Context
No response