Assigned
Status Update
No update yet.
Comments
cb...@google.com
I have forwarded your request to our engineering team. I cannot provide an E.T.A. or guarantee that this feature will be deployed. Nevertheless rest assured that your feedback is always seriously taken.
Any future updates will be posted on this thread. Once again let me thank you for helping us to improve the functionality of our products.
Any future updates will be posted on this thread. Once again let me thank you for helping us to improve the functionality of our products.
hi...@google.com
Hi team!
I have a customer requesting this functionality as well (Bison Trails Co.)
Description
we want to take advantage of the recently introduced regional GKE clusters with HA hosted masters in three zones of a region.
This will allow us to avoid issues during master upgrades, in particular with horizontal pod autoscaling (this bit us in the past).
The current migration path is explicitly to create a new regional GKE cluster then migrate workloads from the zonal cluster:
> You can choose to create zonal or regional clusters at the time of cluster creation. However, you cannot migrate or downgrade a zonal cluster to a regional cluster, and vice versa.
cf.
This adds a lot of planning work to limit downtime during the migration from zonal to regional clusters.
The most obvious sensitive points in our use case being:
* How to migrate a GLB ingress with a static IP address from one cluster to another without disruption?
* How to make two clusters cohabit in the same subnet with a limited IP range (e.g. a /28 CIDR prefix, required for incoming traffic routed through a VPN with a partner)?
Can we expect a more straightforward path in the future where an existing zonal cluster can be converted to regional cluster without recreation and downtime?
Best regards,
Patrick.