Benyamin's playground

if you have ever deployed an AKS cluster, either through the Azure Portal or CLI, there is parameter that needs to be configured related to the networking part of AKS and that is to choose the networking model between  Azure CNI and  Kubenet. ( by default it's Kubenet as of writing this post) So what's this all about? in a nutshell this parameter is related to how Nodes and Pods gets their IP addresses assigned. It\s important to understand their difference before creating the cluster since you can\t change the networking model of your cluster once it\s deployed, and you defiantly don't want to re-create and re-configure your cluster again just because of this option. Overview of Kubenet and a few things to keep in mind This is the default options if you don't explicitly change it. With this option the cluster nodes gets their IP addresses from the VNET which your AKS is deployed to. This is not a big deal since the same thing happens if you go with the second option, ...

Disclaimer: This post does not intend to discuss  WHAT K8 Federation is, rather attempts to answer the question of  When Federation can be useful. So, lately I have came across an interesting topic in K8 which is called Cluster Federation A.K.A KubeFed. In it's core Cluster Federation enables Coordination and Configuration of two or more independent cluster. In another words you can combine the power of two or more clusters and let them work in Parallel for running a common task. In this model, one Cluster will act as the coordinator server also known as Host Cluster, and manages the configuration of several independent cluster under it's hook.  To understand it's concept better, I followed this awesome walkthrough I found on internet, and then I created 3 Clusters, one running on Azure (AKS), another running on AWS (EKS), and third one running on GCloud (GKE). In my setup I choose the GKE cluster as the HOST cluster, and registered the other two cluster underneath ...