Architecture

These pages explain why the provider is shaped the way it is. They are maintainer-facing and assume operator-side context from Start Here, Deployment, and Operations.

Topics

  • Overview for the component model, data flow, trust boundaries, and deployment shape.
  • Background for the Kubernetes etcd encryption and KMS v2 protocol primer, plus the OpenBao Transit primer.
  • Transit Key Model for the OpenBao Transit key, policy, and isolation design.
  • Rotation Model for the rotation invariants the provider enforces against the Transit key version.
  • Failure Modes for the catalog of failure scenarios, observability signals, and design responses.
  • Related Work for existing Vault Transit KMS plugin work and the design influences this project carries forward.

Use Another Section If

  • the question is about how to install, wire, or operate the provider: go to Start Here or Operations .
  • the question is about exact behavior or contract detail: go to Reference .
  • the question is about contributing or local development: go to Development .

In This Section