Project

General

Profile

Actions
Copy link

Feature #408

open

Support #370: OAM: Vault - migrate all API keys (HIGH priority)

Deploy HashiCorp Vault infrastructure for shared secrets

Feature #408: Deploy HashiCorp Vault infrastructure for shared secrets

Added by Charles N 2 days ago. Updated 1 day ago.

Status:
New
Priority:
Normal
Assignee:
Charles N
Target version:
Cat2: PKI/CA + Vault Deployment
Start date:
08/10/2026
Due date:
% Done:

0%

Estimated time:

Description

Parent: #407

Deploy a HashiCorp Vault instance to serve as the backend for all shared/infrastructure credentials.

Scope

  • Deploy Vault (Docker, dev/staging first, then production)
  • Configure storage backend, auto-unseal, audit logging
  • Define secret engine layout (KV v2)
  • Define access policies per service/role
  • Establish auth method (token-based for initial bootstrap, then approle or similar for machines)
  • Document bootstrapping and recovery procedures in Discourse

Success criteria

  • Vault running and reachable on the internal network
  • Policies defined for all 6 shared services (redmine, discourse, uptime-kuma, technitium, phpipam, beszel)
  • Secrets can be written and read via CLI

References

Updated by Charles N 1 day ago Actions
Copy link
 #1

  • Tracker changed from Bug to Feature

Updated by Charles N 1 day ago Actions
Copy link
 #2

  • Assignee set to Charles N

Updated by Charles N 1 day ago Actions
Copy link
 #3

  • Parent task set to #370

Updated by Charles N 1 day ago Actions
Copy link
 #4

  • Target version set to Cat2: PKI/CA + Vault Deployment
Actions
Copy link

Also available in: PDF Atom