Skip to main content
The Maverics Storage config source connects the Orchestrator to Strata-managed cloud storage for centralized configuration delivery. The Console provisions and manages this storage automatically through its deployment management system.
Evaluation only — storage is recycled every 90 days. Maverics Storage is for evaluation and testing purposes only. All published configurations are deleted when storage is recycled. For production deployments, configure a persistent config source such as Amazon S3, Azure Blob, or Google Cloud Storage. See Config Sources for all available options.
Maverics Storage is the Strata-hosted config delivery mechanism used by Console deployments. In the Maverics Console, Orchestrator instances and configuration delivery are managed through Deployments. When working directly with YAML, configuration is managed as files delivered via the -config flag or MAVERICS_CONFIG environment variable.

​
Overview

When an Orchestrator is configured through the Maverics Console, the Console provisions Maverics Storage (a temporary S3 bucket) for each deployment. The Orchestrator downloads its configuration from this storage. Configuration bundles are cryptographically signed and verified before application, ensuring that only authentic, unmodified configuration is loaded. This config source type is called Maverics Storage and is designed for managing multiple Orchestrator instances from a single control plane — the Console handles all provisioning and delivery automatically.
When using Console-managed configuration, the Orchestrator receives its configuration from the Maverics Console. You do not need to set MAVERICS_CONFIG or any remote config source environment variable.

​
Use Cases

  • Multi-Orchestrator fleet management — manage configuration for multiple Orchestrator instances from a single Console
  • Centralized config delivery — deliver configuration through the Console management plane with audit trails
  • Team collaboration — enable multiple team members to author and review configuration changes through the Console UI

​
Getting Started with Maverics Storage

When using Maverics Storage, you download an evaluation bundle from the Console that includes everything the Orchestrator needs — the binary, preconfigured environment variables, and self-signed certificates. You do not need to configure any environment variables manually. The evaluation bundle sets MAVERICS_AWS_CONFIG, MAVERICS_BUNDLE_PUBLIC_KEY_FILE, MAVERICS_RELOAD_CONFIG, and MAVERICS_POLLING_INTERVAL_SECONDS automatically.
For step-by-step setup instructions including how to select Maverics Storage, publish configuration, and download the evaluation bundle, see Maverics Storage.

​
Configuration

Console UI documentation is coming soon. This section will walk you through configuring this component using the Maverics Console’s visual interface, including step-by-step screenshots and field descriptions.

​
Configuration Reference

Console-managed deployments are configured through the Console UI. There are no CLI flags or environment variables specific to this config source — the Console handles all provisioning and delivery automatically.

​
Troubleshooting

  • Orchestrator not receiving config — check network connectivity between the Orchestrator and the Maverics Console. Ensure firewalls allow outbound HTTPS traffic to the Console and to AWS S3 (used for configuration delivery).
  • Conflict with other config sources — do not set MAVERICS_CONFIG or remote config source environment variables when using Console-managed configuration.

Config Sources

Overview of all configuration sources

File

Load config from a local YAML file

Maverics Storage

Console-side Maverics Storage setup and evaluation bundle download