This repository has been archived by the owner on Jan 25, 2023. It is now read-only.
v0.14.2
Modules affected
run-vault
Description
- When using a backend other than Consul,
run-vault
will now explicitly configure Vault to register itself as a service in Consul. Otherwise, if you're using some other backend, such as S3, service discovery won't work correctly. You can configure the Consul agent address to use for registration via the new--consul-agent-service-registration-address
argument (the default islocalhost:8500
). - Updated the
systemd
config thatrun-vault
sets up for Vault:- Configure reasonable defaults for
StartLimitIntervalSec
andStartLimitBurst
so Vault doesn't infinitely try to restart in case of a permanent error. - Set
LimitMEMLOCK
toinfinity
to prevent memory from being swapped to disk.
- Configure reasonable defaults for
- We've updated the examples to use more modern versions:
- Bump Vault to 1.6.1
- Bump Consul to 1.9.2