Skip to content

Commit e0a6ed1

Browse files
author
Scott Malkie
committed
Asciidoc link to new tab attempt (1)
1 parent 4837de6 commit e0a6ed1

File tree

2 files changed

+3
-5
lines changed

2 files changed

+3
-5
lines changed

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

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
= Kubernetes - Setup Cloud9 Development Environment
22
:icons:
3-
:linkcss:
43
:linkattrs:
54
:imagesdir: ../../resources/images
65
:toc:

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

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,19 @@
11
= Create A Kubernetes Cluster Using kops
22
:toc:
33
:icons:
4-
:linkcss:
54
:linkattrs:
65
:imagesdir: ../../resources/images
76

87
This section will walk you through how to install a Kubernetes cluster on AWS using kops.
98

10-
https://github.com/kubernetes/kops[kops], short for Kubernetes Operations, is a set of tools for installing, operating, and deleting Kubernetes clusters. kops can also perform rolling upgrades from older versions of Kubernetes to newer ones, and manage the cluster add-ons.
9+
https://github.com/kubernetes/kops[kops, window="_blank"], short for Kubernetes Operations, is a set of tools for installing, operating, and deleting Kubernetes clusters. kops can also perform rolling upgrades from older versions of Kubernetes to newer ones, and manage the cluster add-ons.
1110
12-
If you have not set up the link:../101-start-here[Cloud9 Devlopment Environment] yet, please do so before continuing.
11+
If you have not set up the link:../101-start-here[Cloud9 Devlopment Environment, window="_blank"] yet, please do so before continuing.
1312
1413
== Create a Kubernetes Cluster with kops
1514
1615
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^] *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.
16+
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.
1817
1918
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`.
2019

0 commit comments

Comments
 (0)