Vlty (pronounced vaulty) is a tool I made for quickly reproducing issues related to Hashicorp Vault on my local machine.
It uses Hashicorp's official docker image for vault enterprise (or optionally vault open source) to spin up vault clusters of 1-3 nodes.
Vlty is designed to be ephemeral and highly configurable. Nodes and clusters can be quickly deleted and re-created.
- Docker installed
- A valid vault enterprise license
- Optionally, you can also run vault open source.
-
3 three-node vault clusters (v/, dr/, and pr/)
-
These are the main clusters I use for reproducing vault issues and especially vault issues related to replication and/or high availability.
-
More info on working with these clusters is documented in the sections below.
-
-
A Vault Agent.
- More info on working with the vault agent can be found in the agent/ readme (in progress)
-
Multiple single-node
autounseal
clusters.- More info on working with these clusters can be found in the autounseal/ readme (in progress) .
./start-cluster.sh
or ./stop-cluster.sh
to start or stop the 3 node cluster.
With no first argument provided, this will start the v
cluster only.
You can pass specify a cluster as the first argument for the shell script ./start-cluster.sh dr
or ./stop-cluster v
.
You can pass a specfic version of vault using the variable VERSION
: VERSION=1.12.1-ent ./start-cluster
- The version name uses the docker image versioning syntax
You can use the OSS version of Vault byt passing the variable OSS=vault
: OSS=vault ./start-cluster.sh
You can prevent the script from initializing Vault by passing a second argument of ni
: ./start-cluster.sh v ni