0

So our current situation is that we are running a GKE cluster with a TCP Proxy loadbalancer with regional IP. Many of our domains are managed externally (by customers).

For quite some time we want to migrate towards a external HTTPS loadbalancer. There is (as far as I'm aware) no direct upgrade path, because the external HTTPS loadbalancer uses a global static IP. Because of the setup above this can't be done instantly, but needs to plan for a longer migration.

I haven't found any documentation towards resolving this situation. My first guess would be to run both loadbalancer (with same paths) in parallel for some time or point the TCP Proxy loadbalancer towards the external HTTPS one. How would that work?

WhatIsName
  • 2,294
  • 4
  • 24
  • 36
  • Can you share the reason why you need to migrate from tcp regional load balancer to external https load balancer? Is there any concern or issue using TCP load balancer with your customer? For now let me share to you this [link](https://cloud.google.com/load-balancing/docs/https/migrate-to-global) of “Plan your migration to the global external HTTP(S) load balancer” to see the differences. – Yvan G. Dec 17 '22 at 03:30

0 Answers0