Building the Home Lab Kubernetes Playground Blog Series
Hi Everyone, I wanted to start sharing some of the content and learning paths I have been taking to get a better grasp on Kubernetes and Cloud Native technologies.
First of all I am going to be putting my learning and findings on this page as I continue to navigate these new technologies.
And then I will keep adding if possible to this post with the latest blog posts.
I would love to get your feedback useful links to add or things we should share with the community.
Page 1 / 1
Nice one CadeZilla
This is exactly the type of thing that is needed to help the huge number of Newbies out there.
If not a secret what CNI (Container Network Interface, i.e. for the pod networking) did you end up using?
Great Job Michael!
Always wanted to learn more about Kubernetes so will start here. Nice job Michael.
This is exactly the type of thing that is needed to help the huge number of Newbies out there.
If not a secret what CNI (Container Network Interface, i.e. for the pod networking) did you end up using?
Great Job Michael!
In my walkthrough I am using “L2 networks and linux bridging” but I have also looked into “weave” and “Flannel”
Would love to read some more on this though outside of the official K8 documentation about CNI, if you have some knowledge would love to hear it.
This is exactly the type of thing that is needed to help the huge number of Newbies out there.
If not a secret what CNI (Container Network Interface, i.e. for the pod networking) did you end up using?
Great Job Michael!
In my walkthrough I am using “L2 networks and linux bridging” but I have also looked into “weave” and “Flannel”
Would love to read some more on this though outside of the official K8 documentation about CNI, if you have some knowledge would love to hear it.
I have been using Calico. They have free training and a free certification as well which is no walk in the park as I happily waffled my first attempt at their exam . It gets pretty advanced so good to have some knowledge of network policies if you really want to leverage all of its capabilities. If you are using kubeadm to build your cluster and intend to use calico then use this pod cidr in the command which is what it expects by default
kubeadm init --pod-network-cidr=192.168.0.0/16
This is exactly the type of thing that is needed to help the huge number of Newbies out there.
If not a secret what CNI (Container Network Interface, i.e. for the pod networking) did you end up using?
Great Job Michael!
In my walkthrough I am using “L2 networks and linux bridging” but I have also looked into “weave” and “Flannel”
Would love to read some more on this though outside of the official K8 documentation about CNI, if you have some knowledge would love to hear it.
I have been using Calico. They have free training and a free certification as well which is no walk in the park as I happily waffled my first attempt at their exam . It gets pretty advanced so good to have some knowledge of network policies if you really want to leverage all of its capabilities. If you are using kubeadm to build your cluster and intend to use calico then use this pod cidr in the command which is what it expects by default
kubeadm init --pod-network-cidr=192.168.0.0/16
Nice Geoff, maybe a post touching on walking through where you found the learning and a small walkthrough of what a pod network is and how they work and why you need them? I would love to understand more.
This is exactly the type of thing that is needed to help the huge number of Newbies out there.
If not a secret what CNI (Container Network Interface, i.e. for the pod networking) did you end up using?
Great Job Michael!
In my walkthrough I am using “L2 networks and linux bridging” but I have also looked into “weave” and “Flannel”
Would love to read some more on this though outside of the official K8 documentation about CNI, if you have some knowledge would love to hear it.
I have been using Calico. They have free training and a free certification as well which is no walk in the park as I happily waffled my first attempt at their exam . It gets pretty advanced so good to have some knowledge of network policies if you really want to leverage all of its capabilities. If you are using kubeadm to build your cluster and intend to use calico then use this pod cidr in the command which is what it expects by default
kubeadm init --pod-network-cidr=192.168.0.0/16
Nice Geoff, maybe a post touching on walking through where you found the learning and a small walkthrough of what a pod network is and how they work and why you need them? I would love to understand more.
Sure thing! I will write something up and post here. For the time being here is the link to Calico and the training. If you fail the exam (like I did the first time) you just need to email them to reset it for you. Again the course is free. https://academy.tigera.io/course/certified-calico-operator-level-1/
I just realized that the Calico Certificate is a cat and the Legend one is a Lion, my cat here at home is thrilled :)
This is exactly the type of thing that is needed to help the huge number of Newbies out there.
If not a secret what CNI (Container Network Interface, i.e. for the pod networking) did you end up using?
Great Job Michael!
I rechecked and I am using weave for the pod network. I might have to document how I found that as it’s not straight forward.
Great work Mike!
Great work Mike!
Thanks, I am hoping when i keep adding these new posts they are being seen or maybe the post is just bouncing back up to the top. Either way hope people are seeing them.
Not sure if people get notified when I add the new posts here but thought I would wait till the end of the series to comment which I think does get a notification. Appreciate that everyone is at different stages of their learning journey here, but hopefully, this helps give some hands-on experience and something to work along too in your own environments.
I am also going to keep maintaining the learning curve subpage on the site with resources that I find useful that maybe covers more of the theory of Kubernetes.
It did not seem to notify. I saw the notification on Linkedin and then came here. But when you made the comment then I got the email. I guess periodically we can comment on our own posts i.e. “please read” and everyone will get an email .
One part to underline is the Dashboard exposure. I know this can get very confusing. MetalLB had been setup before the K10 install in this series. If people just try to jump to the K10 install without setting up a load balancer and ingress controller, then they will either have to port forward or create a nodeport to access the dashboard and it can get tricky and not best practice for production. So it is better to go from A to Z in this series as every part is important, no shortcuts .
Also on the wish list for us service providers would be an overview of the new Multi-Tenancy and Multi-Cluster features introduced in V3 :)
One part to underline is the Dashboard exposure. I know this can get very confusing. MetalLB had been setup before the K10 install in this series. If people just try to jump to the K10 install without setting up a load balancer and ingress controller, then they will either have to port forward or create a nodeport to access the dashboard and it can get tricky and not best practice for production. So it is better to go from A to Z in this series as every part is important, no shortcuts .
Also on the wish list for us service providers would be an overview of the new Multi-Tenancy and Multi-Cluster features introduced in V3 :)
That is a good point I do call out the node port and port forwarding option in the post but yes, I might need to make that clearer. I am going to concentrate on getting some posts out about AWS EKS, Microsoft AKS and Google Kubernetes Engine and maybe others before getting into the K10 stuff.
It is all part of the learning as well.
I'm going through Nigel Poulton's Pluralsight courses at the moment. They're interesting and fun to watch; thanks for the recommendation @michaelcade .
. It gets pretty advanced so good to have some knowledge of network policies if you really want to leverage all of its capabilities. If you are using kubeadm to build your cluster and intend to use calico then use this pod cidr in the command which is what it expects by default 
