Skip to content

Commit 4837de6

Browse files
author
Scott Malkie
committed
Formatting and fixes from chime (9)
1 parent ea8d53c commit 4837de6

File tree

2 files changed

+8
-3
lines changed

2 files changed

+8
-3
lines changed

01-path-basics/101-start-here/readme.adoc

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,10 @@ This section walks you through the creating a Kubernetes development environment
1212

1313
We can create the Cloud9 development environment via CloudFormation.
1414
This CloudFormation template will spin up the Cloud9 IDE, as well as configure the IDE environment for the rest of the workshop.
15-
The template can create a new VPC, or be launched into an existing one.
16-
If you are unsure, We recommend the "Launch template with an existing VPC" option.
15+
16+
The CloudFormation template can create a new VPC, or be launched into an existing one.
17+
If you are unsure, we recommend the "Launch template with an existing VPC" option.
18+
1719
Click on the "Deploy to AWS" button and follow the CloudFormation prompts to begin.
1820

1921
[NOTE]

01-path-basics/102-your-first-cluster/readme.adoc

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ If you have not set up the link:../101-start-here[Cloud9 Devlopment Environment]
1414
== Create a Kubernetes Cluster with kops
1515

1616
kops can be used to create a highly available cluster, with multiple master and worker nodes spread across multiple availability zones.
17-
The master and worker nodes within the cluster can use either DNS or the https://github.com/weaveworks/mesh[Weave Mesh, window="_blank"] *gossip* protocol for name resolution. For this workshop, we will use the gossip protocol. A gossip-based cluster is easier and quicker to setup, and does not does not require a domain, subdomain, or Route53 hosted zone to be registered. Instructions for creating a DNS-based cluster are provided as an appendix at the bottom of this page.
17+
The master and worker nodes within the cluster can use either DNS or the https://github.com/weaveworks/mesh[Weave Mesh^] *gossip* protocol for name resolution. For this workshop, we will use the gossip protocol. A gossip-based cluster is easier and quicker to setup, and does not does not require a domain, subdomain, or Route53 hosted zone to be registered. Instructions for creating a DNS-based cluster are provided as an appendix at the bottom of this page.
1818

1919
To create a cluster using the gossip protocol, simply use a cluster name with a suffix of `.k8s.local`. In the following steps, we will use `example.cluster.k8s.local` as a sample gossip cluster name. You may choose a different name as long as it ends with `.k8s.local`.
2020

@@ -71,6 +71,9 @@ ip-172-20-75-78.ec2.internal node True
7171

7272
Your cluster example.cluster.k8s.local is ready
7373
```
74+
75+
anchor:multi-master[]
76+
7477
=== Multi-Master Cluster
7578

7679
The command below creates a cluster in a multi-master, multi-node, and multi-az configuration.

0 commit comments

Comments
 (0)