/kubernetes-the-hard-way

Bootstrap Kubernetes the hard way on Vagrant on Local Machine. No scripts.

Primary LanguageShellApache License 2.0Apache-2.0

This tutorial is a modified version of the original developed by Kelsey Hightower.

Kubernetes The Hard Way On VirtualBox

This tutorial walks you through setting up Kubernetes the hard way on a local machine using VirtualBox. This guide is not for people looking for a fully automated command to bring up a Kubernetes cluster. If that's you then check out Google Kubernetes Engine, or the Getting Started Guides.

Kubernetes The Hard Way is optimized for learning, which means taking the long route to ensure you understand each task required to bootstrap a Kubernetes cluster.

This tutorial is a modified version of the original developed by Kelsey Hightower. While the original one uses GCP as the platform to deploy kubernetes, we use VirtualBox and Vagrant to deploy a cluster on a local machine. If you prefer the cloud version, refer to the original one here

The results of this tutorial should not be viewed as production ready, and may receive limited support from the community, but don't let that stop you from learning!

Please note that with this particular challenge, it is all about the minute detail. If you miss one tiny step anywhere along the way, it's going to break!

Always run the cert_verify script at the places it suggests, and always ensure you are on the correct node when you do stuff. If cert_verify shows anything in red, then you have made an error in a previous step. For the master node checks, run the check on master-1 and on master-2

Target Audience

The target audience for this tutorial is someone planning to support a production Kubernetes cluster and wants to understand how everything fits together.

Cluster Details

Kubernetes The Hard Way guides you through bootstrapping a highly available Kubernetes cluster with end-to-end encryption between components and RBAC authentication.

Node configuration

We will be building the following:

  • Two control plane nodes (master-1 and master-2) running the control plane components as operating system services.
  • Two worker nodes (worker-1 and worker-2)
  • One loadbalancer VM running HAProxy to balance requests between the two API servers.

Labs