6/29/2023 This proposal attempts to do two things: Describe the current and future needs of Hyperlight's public Sandbox API Describe how to meet these needs with a single, type-safe implementation in Rust This proposal is linked from issue #754 Currently, in the dev branch, we have several different types of Sandboxes, detailed in this section.

This document is a description of the design changes involved with PR #269 in the KEDA HTTP Addon project. Although the overall design herein is finalized, this is a living document. Details will be added as appropriate. Overview The three components -- scaler, interceptor and operator -- are loosely coupled and communicate in two ways: The routing table The HTTP pending queue sizes

June 22, 2021 @arschles This document is a work in progess. This document is an extension of issue #183 in the KEDA HTTP Addon repository. In this issue, @yaron2 requested that the interceptor and external scaler become multi-tenant, so that many Deployments could be controlled by a single scaler and routed by a single interceptor (or many replicas of the same interceptor Deployment). Current design Currently, when a new HTTPScaledObject is created, the HTTP Addon operator creates a new external scaler and interceptor. As implied above, there is currently a 1:1 mapping from interceptor/scaler to application, which is defined as a Deployment & Service. The interceptor watches the Deployment and routes to the Service. The scaler requests the size of the pending HTTP request queue on each interceptor by the following process:

This is a proposal to add HTTP functionality to KEDA (it is currently linked from this GitHub issue). Currently, KEDA includes functionality to scale Deployments and Jobs according to many different scalers, however, an HTTP based scaler is not currently supported. We have built a complete prototype built on top of KEDA core (kedacore/keda) that hosts and scales a user-specified Deployment according to incoming HTTP traffic. While not implemented in full, this architecture diagram overviews the overall system. Design This system, which we tentatively call kedahttp, contains the following components: An external scaler: this component measures the number of HTTP requests in the queue and reports it when KEDA makes a request to the gRPC interface