mirrors
/
kubernetes-the-hard-way
mirror of https://github.com/kelseyhightower/kubernetes-the-hard-way
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Bootstrap Kubernetes the hard way on Google Cloud Platform. No scripts.
197 Commits
4 Branches
7 Tags
4.5 MiB
Markdown 100%
 
Go to file
Tolleiv Nietsch d63fdd28df Adjust the ingress rule to allow all outgoing traffic 2016-10-06 17:21:42 +02:00
deployments update kubedns add-on 2016-09-11 06:20:02 -07:00
docs Adjust the ingress rule to allow all outgoing traffic 2016-10-06 17:21:42 +02:00
services update kubedns add-on 2016-09-11 06:20:02 -07:00
LICENSE add LICENSE file 2016-07-09 09:31:13 -07:00
README.md update etcd version 2016-09-27 06:23:14 -07:00
authorization-policy.jsonl add dns add-on lab 2016-07-09 08:16:09 -07:00
token.csv let the pain begin 2016-07-07 07:15:59 -07:00

README.md

Kubernetes The Hard Way

This tutorial will walk 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 Container Engine, or the Getting Started Guides.

This tutorial is optimized for learning, which means taking the long route to help people understand each task required to bootstrap a Kubernetes cluster. This tutorial can be completed on the following platforms:

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 prevent 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. After completing this tutorial I encourage you to automate away the manual steps presented in this guide.

  • This tutorial is for educational purposes only. There is much more configuration required for a production ready cluster.

Cluster Details

  • Kubernetes 1.4.0
  • Docker 1.12.1
  • etcd 3.0.10
  • CNI Based Networking
  • Secure communication between all components (etcd, control plane, workers)
  • Default Service Account and Secrets

What's Missing

The resulting cluster will be missing the following items:

Assumptions

GCP

  • The us-central1 region will be used
gcloud config set compute/region us-central1

AWS

  • The us-west-2 region will be used

Platforms

This tutorial assumes you have access to one of the following:

Labs

While GCP or AWS will be used for basic infrastructure needs, the things learned in this tutorial apply to every platform.