Hi Devs, There is a proposal for implementing $subject in Kubernetes. This feature is called Kubernetes Cluster Federation [1] and it is more than cloud bursting.
[image: Inline image 2] Main focus is on following features: - *"Preferentially run my workloads in my on-premise cluster(s), but automatically overflow to my cloud-hosted cluster(s) if I run out of on-premise capacity".* - *"Most of my workloads should run in my preferred cloud-hosted cluster(s), but some are privacy-sensitive, and should be automatically diverted to run in my secure, on-premise cluster(s)".* - *"I want to avoid vendor lock-in, so I want my workloads to run across multiple cloud providers all the time. I change my set of such cloud providers, and my pricing contracts with them, periodically".* - *"I want to be immune to any single data centre or cloud availability zone outage, so I want to spread my service across multiple such zones (and ideally even across multiple cloud providers)."* [1] https://github.com/kubernetes/kubernetes/blob/master/docs/proposals/federation.md Thanks -- Imesh Gunaratne Senior Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
