Envoy Proxy control-plane written in Python
The purpose of
sovereign is to supply downstream envoy proxies with
configuration in near-realtime by responding to discovery requests.
Mechanism of Operation
* Polls HTTP/File/Other for data * (optional) Applies transforms to the data * Uses the data to generate Envoy configuration from templates
In a nutshell, Sovereign gathers contextual data ("sources" and "template context"), optionally applies transforms to that data (using "modifiers") and finally uses the data to generate envoy configuration from either python code, or jinja2 templates.
This is performed in a semi-stateless way, where the only state is data cached in memory.
Template context is intended to be statically configured, whereas Sources are meant to be dynamic - for example, fetching from an API, an S3 bucket, or a file that receives updates.
Modifiers can mutate the data retrieved from sources, just in case the data is in a less than favorable structure.
Both modifiers and sources are pluggable, i.e. it's easy to write your own and plug them into Sovereign for your use-case.
Currently, Sovereign supports only providing configuration to Envoy as JSON. That is to say, gRPC is not supported yet. Contributions in this area are highly appreciated!
The JSON configuration can be viewed in real-time with Sovereign's read-only web interface.
- Python 3.8+
pip install sovereign
:new: Read-only user interface
This interface allows you to browse the resources currently returned by Sovereign.
Installing dependencies for dev
I recommend creating a virtualenv before doing any dev work
python3 -m venv venv source venv/bin/activate pip install -r requirements-dev.txt
Running the test env
Running the test env daemonized
make run-daemon acceptance
Pull requests, issues and comments welcome. For pull requests:
- Add tests for new features and bug fixes
- Follow the existing style
- Separate unrelated changes into multiple pull requests
See the existing issues for things to start contributing.
For bigger changes, make sure you start a discussion first by creating an issue and explaining the intended change.
Atlassian requires contributors to sign a Contributor License Agreement, known as a CLA. This serves as a record stating that the contributor is entitled to contribute the code/documentation/translation to the project and is willing to have it used in distributions and derivative works (or is willing to transfer ownership).
Prior to accepting your contributions we ask that you please follow the appropriate link below to digitally sign the CLA. The Corporate CLA is for those who are contributing as a member of an organization and the individual CLA is for those contributing as an individual.
Copyright (c) 2018 Atlassian and others. Apache 2.0 licensed, see LICENSE.txt file.
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Hashes for sovereign-0.24.3-py3-none-any.whl