Kubernetes Federation Evolution
Deploying purposes to a kubernetes cluster is nicely outlined and might in some circumstances be so simple as kubectl create -f app.yaml. The consumer’s story to deploy apps throughout a number of clusters has not been that easy. How ought to an app workload be distributed? Ought to the app assets be replicated into all clusters, or replicated into chosen clusters or partitioned into clusters? How is the entry to clusters managed? What occurs if a few of the assets, which consumer desires to distribute pre-exist in all or fewer clusters in some type.
In SIG multicluster, our journey has revealed that there are a number of doable fashions to unravel these issues and there in all probability is not any single finest match all state of affairs answer. Federation nonetheless is the only largest kubernetes open supply sub undertaking which has seen most curiosity and contribution from the neighborhood on this downside house. The undertaking initially reused the k8s API to eliminate any added utilization complexity for an current k8s consumer. This turned non-viable due to issues finest mentioned on this neighborhood replace.
What has developed additional is a federation particular API structure and a neighborhood effort which now continues as Federation V2.
As a result of federation makes an attempt to handle a fancy set of issues, it pays to interrupt the totally different elements of these issues down. Let’s check out the totally different high-level areas concerned:
Learn extra at Kubernetes
Click on Right here!