Skip to content

Commit 48283cf

Browse files
committed
Fixed replicasets
1 parent 6d40267 commit 48283cf

File tree

2 files changed

+13
-12
lines changed

2 files changed

+13
-12
lines changed

content/en/other/hpa/5-deploy-loadgen.md

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ linkTitle: 5. Deploy Load Generator
44
weight: 5
55
---
66

7-
Now let's see how the autoscaler reacts to increased load. To do this, you'll start a different Pod to act as a client. The container within the client Pod runs in an infinite loop, sending queries to the `php-apache` service.
7+
Now let's apply some load against the `php-apache` pod. To do this, you will need start a different Pod to act as a client. The container within the client Pod runs in an infinite loop, sending HTTP GETs to the `php-apache` service.
88

99
## 1. Review loadgen YAML
1010

@@ -14,7 +14,7 @@ Inspect the YAML file `~/workshop/k3s/loadgen.yaml` and validate the contents us
1414
cat ~/workshop/k3s/loadgen.yaml
1515
```
1616

17-
This file contains the configuration for the load generator and will create a new StatefulSet with a single replica of the load generator image.
17+
This file contains the configuration for the load generator and will create a new ReplicaSet with a two replicas of the load generator image.
1818

1919
``` yaml
2020
apiVersion: apps/v1
@@ -55,7 +55,7 @@ kubectl create namespace loadgen
5555
kubectl apply -f ~/workshop/k3s/loadgen.yaml --namespace loadgen
5656
```
5757

58-
Once 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.
58+
Once you have deployed the load generator, you can see the Pods running in the `loadgen` namespace. Use previous similar commands to check the status of the Pods from the command line.
5959

6060
{{% notice title="Workshop Question" style="tip" icon="question" %}}
6161
Which metrics in the Apache Navigator have now significantly increased?
@@ -81,13 +81,8 @@ kubectl get replicaset loadgen -n loadgen
8181

8282
![Replicaset](../images/k8s-workload-replicaset.png)
8383

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**.
84+
{{% notice title="Workshop Question" style="tip" icon="question" %}}
85+
What impact can you see in the Apache Navigator?
9186
{{% /notice %}}
9287

9388
Let the load generator run for around 2-3 minutes and keep observing the metrics in the Kubernetes Navigator and the Apache Navigator.

content/en/other/hpa/6-setup-hpa.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -80,8 +80,14 @@ kubectl edit hpa php-apache -n apache
8080

8181
Save the changes you have made. (Hint: Use `Esc` followed by `:wq!` to save your changes).
8282

83-
{{% notice title="Workshop Question" style="tip" icon="question" %}}
84-
How many pods are now in a running state? How many are pending? Why are they pending?
83+
{{% notice title="Workshop Questions" style="tip" icon="question" %}}
84+
85+
1. How many pods are now in a running state?
86+
87+
2. How many are pending?
88+
89+
3. Why are they pending?
90+
8591
{{% /notice %}}
8692

8793
**Congratulations!** You have successfully completed the workshop.

0 commit comments

Comments
 (0)