Microsoft Azure
Kubernetes Fleet Manager upstream team is making new multi-cluster features
available to any Kubernetes operator.
For core multi-cluster workload placement
there is a v1alpha1 release of staged release pipelines
(ClusterStagedUpdateRun) which represents a stage-by-stage update process that
applies ClusterResourcePlacement selected resources to specified clusters. Additionally,
work has started on adding support to the fleet upstream project for
sig-multicluster's ClusterProfile API (KEP-4322).
In the networking
space, the upstream team is also announcing the v1alpha1 release of
multi-cluster network traffic shifting for public-facing multi-cluster services
using a new TrafficManagerProfile custom
resource. This new custom resource provides a cloud native method for
interacting with Azure Traffic Manager profiles and related backends via the
TrafficManagerBackend custom resource. Azure Traffic Manager can provide
DNS-based traffic load balancing for endpoints hosted on any public IP,
regardless of where that IP is hosted.