generated from kedacore/github-template
-
Notifications
You must be signed in to change notification settings - Fork 10
Open
Description
Expected behavior when implementing this solution is not fully supported when initial container was created from Azure Function using "func kubernetes deploy" or when building native container from mcr azure-function image. Change-Feed Processor does not seem to be configured correctly which prevents solution from scaling appropriately when CosmoDB trigger is executed.
Use-Case
Goal is to perform the following workflow:
- Create Azure Function which triggers on CosmosDB changes
- Leverage Azure Function Core Tools in order to run functions inside of AKS which creates Dockerfile
- Deploy container into AKS and leverage the external ScaledObject via Keda resource
Specification
- Test Azure Functions support with CosmosDB trigger to ensure solution works for this scenario.
- Test and Validate change-feed processor configuration to ensure the metadata process.Name mandatory field has valid entry
Metadata
Metadata
Assignees
Labels
No labels