Skip to content

docs: Add Release 11 (Metis) release notes#215

Open
JeromeJaggi wants to merge 1 commit into
prod-stagingfrom
jeromejaggi/release-11-metis-notes
Open

docs: Add Release 11 (Metis) release notes#215
JeromeJaggi wants to merge 1 commit into
prod-stagingfrom
jeromejaggi/release-11-metis-notes

Conversation

@JeromeJaggi

Copy link
Copy Markdown
Member

Summary

Adds a Releases section to the docs, with a landing index and the first public release notes: Release 11 (Metis).

New pages

  • pages/releases/index.mdx — releases landing page with a summary table.
  • pages/releases/r11-metis.mdx — Release 11 (Metis) notes, organized into a Platform / Tooling split:
    • Platform: Branching, Checkpointing, Custom filesystems and persistent volumes, Custom network configuration, Network shield and relay, Plugin API.
    • Tooling: Agent (image pruning, improved health checks), CLI (--follow on start/restart), Dashboard (revamped dashboard, online enterprise documentation).

Navigation

  • Adds a Releases category to zudoku.config.tsx and a /releases/releases/index redirect.

Notes

  • Only items scoped for public release notes are included; internal/omitted items from the source are excluded.
  • Marketing-voice intro is preserved verbatim inside a {/* vale off */} block; the rest of the body is written to pass Vale (make lint is clean, 0 errors).
  • Learn more links for the enterprise/CLI tooling items point to https://unikraft.com/docs/introduction.
  • Release date set to 2026-07-03.

Add a Releases section with a landing index and the Release 11 (Metis)
release notes, covering the platform features (branching, checkpointing,
custom filesystems and persistent volumes, custom network configuration,
network shield and relay, and the plugin API) and the supporting
tooling. Wire the Releases category and the /releases redirect into the
Zudoku navigation.

Signed-off-by: Jerome Jaggi <jerome@unikraft.io>
@JeromeJaggi JeromeJaggi temporarily deployed to pull-requests July 3, 2026 16:44 — with GitHub Actions Inactive

Release 11 is a major step forward for the platform, and it comes jam-packed. Headlining it are advanced snapshotting capabilities — branching and checkpointing — alongside custom filesystems for persistent storage, and a plugin API that transparently extends a microVM with your own code. A sandbox plugin built on it is already available to enterprise customers.

Also on the sandbox track — but useful for all use cases — is our new network shield. It sits between any microVM and the public Internet, filtering traffic and injecting tokens, credentials or secrets so they never have to live inside the microVM (read: agent) itself. The shield is implemented as a minimalist, scale-to-zero microVM of its own, so it is as strongly isolated as everything else you run — and, being a microVM, extremely flexible in what it can do (iptables, eBPF, and so on).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Microsoft.SentenceLength] Try to keep sentences short (< 30 words).


**Why it matters:** Branching is the foundation for stateful instance workflows on the platform.
It enables fast, low-downtime cloning of live workloads for testing, scaling, and recovery.
It applies to many use cases, including launching sub-agents or branching large production databases to safely develop on them.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[Microsoft.Adverbs] Remove 'safely' if it's not important to the meaning of the statement.


**Requirements and limitations:** Requires a valid license.
Checkpointing only works with block-based volumes (for example, `ext4`).
You load checkpoints by creating a new instance from them; in-place rewind of an instance to a previous checkpoint isn't part of this release.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Microsoft.Semicolon] Try to simplify this sentence.


### Custom network configuration

You can now create microVMs with several network interfaces and fully custom network configuration via `POST /v1/instances`:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[write-good.Weasel] 'several' is a weasel word!

```

The first interface is the **primary interface**: the `private_ip` that the instance returns always comes from it, and the proxy forwards traffic to the primary interface's IP.
If you omit `ip` and `tap_name`, the platform chooses a TAP device from its pool; you must specify both fields or neither.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Microsoft.Semicolon] Try to simplify this sentence.


#### Image pruning

The agent now automatically prunes unused images from disk.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[Microsoft.Terms] Prefer 'personal digital assistant' over 'agent'.

#### Image pruning

The agent now automatically prunes unused images from disk.
When no running or stopped instance references an image any longer, the agent garbage-collects it to reclaim space; if you need the image again later, the agent pulls it on demand from the registry.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Microsoft.SentenceLength] Try to keep sentences short (< 30 words).

#### Image pruning

The agent now automatically prunes unused images from disk.
When no running or stopped instance references an image any longer, the agent garbage-collects it to reclaim space; if you need the image again later, the agent pulls it on demand from the registry.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [vale] reported by reviewdog 🐶
[Microsoft.Terms] Prefer 'personal digital assistant' over 'agent'.

#### Image pruning

The agent now automatically prunes unused images from disk.
When no running or stopped instance references an image any longer, the agent garbage-collects it to reclaim space; if you need the image again later, the agent pulls it on demand from the registry.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Microsoft.Semicolon] Try to simplify this sentence.

You can now check real-time metrics for all your resources and inspect instance logs.
You can start and stop instances directly from the UI and manage your organization, including user management.

Coming soon, you'll also be able to SSH directly into a particular instance, create and delete instances, and inspect the lifetime of an instance as you checkpoint or fork it.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] reported by reviewdog 🐶
[Microsoft.SentenceLength] Try to keep sentences short (< 30 words).

@github-actions github-actions Bot temporarily deployed to pull-requests July 3, 2026 16:47 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants