Skip to content

Commit e554e8c

Browse files
authored
Merge pull request #101992 from jeffhollan/kubernetes-fix
removing ref to func tools on KEDA
2 parents 8f0e34c + 185a0f4 commit e554e8c

File tree

1 file changed

+4
-14
lines changed

1 file changed

+4
-14
lines changed

articles/azure-functions/functions-kubernetes-keda.md

Lines changed: 4 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -22,15 +22,9 @@ Kubernetes-based Functions provides the Functions runtime in a [Docker container
2222

2323
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).
2424

25-
### Installing with the Azure Functions Core Tools
25+
### Installing with Helm
2626

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/).
3428

3529
## Deploying a function app to Kubernetes
3630

@@ -69,11 +63,7 @@ kubectl delete secret <name-of-function-deployment>
6963

7064
## Uninstalling KEDA from Kubernetes
7165

72-
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/).
7767

7868
## Supported triggers in KEDA
7969

@@ -87,7 +77,7 @@ KEDA has support for the following Azure Function triggers:
8777

8878
### HTTP Trigger support
8979

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).
9181

9282
## Next Steps
9383
For more information, see the following resources:

0 commit comments

Comments
 (0)