kumahq / kuma

🐻 The multi-zone service mesh for containers, Kubernetes and VMs. Built with Envoy. CNCF Sandbox Project.
https://kuma.io/install
Apache License 2.0
3.63k stars 332 forks source link

Migrate zones between global CPs without breaking cross-zone traffic #8211

Open lobkovilya opened 11 months ago

lobkovilya commented 11 months ago

Description

  1. zone-1 and zone-2 connected to global-cp-old and there is cross-zone traffic
  2. connect zone-1 to global-cp-new, zone-ingress-2 is not synced yet, so cross-zone traffic doesn't work
  3. connect zone-2 to global-cp-new, zone-ingress-2 is synced, and cross-zone traffic works again

If we somehow allow syncing zoneIngresses up first, we can have cross-zone traffic working on step 2.

lahabana commented 11 months ago

Triage: could it be an option in the zone to pause sync of zoneIngresses?

xref: https://github.com/kumahq/kuma/issues/4360

github-actions[bot] commented 8 months ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 5 months ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 2 months ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

lobkovilya commented 2 months ago

@jakubdyszkiewicz is it somehow different with MeshMultizoneService? Or we still need a way to sync ZoneIngresses manually?

michaelbeaumont commented 2 months ago

While we don't need to sync ZoneIngress, we need to sync MeshServices, so I think the issue would still exist.