kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #5861 from karlmutch/patch-1 

doc: Trivial spelling change
This commit is contained in:
k8s-ci-robot 2018-10-03 04:58:21 -07:00 committed by GitHub
parent 646fee8a9d caca4f6b09
commit 28cb83bc57
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/examples/kops-tests-private-net-bastion-host.md
View File

@ -1,4 +1,4 @@
# USING KOPS WITH PRIVATE NETWORKING AND A BASTION HOST IN A HIGLY-AVAILABLE SETUP
# USING KOPS WITH PRIVATE NETWORKING AND A BASTION HOST IN A HIGHLY-AVAILABLE SETUP
## WHAT WE WANT TO ACCOMPLISH HERE?
@ -307,7 +307,7 @@ ip-172-20-74-55.ec2.internal master True
Your cluster privatekopscluster.k8s.local is ready
```
## MAKING THE BASTION LAYER "HIGLY AVAILABLE".
## MAKING THE BASTION LAYER "HIGHLY AVAILABLE".
If for any reason any "legendary monster from the comics" decides to destroy the amazon AZ that contains our bastion, we'll basically be unable to enter to our instances. Let's add some H.A. to our bastion layer and force amazon to deploy additional bastion instances on other availability zones.