From 3e67675d508a3deea43c1f3e6fb28b00d01a8add Mon Sep 17 00:00:00 2001 From: khenidak Date: Tue, 4 Oct 2016 11:32:01 -0700 Subject: [PATCH] Doc updates and typo fixes --- README.md | 2 +- docs/01-infrastructure-azure.md | 7 ++++--- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 8f7ccaa..8039af0 100644 --- a/README.md +++ b/README.md @@ -48,7 +48,7 @@ AWS * The us-west-2 region will be used -AWS +Azure * The "west us" region will be used diff --git a/docs/01-infrastructure-azure.md b/docs/01-infrastructure-azure.md index 4cc7cc6..e18da9f 100644 --- a/docs/01-infrastructure-azure.md +++ b/docs/01-infrastructure-azure.md @@ -6,7 +6,7 @@ The guide assumes you'll be creating resources in the `West Us` region as a sing > All machines will be provisioned with fixed private IP addresses to simplify the bootstrap process. -The cluster VNs are only accessible via a jump box (a VM with publicly accessible ssh endpoint). The workers machines are exposed via external load balancer that carries both an public IP and public FQDN. +The cluster VMs are only accessible via a jump box (a VM with publicly accessible ssh endpoint). The workers machines are exposed via external load balancer that carries both an public IP and public FQDN. ## Variables @@ -97,8 +97,9 @@ azure network vnet create \ Create subnets ``` -# Azure UDR routes traffic subnet's eggress -# workers & pod ips have to be 2 separate subnets +# Azure UDR "user defined routes" in custom routing tables +# routes traffic leaving the subnet. +# Workers & pods (IPs) have to be in two separate subnets azure network vnet subnet create \ --resource-group the-hard-way \