Skip to content
This repository has been archived by the owner on Dec 1, 2021. It is now read-only.

Design and Implement Architecture of handling multiple deployment #3

Open
4 tasks
TsuyoshiUshio opened this issue Jan 24, 2020 · 0 comments
Open
4 tasks
Labels

Comments

@TsuyoshiUshio
Copy link
Collaborator

As a developer I want to have a feature to handle multiple deployment by a single gRPC server, so that customer don't need to deploy server one for a deployment.

The gRPC server will accept request from several deployments. In this case, when the New method on the ExternalScalerService is created, You need to create a DisconnectedPerformanceMonitor object for each deployment. And it should be removed when Close called.

Success Criteria

  • DisconnectedPerformanceMonitor object is created for each deployment and removed when it closed.
  • Discuss the architecture with product team
  • Write unit testing for this feature
  • Write integration testing in possible scenario.

Resource

https://github.com/microsoft/keda-durable-scaler/issues/11

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant