How-to · Vault-compatible API

Your tooling speaks Vault.
Your secrets live in Monopam.

Clusters, pipelines, and GitOps tools grow up around the HashiCorp Vault API. Monopam exposes a Vault-compatible endpoint over its Secrets Store, so the vault CLI, External Secrets Operator, and argocd-vault-plugin read Monopam secrets without a rewrite: same paths, same login methods, PAM-grade policy and audit behind them.

  • KV v2 reads
  • Kubernetes · JWT/OIDC · AppRole login
  • Off by default
Walkthrough

From vault CLI to synced cluster secrets.

Five steps. Your manifests keep their Vault syntax.

  1. 01

    Turn on the Secrets API

    The Vault-compatible endpoint ships off by default. Enable it under System > Secrets API, and put the built-in IP allowlist and login throttling in front of it before anything else connects.

    Tip — Projects map to mounts and environments to top-level paths: a secret lives at <project>/data/<environment>/<folder>.
  2. 02

    Create machine identities and grants

    Each workload gets its own machine identity, granted per project and environment. A Kubernetes identity is bound to a specific service account; JWT/OIDC and AppRole identities fit pipelines and platforms that cannot present a cluster token.

    Tip — Grants gate everything, including names: a token without a grant on a project cannot even list its environments; it gets the same refusal as for a project that does not exist.
  3. 03

    Log in with the client you already use

    From a pod: vault write auth/kubernetes/login role=<identity> jwt=<service-account token>. From a pipeline: vault write auth/approle/login with the role and secret id. The returned token answers lookup, renew, and revoke exactly as your tooling expects.

    Tip — A token presented by the wrong service account is refused by name, and a revoked token answers permission denied from that moment on.
  4. 04

    Read secrets the Vault way

    vault kv get -mount=<project> <environment> returns the environment’s keys with version metadata; folders and single keys resolve as deeper paths, and vault kv list walks what the grant allows. References defined in Monopam, such as a DATABASE_URL built from other keys, arrive already resolved.

  5. 05

    Point your platform tooling at it

    The External Secrets Operator’s native vault provider syncs Monopam secrets into cluster Secrets, and argocd-vault-plugin renders path placeholders in your manifests. Prefer a CRD-first setup? The Monopam Kubernetes Operator ships as a Helm chart with MonoStore and MonoSecret resources.

    Tip — All three paths were verified end to end against a live GKE cluster: ESO reports SecretSynced, avp generate fills the manifest, and the operator passes its end-to-end suite.
Ready for the full picture?

The complete walkthrough — with every screenshot, every flag, and version-specific notes — lives in our help center.

Continue in the full docs

Ready to start managing
identities the right way?

Spin up a fully-loaded trial tenant in under five minutes. No credit card. No sales gate.