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
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.
8
8
9
9
## 1. Review loadgen YAML
10
10
@@ -14,7 +14,7 @@ Inspect the YAML file `~/workshop/k3s/loadgen.yaml` and validate the contents us
14
14
cat ~/workshop/k3s/loadgen.yaml
15
15
```
16
16
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.
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.
0 commit comments