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: content/learning-paths/servers-and-cloud-computing/kedify-http-autoscaling/install-ingress.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ weight: 3
4
4
layout: "learningpathall"
5
5
---
6
6
7
-
Before deploying HTTP applications with Kedify autoscaling, you need an Ingress Controller to handle incoming traffic. Most major cloud providers (AWS EKS, Google GKE, Azure AKS) do not include an Ingress Controller by default in their managed Kubernetes offerings.
7
+
Before deploying HTTP applications with Kedify autoscaling, you need an Ingress Controller to handle incoming traffic. Most managed Kubernetes services offered by major cloud providers (AWS EKS, Google GKE, Azure AKS) do not include an Ingress Controller by default.
8
8
9
9
{{% notice Note %}}
10
10
If your cluster already has an Ingress Controller installed and configured, you can skip this step and proceed directly to the [HTTP Scaling guide](../http-scaling/).
@@ -64,13 +64,13 @@ This will save the external IP or hostname in the `INGRESS_IP` environment varia
64
64
65
65
## Configure Access
66
66
67
-
For this tutorial, you have two options:
67
+
To configure access to the ingress controller, you have two options:
68
68
69
69
### Option 1: DNS Setup (Recommended for production)
70
70
Point `application.keda` to your ingress controller's external IP/hostname using your DNS provider.
71
71
72
72
### Option 2: Host Header (Quick setup)
73
-
Use the external IP/hostname directly with a `Host:` header in your requests. When testing, you'll use:
73
+
Use the external IP/hostname directly with a `Host:` header in your requests. When testing, you will use:
@@ -80,14 +80,13 @@ The `$INGRESS_IP` environment variable contains the actual external IP or hostna
80
80
81
81
## Verification
82
82
83
-
Test that the ingress controller is working by checking its readiness:
83
+
Verify that the ingress controller is working by checking its readiness:
84
84
85
85
```bash
86
86
kubectl get pods --namespace ingress-nginx
87
87
```
88
88
89
89
You should see the `ingress-nginx-controller` pod in `Running` status.
90
90
91
-
## Next Steps
92
91
93
-
Now that you have an Ingress Controller installed and configured, proceed to the [HTTP Scaling guide](../http-scaling/) to deploy an application and configure Kedify autoscaling.
92
+
Now that you have an Ingress Controller installed and configured, proceed to the next section to deploy an application and configure Kedify autoscaling.
0 commit comments