Skip to content

Commit 5bae323

Browse files
authored
Remove the rest of func deploy info
1 parent 5268e37 commit 5bae323

File tree

1 file changed

+2
-18
lines changed

1 file changed

+2
-18
lines changed

articles/azure-functions/functions-run-local.md

Lines changed: 2 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -538,34 +538,18 @@ The following considerations apply to this kind of deployment:
538538

539539
### Kubernetes cluster
540540

541-
Functions also lets you define your Functions project to run in a Docker container. Use the [`--docker` option][func init] of `func init` to generate a Dockerfile for your specific language. This file is then used when creating a container to deploy.
541+
Functions also lets you define your Functions project to run in a Docker container. Use the [`--docker` option][func init] of `func init` to generate a Dockerfile for your specific language. This file is then used when creating a container to deploy. To learn how to publish a custom container to Azure without Kubernetes, see [Create a function on Linux using a custom container](functions-create-function-linux-custom-image.md).
542542

543-
Core Tools can be used to deploy your project as a custom container image to a Kubernetes cluster. The command you use depends on the type of scaler used in the cluster.
543+
Core Tools can be used to deploy your project as a custom container image to a Kubernetes cluster.
544544

545545
The following command uses the Dockerfile to generate a container and deploy it to a Kubernetes cluster.
546546

547-
# [KEDA](#tab/keda)
548-
549547
```command
550548
func kubernetes deploy --name <DEPLOYMENT_NAME> --registry <REGISTRY_USERNAME>
551549
```
552550

553551
To learn more, see [Deploying a function app to Kubernetes](functions-kubernetes-keda.md#deploying-a-function-app-to-kubernetes).
554552

555-
# [Default/KNative](#tab/default)
556-
557-
```command
558-
func deploy --name <FUNCTION_APP> --platform kubernetes --registry <REGISTRY_USERNAME>
559-
```
560-
561-
In the example above, replace `<FUNCTION_APP>` with the name of the function app in Azure and `<REGISTRY_USERNAME>` with your registry account name, such as you Docker username. The container is built locally and pushed to your Docker registry account with an image name based on `<FUNCTION_APP>`. You must have the Docker command line tools installed.
562-
563-
To learn more, see the [`func deploy` command](functions-core-tools-reference.md#func-deploy).
564-
565-
---
566-
567-
To learn how to publish a custom container to Azure without Kubernetes, see [Create a function on Linux using a custom container](functions-create-function-linux-custom-image.md).
568-
569553
## Monitoring functions
570554

571555
The recommended way to monitor the execution of your functions is by integrating with Azure Application Insights. You can also stream execution logs to your local computer. To learn more, see [Monitor Azure Functions](functions-monitoring.md).

0 commit comments

Comments
 (0)