Expand description
Kubernetes Secrets backend powered by the Kubernetes REST API.
Each Greentic secret maps to a namespaced Kubernetes Secret resource.
Every write creates a new resource whose name encodes the version number,
preserving history. Deletions append a tombstone version. All operations
execute via the standard Kubernetes HTTPS endpoints using a bearer token
provided through environment variables.
Structs§
- Backend
Components - Components returned to the broker wiring.
Functions§
- build_
backend - Construct the backend and key provider from environment configuration.