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: articles/azure-functions/functions-kubernetes-keda.md
+4-14Lines changed: 4 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,15 +22,9 @@ Kubernetes-based Functions provides the Functions runtime in a [Docker container
22
22
23
23
To run Functions on your Kubernetes cluster, you must install the KEDA component. You can install this component using [Azure Functions Core Tools](functions-run-local.md).
24
24
25
-
### Installing with the Azure Functions Core Tools
25
+
### Installing with Helm
26
26
27
-
By default, Core Tools installs both KEDA and Osiris components, which support event-driven and HTTP scaling, respectively. The installation uses `kubectl` running in the current context.
28
-
29
-
Install KEDA in your cluster by running the following install command:
30
-
31
-
```cli
32
-
func kubernetes install --namespace keda
33
-
```
27
+
There are various ways to install KEDA in any Kubernetes cluster including Helm. Deployment options are documented on the [KEDA site](https://keda.sh/deploy/).
You can run the following core tools command to remove KEDA from a Kubernetes cluster:
73
-
74
-
```cli
75
-
func kubernetes remove --namespace keda
76
-
```
66
+
Steps to uninstall KEDA are documented [on the KEDA site](https://keda.sh/deploy/).
77
67
78
68
## Supported triggers in KEDA
79
69
@@ -87,7 +77,7 @@ KEDA has support for the following Azure Function triggers:
87
77
88
78
### HTTP Trigger support
89
79
90
-
You can use Azure Functions that expose HTTP triggers, but KEDA doesn't directly manage them. The Azure Functions Core Tools will install a related project, Osiris, that enables scaling HTTP endpoints from 0 to 1. Scaling from 1 to *n*would rely on the traditional Kubernetes scaling policies.
80
+
You can use Azure Functions that expose HTTP triggers, but KEDA doesn't directly manage them. You can leverage the KEDA prometheus trigger to [scale HTTP Azure Functions from 1 to *n*instances](https://dev.to/anirudhgarg_99/scale-up-and-down-a-http-triggered-function-app-in-kubernetes-using-keda-4m42).
91
81
92
82
## Next Steps
93
83
For more information, see the following resources:
0 commit comments