Scaffold the bind-tsig secrets engine #1
Reference in New Issue
Block a user
Delete Branch "benvin/plugin-scaffold"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
First cut of the Vault/OpenBao secrets engine for BIND TSIG keys, modelled on vault-plugin-secrets-litellm.
Architecture
Vault never touches Kubernetes — it calls the bind-operator companion API (deployed by the operator, boolean-gated), which creates/rotates/deletes
BindTSIGKeyCRs; the operator reconciles them into key material.Paths
config— companion API url/token/tls + defaultsstatic-roles/<role>+static-creds/<role>— stable named key, managed rotation (name never changes so zone allow-update stays valid)roles/<role>+creds/<role>— dynamic, lease-bound keys (revoke deletes the CR)Companion API contract (defined here, implemented next in bind-operator)
POST /v1/keys,GET/POST /v1/keys/{name}[/rotate],DELETE /v1/keys/{name}Build/CI/e2e
make e2e)Next
Implement the companion API + operator-manages-its-deployment (boolean) in the bind-operator repo, to the contract above.
a743a7246ftob4b8915d3e