Introduce guardrails on the app, user, environment and resource level. Go fast without breaking things.
Ensure lean resource allocation, optimally and securely reuse running instances. Tear them down or restart them on schedule.
Create ephemeral environments with every pull request. Production-like infrastructure comes out-of-the-box.
How it works
The Orchestrator follows a “Read”-”Match”-”Create”-”Deploy” pattern.
The Orchestrator reads the description of the workload and its dependent resources (the workload specification or Score file) from the CI pipeline.
The Orchestrator identifies the context (e.g. deployment to env of type staging). It then matches the correct rules (resource and configuration definitions) provided by the platform team.
After matching the abstract request from the developer to the rules and defaults provided by the platform team, the Orchestrator creates the app- and infrastructure configs.
Finally, the Orchestrator creates/updates the resources and deploys the workload. It can do this itself or in collaboration with a dedicated CD tool.
How it integrates with your setup
The Orchestrator connects to your CI pipeline and integrates with your existing toolchain through drivers. These are extension points to Infrastructure as Code (IaC) modules and cloud-APIs, like your AWS or GCP.