@@ -18,14 +18,13 @@ This file contains the configuration for the load generator and will create a ne
1818
1919``` yaml
2020apiVersion : apps/v1
21- kind : StatefulSet
21+ kind : ReplicaSet
2222metadata :
2323 name : loadgen
2424 labels :
2525 app : loadgen
2626spec :
27- serviceName : " loadgen"
28- replicas : 1
27+ replicas : 2
2928 selector :
3029 matchLabels :
3130 app : loadgen
@@ -59,7 +58,7 @@ kubectl apply -f ~/workshop/k3s/loadgen.yaml --namespace loadgen
5958Once you have deployed the load generator, you can see the Pod running in the ` loadgen ` namespace. Use previous similar commands to check the status of the Pod from the command line.
6059
6160{{% notice title="Workshop Question" style="tip" icon="question" %}}
62- What metrics in the Apache Dashboard have now significantly increased?
61+ Which metrics in the Apache Navigator have now significantly increased?
6362{{% /notice %}}
6463
6564## 4. Scale the load generator
@@ -71,17 +70,24 @@ ReplicaSet helps bring up a new instance of a Pod when the existing one fails, s
7170Let's scale our ReplicaSet to 4 replicas using the following command:
7271
7372``` text
74- kubectl scale statefulset /loadgen --replicas 4 -n loadgen
73+ kubectl scale replicaset /loadgen --replicas 4 -n loadgen
7574```
7675
7776Validate the replicas are running from both the command line and Splunk Observability Cloud:
7877
7978``` text
80- kubectl get statefulset loadgen -n loadgen
79+ kubectl get replicaset loadgen -n loadgen
8180```
8281
83- {{% notice title="Workshop Question" style="tip" icon="question" %}}
84- What impact did this have? Where in O11y can you see the increased replica number?
82+ ![ Replicaset] ( ../images/k8s-workload-replicaset.png )
83+
84+ {{% notice title="Workshop Questions" style="tip" icon="question" %}}
85+
86+ 1 . What impact did this have?
87+
88+ 2 . Where in Splunk Observability Cloud can you see the increased replica number?
89+
90+ ** Hint:** Use the Kubernetes Navigator and make sure ** Group by** is set to ** none** .
8591{{% /notice %}}
8692
8793Let the load generator run for around 2-3 minutes and keep observing the metrics in the Kubernetes Navigator and the Apache Navigator.
0 commit comments