Reference configurations

    The goal of this set of example configurations is to demonstrate the full capabilities of Envoy in a complex deployment. All features will not be applicable to all use cases. For full documentation see the .

    Envoy configurations can become relatively complicated. At Lyft we use jinja templating to make the configurations easier to create and manage. The source distribution includes a version of the configuration generator that loosely approximates what we use at Lyft. We have also included three example configuration templates for each of the above three scenarios.

    To generate the example configurations run the following from the root of the repo:

    The previous command will produce three fully expanded configurations using some variables defined inside of configgen.py. See the comments inside of configgen.py for detailed information on how the different expansions work.

    • An instance of endpoint discovery service is assumed to be running at discovery.yourcompany.net.

    • Tracing is configured for . To disable this or enable Zipkin or tracing, delete or change the tracing configuration accordingly.

    • The configuration demonstrates the use of a . To disable this delete the rate limit configuration.

    • is configured for the service to service reference configuration and it is assumed to be running at rds.yourcompany.net.