You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 02-path-working-with-clusters/201-cluster-monitoring/readme.adoc
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,12 +109,13 @@ As this manifest is a DaemonSet, this deploys a Datadog Agent on all your nodes.
109
109
Referring to the https://kubernetes.io/blog/2017/01/running-mongodb-on-kubernetes-with-statefulsets/[Kubernetes Blog] on deploying a MongoDB StatefulSet on Kubernetes:
110
110
To set up the MongoDB replica set, you need three things: A StorageClass, a Headless Service, and a StatefulSet.
111
111
We start by creating a StorageClass to tell Kubernetes what kind of storage to use for the database nodes.
112
-
In this case, we rely on EBS GP2s to store our data.
112
+
In this case, we rely on EBS GP2s to store our data (or pd-standard if you are running this in GKE).
(use templates/mongodb/storageclass-gcp.yaml if you are on GKE).
118
119
119
120
Once the storage is ready, we can spin up our MongoDB with 3 replicas.
120
121
@@ -125,7 +126,7 @@ statefulset.apps "mongo" created
125
126
```
126
127
127
128
Note that this creates a service which operates as a headless loadbalancer in front of the DBs.
128
-
This also generates Persistent Volume Claims, these should appear as EBS volumes in your AWS account.
129
+
This also generates Persistent Volume Claims, these should appear as EBS volumes in your AWS account (or pd-standard if you are running this in GKE).
129
130
130
131
Finally, for the sake of monitoring, we are going to create a user in the Primary Database, which will be used by the Datadog Agent to collect data.
131
132
@@ -174,7 +175,7 @@ This web app is an interface to spin up scenarios, where different parts of the
174
175
Now is time to see the result of your labor.
175
176
176
177
Apply the NGINX manifest, this creates a webserver in front of the application as well as a service.
177
-
The service, as opposed to the above services is configured to be a LoadBalancer. Therefore, it spins up an AWS ELB and makes a public DNS that is exposed to the world.
178
+
The service, as opposed to the above services is configured to be a LoadBalancer. Therefore, it spins up an AWS ELB (or a Load Balancer on GCP) and makes a public DNS that is exposed to the world.
178
179
179
180
```
180
181
$ kubectl apply -f templates/nginx/nginx.yaml
@@ -388,7 +389,7 @@ If you want to remove all the installed components:
388
389
kubectl get pvc
389
390
kubectl delete pvc-*
390
391
391
-
Make sure you remove the ELBand the EBSs created.
392
+
Make sure you remove the ELB/Load Balancer and the EBSs/pd-standard created.
392
393
393
394
You are now ready to continue on with the workshop!
0 commit comments