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

updated 01-infrastructure.md

pull/79/head
khenidak 2016-09-30 08:29:52 +09:00
parent c0d89731d4
commit a9b535f3a4
2 changed files with 17 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/01-infrastructure-azure.md
View File

@ -1,4 +1,16 @@
# Cloud Infrastructure Provisioning - Azure # Cloud Infrastructure Provisioning - Azure
This lab will walk you through provisioning the compute instances required for running a H/A Kubernetes cluster. A total of 10 virtual machines will be created.
The guide assumes you'll be creating resources in the `West Us` region as a single Azure Resource Manager resource group.
After completing this guide you should have the following compute instances:
##### add screen shot ####
> All machines and load balancers will be provisioned with fixed private IP addresses to simplify the bootstrap process.
The control plane machines are only accessible via a jump box (a VM with publically accessable ssh). The workers machines are exposed via external load balancer that carries both an public IP and public addressable dns FQDN.
## Variables ## Variables
@ -6,10 +18,10 @@
#change the following values as needed. #change the following values as needed.
# dns for jumpbox is <jumpboxDnsLabel>.westus.cloudapp.azure.com # dns for jumpbox is <jumpboxDnsLabel>.westus.cloudapp.azure.com
jumpboxDnsLabel="the-hardway-way-jumpbox" jumpboxDnsLabel="the-hard-way-jumpbox"
# dns for workers is <workersDnsLabel>.westus.cloudapp.azure.com # dns for workers is <workersDnsLabel>.westus.cloudapp.azure.com
workersDnsLabel="the-hardway-way" workersDnsLabel="the-hard-way"
#storage account used by jumpbox + controllers + Etcd VMs #storage account used by jumpbox + controllers + Etcd VMs
controlPlaneStorageAccount="thehardwaycsa" controlPlaneStorageAccount="thehardwaycsa"

4
docs/01-infrastructure.md
View File

@ -1,8 +1,10 @@
# Cloud Infrastructure Provisioning # Cloud Infrastructure Provisioning
Kubernetes can be installed just about anywhere physical or virtual machines can be run. In this lab we are going to focus on [Google Cloud Platform](https://cloud.google.com/) and [Amazon Web Services](https://aws.amazon.com). Kubernetes can be installed just about anywhere physical or virtual machines can be run. In this lab we are going to focus on [Google Cloud Platform](https://cloud.google.com/), [Amazon Web Services](https://aws.amazon.com) and [Microsoft Azure](https://azure.microsoft.com).
This lab will walk you through provisioning the compute instances required for running a H/A Kubernetes cluster. This lab will walk you through provisioning the compute instances required for running a H/A Kubernetes cluster.
* [Cloud Infrastructure Provisioning - Google Cloud Platform](01-infrastructure-gcp.md) * [Cloud Infrastructure Provisioning - Google Cloud Platform](01-infrastructure-gcp.md)
* [Cloud Infrastructure Provisioning - Amazon Web Services](01-infrastructure-aws.md) * [Cloud Infrastructure Provisioning - Amazon Web Services](01-infrastructure-aws.md)
* [Cloud Infrastructure Provisioning - Microsoft Azure](01-infrastructure-azure.md)