From f10e2cd7f7ac979722e778b5ab5d3b6488da03bf Mon Sep 17 00:00:00 2001 From: Ashish Date: Fri, 30 Aug 2019 19:50:56 -0400 Subject: [PATCH] corrected spelling of 'we' --- docs/examples/kops-tests-private-net-bastion-host.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/examples/kops-tests-private-net-bastion-host.md b/docs/examples/kops-tests-private-net-bastion-host.md index b00862bbde4dc..d1bbc082b6846 100644 --- a/docs/examples/kops-tests-private-net-bastion-host.md +++ b/docs/examples/kops-tests-private-net-bastion-host.md @@ -137,7 +137,7 @@ kops create instancegroup bastions --role Bastion --subnet utility-us-east-1a -- **Explanation of this command:** - This command will add to our cluster definition a new instance group called "bastions" with the "Bastion" role on the aws subnet "utility-us-east-1a". Note that the "Bastion" role need the first letter to be a capital (Bastion=ok, bastion=not ok). -- The subnet "utility-us-east-1a" was created when we created our cluster the first time. KOPS add the "utility-" prefix to all subnets created on all specified AZ's. In other words, if we instructed kops to deploy our instances on us-east-1a, use-east-1b and use-east-1c, kops will create the subnets "utility-us-east-1a", "utility-us-east-1b" and "utility-us-east-1c". Because we need to tell kops where to deploy our bastion (or bastions), wee need to specify the subnet. +- The subnet "utility-us-east-1a" was created when we created our cluster the first time. KOPS add the "utility-" prefix to all subnets created on all specified AZ's. In other words, if we instructed kops to deploy our instances on us-east-1a, use-east-1b and use-east-1c, kops will create the subnets "utility-us-east-1a", "utility-us-east-1b" and "utility-us-east-1c". Because we need to tell kops where to deploy our bastion (or bastions), we need to specify the subnet. You'll see the following output in your editor when you can change your bastion group size and add more networks.