Skip to content

lpmi-13/kubernetes-the-hard-way-vultr

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

30 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

About

Following along after the smashing success of both k8s the hard way digitalocean and k8s the hard way linode...here's the same thing, but on Vultr!

This is a fork of the outstanding Kubernetes The Hard Way - AWS, itself a fork of the awesome Kubernetes The Hard Way by Kelsey Hightower and is geared towards using it on Vultr.

  1. Kubernetes v1.17.2
  2. cri-tools v1.17.0
  3. containerd v1.3.2
  4. CNI plugins v0.8.5
  5. etcd v3.3.18
  6. vultr-cli v2.7.0

Kubernetes The Hard Way

This tutorial walks you through setting up Kubernetes the hard way. 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, AWS Elastic Container Service for Kubernetes 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.

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!

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.

Labs

This tutorial assumes you have access to Vultr. If you are looking for the GCP version of this guide then look at : https://github.com/kelseyhightower/kubernetes-the-hard-way.

Scripts

Since I'm only able to work on this in short stretches, it's easiest to script out steps so I can pick up where I left off. If you'd like to get to a certain point automatically, for example, the end of the steps in docs/06-data-encryption-keys.md, then you can run:

for i in {3..6}; do
    ./scripts/${i}.sh
done

And to clean up at any point, just run ./scripts/14.sh. This also removes all the local resources (like yaml config files and ssh keys) that were generated along the way.

About

setting up a bootstrapped kubernetes cluster on vultr

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages