Skip to content

2.9.1: Confidential computing and security enhancements

Latest

Choose a tag to compare

@IsaacYangSLA IsaacYangSLA released this 12 Nov 20:54
· 211 commits to main since this release
5f2250f

2.9.1 Release Contributors (PR Count Order)

Total PRs counted in this release: 73


🎉 Welcome First-Time Contributors!


Feature Highlights

NVIDIA FLARE 2.9.1 updates the confidential computing deployment stack to follow the NVIDIA confidential computing reference architecture. Confidential computing remains a technical preview and entirely optional. Changes that affect all deployments include stricter control-request authorization, checkpoint path and Dashboard restrictions, removal of the legacy push-based tensor-streaming API, updated security dependencies, configuration-format deprecations, and reliability fixes.

  • Confidential computing (Technical Preview): one provisioning interface for bare-metal confidential VMs (CVMs), Confidential Containers (CoCo) and Azure; modes can be mixed in one federation.
    • CVM Builder builds and approves a generic confidential VM once per CPU/GPU profile, then seals each application's image, code, configuration and secrets into a separate encrypted vault, so application updates reuse the approved VM. It supports Intel TDX and AMD SEV-SNP, CPU-only or with NVIDIA confidential GPUs. Vault keys are released only after attestation passes, and workloads are re-checked periodically and quarantined on failure.
    • Confidential Containers (CoCo) run FLARE participants as Kubernetes workloads inside confidential VMs, including mixed TDX and SEV-SNP participants. Peers verify each other against the Trustee attestation service.
    • Azure: refreshed confidential VM and container guides; the single Azure Container Instances (ACI) server deployment now enforces the administrator-approved confidential computing policy and verifies a signed external startup kit.
  • Security hardening: client administration and job-control requests are checked against the authenticated caller, route and job; multiprocess sub-workers enforce the site's component authorization; PTFileModelPersistor checkpoint paths must stay within the application directory; the Dashboard rejects client props; jobs that carry their own executable content in launcher specifications (BYOC) are blocked in confidential computing; and certifi and uv minimum versions are raised following the eMudhra/emSign CA incident.
  • Tensor streaming removal: the legacy push-based nvflare.app_opt.tensor_stream API and Recipe.enable_tensor_streaming() are removed; use the pull-based Tensor Downloader for large-model transfer.
  • Deprecation: HOCON (.conf) and OmegaConf YAML (.yml, .yaml) runtime and job configuration are deprecated and will be removed in 2.10.0; use JSON. Provisioning files such as project.yml are not affected.

Existing confidential computing and ACI deployments must be reprovisioned; there is no in-place upgrade. See the migration guide before upgrading.

See the full 2.9.1 release note: https://nvflare.readthedocs.io/en/2.9.1/release_notes/flare_291.html


What's Changed

Full Changelog: 2.9.0...2.9.1