Standalone deployment is not using the proxy in the correct region

[numerology]

If a standalone deployment is deployed to a us-central1 GKE cluster, it is supposed to talk to inverse proxy us-central1. However currently it seems like it's talking to us-central2, which is inconsistent with our proxy config.

[numerology]

/assign @rmgogogo
/assign @numerology

/cc @abdallag

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Bobgy]

@numerology can you provide more details?

Choosing which proxy is code we maintain in KFP, so one of us need to investigate this.

[Bobgy]

https://github.com/kubeflow/pipelines/blob/0ff6d9cfa438119785b94b8802f4bf7d36f95bda/proxy/attempt-register-vm-on-proxy.sh

[numerology]

/lifecycle frozen

[numerology]

@Bobgy Sorry I dropped the ball on this one...

For example, if a user deploys KFP onto a GKE cluster in us-central1 region, then according to this config inverse proxy should return a host name suffixed by us-central1, but it's currently xxx-us-central2. It's not blocking usage but suboptimal.

[Bobgy]

Understood, FYI code for deciding which proxy url to choose is in https://github.com/kubeflow/pipelines/blob/0ff6d9cfa438119785b94b8802f4bf7d36f95bda/proxy/get_proxy_url.py, so anyone who'll try to fix this problem should troubleshoot there.

[suryaavala]

@Bobgy I submitted a fix in #4702, would you be able to review it?