Skip to main content
Centralize credential authority by linking external secret management tools (such as HashiCorp Vault). The external secrets integration dynamically imports existing keys and passwords, allowing teams to safely reference them across all active services.

Integration Workflow

Connect your Vault provider in four steps:
1

Select Extensions

Click on Extensions in the left sidebar of the Revolte console.
2

Select Vault

Locate Vault under the recommended integrations and select it.
3

Choose provider

Open the Select the provider dropdown and choose your provider (e.g., hashicorp vault).
4

Fill integration details

Fill in the required authentication and access fields to establish a secure link. Revolte will pull your existing secrets automatically.
Environment variables must be configured in your revolte.yaml configuration file to properly reference and inject the synchronized Vault secrets into your application services.

Reference

FAQ

Yes. Connection metadata and secret values are stored under industry-standard AES-256 encryption using customer-isolated KMS keys.
Revolte pulls credentials dynamically from the linked Vault during container build and deploy phases, ensuring running workloads use the latest active secrets.

Support Policy

For advanced assistance with private VPC configurations, enterprise cluster peerings, or custom vault providers, connect with our support engineers on our Contact Page.