Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Functions Support #58

Open
2 tasks
jamal-brown opened this issue Apr 20, 2023 · 0 comments
Open
2 tasks

Azure Functions Support #58

jamal-brown opened this issue Apr 20, 2023 · 0 comments

Comments

@jamal-brown
Copy link

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:

  1. Create Azure Function which triggers on CosmosDB changes
  2. Leverage Azure Function Core Tools in order to run functions inside of AKS which creates Dockerfile
  3. 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant