# SPIRE v1.14.0

2025-12-11 · [Original release notes](https://github.com/spiffe/spire/releases/tag/v1.14.0) · [Full summary](https://ratatosk.io/en/releases/spire/v1.14.0)

Breaking changes 4 · Important fixes 2 · Enhancements 6 · Other changes 5

## Breaking changes (4)

### SPIRE agent `retry_bootstrap` setting and `retryBootstrap` flag removed

- Affects: SPIRE agents with `retry_bootstrap` set to false
- Action required: Testing without the flag before upgrading

Previously, bootstrap attestation and manager initialization did not retry when `retry_bootstrap` was false; when it was enabled, they retried with backoff.

Evidence: “- flags.BoolVar(&retryBootstrap, "retryBootstrap", true, "If true, the agent retries bootstrap with backoff")” https://github.com/spiffe/spire/pull/6431

> - Removed the deprecated 'retry_rebootstrap' agent config (#6431)

### Plugin configuration validation added to `spire-server validate`

- Affects: server configurations with plugin settings

Previously, the command did not validate plugin configuration. It now reports plugin validation errors and returns 1 when they are found; when none are found, it prints that the configuration is valid.

> - `spire-server validate` now supports validating plugin configuration (#6355)

### Disk KeyManager validates its directory at startup

- Affects: SPIRE agents configured to use the `disk` KeyManager plugin

A missing configured directory is created. Startup can fail with `FailedPrecondition` if the directory cannot be created or written to.

> - The KeyManager directory is now validated to exist and be writeable on agent startup (#6397)

### SQL datastore version and CTE queries now use the configuration context

- Affects: deployments using the SQL datastore (Inferred)

Previously, the SQL version and CTE-support queries did not use the context passed through configuration.

> - QueryContext is now used for querying the version database version and CTE support (#6461)

## Important fixes (2)

### GCP CAS adds certificate IDs for Enterprise-tier CA compatibility

- Affects: GCP CAS UpstreamAuthority with Enterprise-tier CA pools

The `certificate_id` is generated from the CSR public-key hash, giving each request a deterministic identifier for compatibility.

> - GCP CAs now specify a `certificate_id` in `CreateCertificateRequest` for Enterprise tier compatibility (#6392)

### Container location in the `k8s` and `docker` attestors fixed

- Affects: Setups using the `k8s` or `docker` workload attestor with cgroup mountinfo

When a container had multiple cgroup mounts, including entries whose root was `/`, the locator could find empty container IDs and pod UIDs and return `FailedPrecondition` errors. It now skips root-`/` entries, avoiding those errors when other entries provide the container information.

> - The `k8s` and `docker` workload attestors now ignore cgroup mountinfo with root == / (#6462)

## Enhancements (6)

- Azure IMDS attestation for Azure VMs and VM Scale Sets (To use: The `azure_imds` agent plugin used with the server-side `azure_imds` plugin)
- User-defined tags for `aws_kms`-created KMS keys (To use: Configure the `key_tags` option in the `aws_kms` plugin to use tagging.)
- Server option to disable JWT-SVID functionality (To use: Set the server configuration option `disable_jwt_svids` to `true` to disable JWT-SVID functionality.)
- SPIRE agent support for P-384 workload X.509 SVID keys
- Docker workload attestor adds image config digest selector (To use: Successful image inspection)
- PostgreSQL SQL datastore supports Cloud SQL Proxy (To use: Cloud SQL connection string)

## Other changes (5)

- Dummy WIT-SVID RPC implementations added to the server
- SPIRE server stops event fetching after cancellation
- Unused `V3AttestedNode` model removed from the SQL datastore
- `k8s_configmap` BundlePublisher documentation
- SPIRE Agent adds support for the `tpm_devid` node attestor

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
