docs: release 2.0

[polarweasel]

Final cleanup for v2.0.

(Yes, I messed up the original PR for this. Was faster to cherry-pick and recreate it.)

Related issues

Closes #4202.

Type of Change

• Add - New feature or capability
• Change - Changes in existing functionality
• Fix - Bug fixes
• Remove - Removed features or deprecated functionality
• Internal - Internal changes (refactoring, tests, docs, etc.)

Breaking Changes

• This PR contains breaking changes

Testing

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed
• No testing required (docs, internal refactor, etc.)

Signed-off-by: Alex Ball aball@nvidia.com

[coderabbitai]

Summary by CodeRabbit

• Documentation

  • Added clear “New,” “Upcoming,” and v2.0 badges to relevant documentation pages.
  • Improved formatting, guidance presentation, and code example readability.
  • Added redirects for firmware updates, core metrics, and boot interfaces.
  • Updated compatibility tables without changing supported entries.

• Changelog

  • Improved release status labels and metadata.
  • Published the v2.0 release overview, including operations, security, telemetry, and multi-architecture updates.
  • Added guidance to review REST API database migration requirements before upgrading.

Walkthrough

The PR updates documentation badges, Markdown formatting, changelog metadata, release notes, redirects, and the Fern configuration version for the 2.0 documentation release.

Changes

Documentation page updates

Layer / File(s)	Summary
Page metadata and formatting docs/configuration/*, docs/hcl.md, docs/manuals/vpc/*, docs/operations/*, docs/provisioning/*	Documentation headings now use release badges. Selected Markdown content was reformatted, compatibility tables were normalized, and one code fence now specifies text.
Release note metadata and content fern/changelog/*	Changelog entries now use updated lifecycle labels and tags. The v2.0 entry is marked current and includes release details and migration guidance.
Documentation navigation and Fern configuration fern/docs.yml, fern/fern.config.json	Three documentation redirects were added. The Fern version was updated from 5.80.4 to 5.89.1.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• NVIDIA/infra-controller#4448: Updates the same documentation files, badges, changelog entries, redirects, and Fern configuration.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR adds v2.0 badges to document titles, which conflicts with issue #4202's requirement to remove versioning.	Remove version badges where issue #4202 requires versioning removal, while retaining the required New, deprecated, and changelog updates.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the documentation release as the primary change.
Description check	✅ Passed	The description explains the v2.0 documentation cleanup and identifies the related issue.
Out of Scope Changes check	✅ Passed	The documented changes support the v2.0 documentation release and do not show unrelated scope.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🌿 Preview your docs: https://nvidia-preview-pull-request-4456.docs.buildwithfern.com/infra-controller

Here are the markdown pages you've updated:

• infra-controller/documentation/release-notes/2026/1/23
• infra-controller/documentation/release-notes/2026/2/12
• infra-controller/documentation/release-notes/2026/5/15
• infra-controller/documentation/release-notes/2026/7/31

[nv-dmendoza]

+1

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/manuals/vpc/flat_vpcs_zero_dpu.md`:
- Line 374: Split the mixed fenced example around the REST request and CLI
command: keep the GET request in a text or HTTP-specific code fence, and move
nicocli instance get <instance-id> into a separate bash or sh fence. Preserve
both examples unchanged apart from their fence types.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: f7cba382-2301-4fc2-be3d-7f431de8c35c

📥 Commits

Reviewing files that changed from the base of the PR and between 0021e8c and b06e824.

📒 Files selected for processing (18)

• docs/configuration/component-manager-rms.md
• docs/configuration/dns.md
• docs/configuration/machine_identity.md
• docs/configuration/secrets-storage.md
• docs/hcl.md
• docs/manuals/vpc/flat_vpcs_zero_dpu.md
• docs/operations/firmware-updates.md
• docs/operations/monitoring-health.md
• docs/operations/nvos-password-rotation.md
• docs/operations/tenant-lifecycle-cleanup.md
• docs/provisioning/boot-interfaces-and-dpu-modes.md
• docs/provisioning/machine-validation.md
• fern/changelog/2026-01-23.mdx
• fern/changelog/2026-02-12.mdx
• fern/changelog/2026-05-15.mdx
• fern/changelog/2026-07-31.mdx
• fern/docs.yml
• fern/fern.config.json

[polarweasel]

@coderabbitai the "remove versioning" item in #4202 refers to not using Fern's built-in versioning mechanism, which was addressed in a previous PR.

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@polarweasel Understood. The “remove versioning” objective applies only to Fern built-in versioning. The earlier PR already completed that work. I will not treat the version badges in this PR as a conflict with #4202.

🐇

---

✏️ Learnings added

Learnt from: polarweasel
URL: https://github.com/NVIDIA/infra-controller/pull/4456

Timestamp: 2026-07-31T19:47:44.085Z
Learning: For NVIDIA/infra-controller issue `#4202`, “remove versioning” means removing Fern built-in versioning. It does not prohibit documentation release badges such as `v2.0`. The Fern built-in versioning removal was completed in an earlier PR.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

_{You are interacting with an AI system.}

[nv-dmendoza]

LGTM, adds formatting changes and other updates that we want