Dual-stack ephemeral IPs on instance detail#3101
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| ? `Only ${availableVersions[0]} pools are shown because this instance already has a ${availableVersions[0] === 'v4' ? 'v6' : 'v4'} ephemeral IP.` | ||
| : availableVersions.length === 2 | ||
| ? 'Dual-stack network interfaces support one ephemeral IP per version.' | ||
| : undefined |
There was a problem hiding this comment.
Good catch from Señor gpt-5.3-codex: this message is only correct for dual-stack instances and, more subtly, it assumes there are pools available for both stacks. Need to make it conditional on the stack config and probably the pools.
The new info banner can state a false reason for pool filtering. In app/components/AttachEphemeralIpModal.tsx:79, the
availableVersions.length === 1branch always says the instance already has the opposite-version ephemeral IP.That is not always true:
- single-stack instances with no ephemeral IP also produce
availableVersions.length === 1- dual-stack instances with one open version because of pool availability (not because the other version is attached) can also produce
length === 1This creates incorrect user-facing guidance in the modal.
Open question: should that message only appear when the instance is dual-stack and exactly one ephemeral IP is already attached? If yes, the condition needs attached-version context rather than only
availableVersions.length.
2 participants
Closes #3042
2026-02-27-dual-stack-ips-instance-detail.mp4