# Vault course compatibility

Verified for course authoring on 2026-09-02:

| Component | Course target or observed tool | Use in this repository |
|---|---|---|
| Vault Community Edition | 2.1.0 container image | Disposable local server and Agent image |
| Vault CLI | 1.21.1 observed locally | Offline command/help and content validation |
| PostgreSQL | 18.6-alpine3.23 container image | Disposable dynamic-database target |
| Docker / Compose | 27.4.0 / 2.31.0 observed locally | Compose rendering; runtime requires a running daemon |
| kubectl | 1.36.3 observed locally | Client-side manifest dry-run only |
| GitLab CI | Current id_tokens and secrets:vault documentation | Offline YAML contract; no runner is invoked |

Primary version and behavior references:

- https://github.com/hashicorp/vault/releases
- https://developer.hashicorp.com/vault/tutorials/get-started/available-editions
- https://developer.hashicorp.com/vault/docs/agent-and-proxy/agent
- https://docs.gitlab.com/ci/secrets/hashicorp_vault/
- https://www.postgresql.org/support/versioning/
- https://hub.docker.com/_/postgres/tags

The Docker daemon was unavailable during authoring, so Compose rendering and
all offline checks ran, but the Vault/PostgreSQL runtime smoke remains a
documented verification step rather than claimed evidence.