NOTE this document refers to Red Hat internal components
To onboard with Service Delivery AppSRE, please follow the following onboarding document which details the whole process.
All traffic goes through the Envoy container, which sends requests to the 3scale Limitador instance for global rate limiting across all API endpoints. If Limitador is unavailable, the response behaviour can be configured as desired. For this setup, the Envoy configuration when Limitador is unavailable is setup to forward all requests to the fleet-manager container. If the Envoy sidecar container itself was unavailable, the API would be unavailable.
-
The Envoy configuration for your deployment will need to be provided in AppInterface. Follow the manage a config map guideline. The file kas-fleet-manager Envoy ConfigMap can serve as a starting template for your fleet manager. This file is further referenced in kas-fleet-manager namespace so that the config map gets created.
-
Rate Limiting configuration is managed in rate-limiting saas file. Follow the
kas-fleet-manager
example to setup your configuration.
For more information on the setup, please see the Rate Limiting template and engage AppSRE for help.