Mvm docs - #704
Merged
Merged
Conversation
…re to migrate — 21 pages covering lifecycle, the 8-hour ceiling and endAt, filesystem-only checkpoints, sizes, the in-guest secrets tradeoff and the supported/unsupported split, with the existing Sandboxes docs left untouched and still first
…nly the default pooled) instead of implying any size can be published, and rewrite the secrets page as an explicit before/after — the substituting proxy moved from the VM host into the guest as root, which changes only the blast radius of an in-sandbox privilege escalation
…easurable from inside the guest (nproc reports the host, not the share) so the numbers were unsubstantiated; say instead that CPU follows memory and that cpuCount and diskMB are accepted but are not controls on this runtime
…it cannot reach the platform's launch call, and it opts the create out of the warm pool into a cold launch for no benefit
…rying a rootfs image are refused outright (which is what most existing templates are, so they need rebuilding), and disk is fixed at ~16GB with diskMB accepted-but-ignored, down from a 20GB default; both added to the checklist, FAQ and comparison tables
…ublish.sh and microvm_common.go, and correct the customer-facing range to the 2-8GB we can actually offer — publish.sh treats 2048 as the vCPU floor and warns below it, so listing 512/1024 as available sizes was wrong
…runtime's tiers — 1/4/8GB carry over, 2GB is new, 16GB has no equivalent; the sub-2048 publish warning is expected for the 1GB tier since the current 1GB tier is already best-effort CPU, so it is not a regression
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
breardon2011
force-pushed
the
mvm-docs
branch
from
September 2, 2026 01:40
4dd8cd7 to
c1c9417
Compare
breardon2011
marked this pull request as ready for review
September 2, 2026 02:00
…roVM tab, per review — v2 mirrors v1's page structure one-for-one under v2/**, drops all infrastructure vocabulary in favour of 'v2 with breaking changes', keeps removed features as honest not-available pages so the structures still match, and adds a dedicated migrating-from-v1 guide
breardon2011
force-pushed
the
mvm-docs
branch
from
September 2, 2026 16:21
3c94ea9 to
2dae0b9
Compare
… entry in navigation.versions, so v2 now leads and v1 stays reachable from the switcher
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a Sandboxes · MicroVM tab (21 pages) beside the existing Sandboxes docs, which are untouched and still first — customers can read both while preparing to move.
Written against behaviour verified on dev. The migration-relevant findings:
Also adds deploy/microvm/SIZE-TIERS.md, the prerequisites for publishing a size tier.
Microvm branch WIP here, mostly complete: #703