Skip to content
This repository was archived by the owner on Apr 25, 2024. It is now read-only.

Commit b57cf16

Browse files
author
Geremy Cohen
committed
Merge remote-tracking branch 'origin/eks-5-12' into issue-512
2 parents 3dde845 + 007e8cc commit b57cf16

File tree

1 file changed

+2
-2
lines changed
  • 04-path-security-and-networking/404-network-policies/weavenet

1 file changed

+2
-2
lines changed

04-path-security-and-networking/404-network-policies/weavenet/readme.adoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ This exercise will walk you through configuring Weave Net and applying a Network
99

1010
== Prerequisites
1111

12-
This chapter uses a cluster with 3 master nodes and 5 worker nodes as described here: link:../../cluster-install#multi-master-multi-node-multi-az-gossip-based-cluster[multi-master, multi-node gossip based cluster], except we ask kops to use Weave Net as shown below:
12+
In order to perform exercises in this chapter, you’ll need to deploy configurations to a 3 master, 5 worker kops-created cluster created with the following command-line:
1313

1414
kops create cluster \
1515
--name example2.cluster.k8s.local \
@@ -19,7 +19,7 @@ This chapter uses a cluster with 3 master nodes and 5 worker nodes as described
1919
--networking weave \
2020
--yes
2121

22-
It uses `--networking weave` which tells the cluster to use Weave Net instead of the default networking provided by kubenet. Note, the name here is `example2.cluster.k8s.local` instead of the usual `example.cluster.k8s.local` name. This is just to make sure, in case, the two clusters can coexist.
22+
This command-line implements the `--networking weave` option, which tells the cluster to use Weave Net instead of the default networking provided by kubenet. Note, the name here is `example2.cluster.k8s.local` instead of the usual `example.cluster.k8s.local` name. This is just to make sure, in case, the two clusters can coexist.
2323

2424
To check the network configuration is using Weave Net, view the cluster configuration using the following command:
2525

0 commit comments

Comments
 (0)