to run sensitive workloads only in specific clusters. • Avoiding provider lock-in: By making it easier to migrate applications across clusters, federation prevents cluster provider lock-in. • High availability: Single region outage does not impact the availability of workloads. • Hybrid Cloud: Extend Deployments from on-premise clusters to the cloud. Multiple clusters
clusters. • Migration of applications and services and their storage between clusters • Disaster recovery for those applications and services. • Serving users from clusters closest to them. Benefit of applications
is a custom controller that watches Kubernetes resources, and configures corresponding DNS records using external DNS providers like AWS Route 53, AzureDNS, CloudFlare, DigitalOcean, DNSimple, Dyn, PowerDNS, CoreDNS, Exoscale, and more. ExternalDNS https://github.com/kubernetes-incubator/external-dns
new APIs. • The building blocks approach allows the extension of federation to supported and custom resources, which only enhances the flexibility Federation v2 is providing for future development. • Although Federation v2 is in the prototype stage, I believe that the community behind the Federation V2 project is strong and that the project seems to be headed in the right direction. Summary