hashicorp / hashicorp/nomad

Allow Nomad to set Vault default lease duration for non-leased credentials (KVv2)

Open
#28,200 5 comments 0 reactions 0 assignees View on GitHub
hcc/jira stage/accepted theme/vault type/enhancement
Dominant language
Go
Stars
17k
Forks
2.1k
Avg merge
1d 9h
Merged PRs (30d)
105

Description

### Proposal
Nomad should be allowed to set the Vault default lease duration for non-leased credentials. This is already exposed in consul-template as vault.default_lease_duration.

### Use-cases
In cases where allocations either have a large number of secrets this can cause load issues on Vault, or a very large number of allocations monitoring a few secrets that are rarely written a 5 minute re-check duration does not make much sense.

### Attempted Solutions
Set `ttl` keys (works with kvv1, for better or worse), explore all kinds of places where this could be set, but isn't.

Current solution is using [[[ ]]] delimiters with `template{}` and running an actual `consul-template` sidecar, which is strictly unnecessary and a lot of added complexity.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing Nomad's Vault template integration and compare it with the consul-template setting named in the issue, vault.default_lease_duration. Check how KVv2 non-leased credentials are rechecked and identify the configuration entry point; done means Nomad users can set that duration without running a consul-template sidecar.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.