Skip to content

Commit bae6d7d

Browse files
Refine wording and improve clarity in Kedify HTTP autoscaling and installation documentation
1 parent 7ec2fee commit bae6d7d

3 files changed

Lines changed: 23 additions & 20 deletions

File tree

content/learning-paths/servers-and-cloud-computing/kedify-http-autoscaling/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ learning_objectives:
1212

1313
prerequisites:
1414
- A running Kubernetes cluster (local or cloud)
15-
- Kubectl and Helm installed locally
15+
- Kubectl and Helm installed
1616
- Access to the Kedify Service dashboard to obtain your Organization ID and API key (sign up at [Kedify dashboard](https://dashboard.kedify.io/))
1717

1818
author: Zbynek Roubalik

content/learning-paths/servers-and-cloud-computing/kedify-http-autoscaling/http-scaling.md

Lines changed: 20 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -5,23 +5,25 @@ layout: "learningpathall"
55
---
66
## Overview
77

8-
In this section, you’ll gain hands-on experience with Kedify HTTP autoscaling. You will deploy a small web service, expose it through a standard Kubernetes Ingress, and rely on Kedify’s autowiring to route traffic through its proxy so requests are measured and drive scaling.
8+
In this section, you’ll gain hands-on experience with Kedify HTTP autoscaling. You will deploy a small web service, expose it through a standard Kubernetes Ingress, and rely on Kedify’s autowiring to route traffic through its proxy so that requests are measured and drive scaling.
99

10-
You will scale a real HTTP app exposed through Kubernetes Ingress using Kedify’s [kedify-http](https://docs.kedify.io/scalers/http-scaler/) scaler. You will deploy a simple application, enable autoscaling with a [ScaledObject](https://keda.sh/docs/latest/concepts/scaling-deployments/), generate load, and observe the system scale out and back in (including scale-to-zero when idle).
10+
You will scale a real HTTP app exposed through Kubernetes Ingress using [Kedify’s HTTP Scaler](https://docs.kedify.io/scalers/http-scaler/), and then move on to deploy a simple application, enable autoscaling with a scaled object, generate load, and observe the system scale out and back in (including scale-to-zero when idle).
11+
12+
For more information, see [Scaling Deployments, StatefulSets & Custom Resources](https://keda.sh/docs/latest/concepts/scaling-deployments/) at the KEDA website.
1113

1214
## How it works
1315

14-
With ingress autowiring enabled, Kedify automatically routes traffic through its proxy before it reaches your Service/Deployment:
16+
With ingress autowiring enabled, Kedify automatically routes traffic through its proxy before it reaches your service and deployment:
1517

1618
```output
1719
Ingress → kedify-proxy → Service → Deployment
1820
```
1921

20-
The [Kedify Proxy](https://docs.kedify.io/scalers/http-scaler/#kedify-proxy) gathers request metrics used by the scaler to make decisions.
22+
The [Kedify proxy](https://docs.kedify.io/scalers/http-scaler/#kedify-proxy) gathers request metrics used by the scaler to make decisions.
2123

2224
## Deployment overview
2325

24-
There are three main components at play:
26+
There are three main components involved in the process:
2527
* For the application deployment and service, there is an HTTP server with a small response delay to simulate work.
2628
* For ingress, there is a public entry point that is configured using the `application.keda` host.
2729
* For the ScaledObject, there is a Kedify HTTP scaler using `trafficAutowire: ingress`.
@@ -44,7 +46,7 @@ If your ingress controller service uses a different name or namespace, update th
4446

4547
## Deploy the application and configure Ingress
4648

47-
Now you will deploy a simple HTTP server and expose it using an Ingress resource. The source code for this application is available on [GitHub](https://github.com/kedify/examples/tree/main/samples/http-server).
49+
Now you will deploy a simple HTTP server and expose it using an Ingress resource. The source code for this application is available on the [Kedify GitHub repository](https://github.com/kedify/examples/tree/main/samples/http-server).
4850

4951
### Deploy the application
5052

@@ -138,6 +140,7 @@ application 1/1 1 1 3m44s
138140
```
139141

140142
## Test the application
143+
141144
Once the application and Ingress are deployed, verify that everything is working correctly by sending a request to the exposed endpoint. Run the following command:
142145

143146
```bash
@@ -155,7 +158,7 @@ Connection: keep-alive
155158

156159
## Enable autoscaling with Kedify
157160

158-
The application is now running. Next, you will enable autoscaling so that it can scale dynamically between 0 and 10 replicas. Kedify ensures that no requests are dropped during scaling. Apply the `ScaledObject` by running the following command:
161+
The application is now running. Next, you will enable autoscaling so that it can scale dynamically between 0 and 10 replicas. Kedify ensures that no requests are dropped during scaling. Apply the `ScaledObject` by running the following command:
159162

160163
```bash
161164
cat <<'EOF' | kubectl apply -f -
@@ -195,17 +198,17 @@ spec:
195198
EOF
196199
```
197200

198-
Key Fields explained:
199-
- `type: kedify-http` — Specifies that Kedify’s HTTP scaler should be used.
200-
- `hosts`, `pathPrefixes` — Define which requests are monitored for scaling decisions.
201-
- `service`, `port` — TIdentify the Kubernetes Service and port that will receive the traffic.
202-
- `scalingMetric: requestRate` and `targetValue: 10` — Scale out when request rate exceeds the target threshold (e.g., 1000 req/s per window, depending on configuration granularity).
201+
Key fields explained:
202+
- `type: kedify-http` - specifies that Kedify’s HTTP scaler should be used
203+
- `hosts`, `pathPrefixes` - define which requests are monitored for scaling decisions
204+
- `service`, `port` - identify the Kubernetes Service and port that will receive the traffic
205+
- `scalingMetric: requestRate`, `granularity: 1s`, and `targetValue: "10"` - scale out when sustained request rate exceeds ~10 req/s per replica
203206
- `minReplicaCount: 0` — Enables scale-to-zero when there is no traffic.
204207
- `trafficAutowire: ingress` — Automatically wires your Ingress to the Kedify proxy for seamless traffic management.
205208

206209
After applying, the `ScaledObject` will appear in the Kedify dashboard (https://dashboard.kedify.io/).
207210

208-
![Kedify Dashboard With ScaledObject](images/scaledobject.png)
211+
![Kedify dashboard showing the ScaledObject alt-text#center](images/scaledobject.png "Kedify dashboard: ScaledObject")
209212

210213
## Send traffic and observe scaling
211214

@@ -219,8 +222,8 @@ To confirm that the application has scaled down, run the following command and w
219222
watch kubectl get deployment application -n default
220223
```
221224

222-
You should see similar output:
223-
```bash
225+
You should output similar to:
226+
```output
224227
Every 2,0s: kubectl get deployment application -n default
225228
226229
NAME READY UP-TO-DATE AVAILABLE AGE
@@ -267,7 +270,7 @@ Expected behavior:
267270

268271
You can also monitor traffic and scaling in the Kedify dashboard:
269272

270-
![Kedify Dashboard ScaledObject Detail](images/load.png)
273+
![Kedify dashboard showing request load and scaling over time alt-text#center](images/load.png "Kedify dashboard: request load and scaling over time")
271274

272275
## Clean up
273276

@@ -283,4 +286,4 @@ This will delete the `ScaledObject`, Ingress, Service, and Deployment associated
283286

284287
## Next steps
285288

286-
To go futher, you can explore the Kedify [How-to guides](https://docs.kedify.io/how-to/) for more configurations such as Gateway API, Istio VirtualService, or OpenShift Routes.
289+
To go further, you can explore the Kedify [How-to guides](https://docs.kedify.io/how-to/) for more configurations such as Gateway API, Istio VirtualService, or OpenShift Routes.

content/learning-paths/servers-and-cloud-computing/kedify-http-autoscaling/install-kedify-helm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,9 @@ layout: "learningpathall"
55
---
66

77
## Overview
8-
In this section, you install Kedify on your Kubernetes cluster using Helm. You will add the Kedify chart repository, install KEDA (Kedify build), the HTTP Scaler, and the Kedify Agent, then verify the installation. This enables HTTP autoscaling on Kubernetes with KEDA and Kedify, including arm64 nodes.
8+
In this section, you will install Kedify on your Kubernetes cluster using Helm. You will add the Kedify chart repository, install KEDA (Kedify build), the HTTP Scaler, and the Kedify Agent. You will then verify the installation. This enables HTTP autoscaling on Kubernetes with KEDA and Kedify, including arm64 nodes.
99

10-
For more information and other installation methods on Arm, see the [Kedify installation docs](https://docs.kedify.io/installation/helm#installation-on-arm).
10+
For more information and other installation methods on Arm, see the [Kedify installation documentation](https://docs.kedify.io/installation/helm#installation-on-arm).
1111

1212
## Before you begin
1313

0 commit comments

Comments
 (0)