You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 1, 2021. It is now read-only.
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.
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
Resource
https://github.com/microsoft/keda-durable-scaler/issues/11
The text was updated successfully, but these errors were encountered: