Repository navigation
docs: add IPv6 readiness guidance for Compute - #118
Open
dlotterman wants to merge 8 commits into
Open
dlotterman wants to merge 8 commits into
dlotterman wants to merge 8 commits into
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
dlotterman
force-pushed
the
dlott_agents+ipv6
branch
from
November 3, 2026 22:04
7e40b14 to
9ede253
Compare
Add a quickstart that reaches an Instance by its private name and then by a custom name, a guide to private zones, records, and network associations, a limits and behavior reference, and Private DNS troubleshooting. Stop describing Private DNS as planned.
Use an AAAA record in the quickstart, since CNAMEs into another zone are not followed yet. Add the Network Admin role, use made-up names in examples, and correct the troubleshooting reasons.
Private zones no longer need a zone class.
dlotterman
force-pushed
the
dlott_agents+ipv6
branch
from
November 4, 2026 19:22
0cd7e41 to
fd3687b
Compare
|
|
Describe private zone visibility only as association-based, and say what happens past 256 zones on a network, since that isn't refused yet.
dlotterman
force-pushed
the
dlott_agents+ipv6
branch
from
November 10, 2026 23:36
fd3687b to
452e8df
Compare
Compute and gVPC are IPv6 only. Apps that bind to IPv4 (0.0.0.0, listen 80;) or connect to IPv4 addresses fail, and the docs didn't say so until a deploy failed. - Add an "IPv6 readiness" section to Compute troubleshooting with the pre-deploy checklist, bind examples, a local check, and steps for agents. - Add a short "IPv6 readiness" section to the Compute overview that links to it, and note that Instances are IPv6 only. - Link the first-workload tutorial's "What's next" and the ALB prerequisites to the readiness section. - Tell agents on the deploy-workloads page to search the app's code and config for IPv4 addresses before they deploy, and note in the configuration page that env values should use hostnames.
dlotterman
force-pushed
the
dlott_agents+ipv6
branch
from
November 11, 2026 00:06
452e8df to
a8ae253
Compare
dlotterman
force-pushed
the
dlott_agents+ipv6
branch
from
November 11, 2026 01:31
a8ae253 to
a64b59e
Compare
dlotterman
force-pushed
the
dlott_agents+ipv6
branch
from
November 11, 2026 01:37
a64b59e to
a8ae253
Compare
Contributor
Author
|
Theres some real improvement here: I think this has enough merit to merge and anything that gets missed we can include in #157 or other cleanup |
This branch was successfully deployed
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
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.
Summary
Compute and gVPC are IPv6 only. Agents and users keep running into problems because apps bind to IPv4 (
0.0.0.0,listen 80;) or connect to IPv4 addresses, and the docs don't say so until a deploy fails.This PR puts the guidance where people and agents look first, without adding a new page.
sscheck, and steps for agents.Testing
I compared this branch with its parent on seven IPv6-related agent tasks, four reps each, across Haiku, Luna, DeepSeek and GLM (28 runs per model per condition). Accuracy with this change versus without: Haiku 100% vs 93%, Luna 93% vs 82%, DeepSeek 96% vs 93%, GLM 96% vs 96%. Most of the gain is on the "sweep an app for IPv4 assumptions" task, where agents without this change told users to use IPv6 literals because they thought private DNS names were unavailable. Keyword scoring is crude and samples are small, so treat the numbers as directional.
Review notes