upcoming: [M3-10597] – Add VPC IPv6 support in Linode Create flow by dwiley-akamai · Pull Request #12885 · linode/manager

dwiley-akamai · 2025-09-16T19:25:30Z

Description 📝

Add VPC IPv6 support in the Linode Create flow. This encompasses three sub-flows:

Linode Interfaces enabled flag OFF (legacy configs used)
Linode Interfaces enabled flag ON
- Config profile/legacy interfaces selected --> legacy configs used
- Linode Interfaces selected --> Linode Interfaces used

Changes 🔄

Copy updates
- Assign a public IPv4 address for this Linode --> Allow public IPv4 access (1:1 NAT)
- Auto-assign a VPC IPv4 address for this Linode in the VPC --> Auto-assign VPC IPv4 address
Refactor getLegacyInterfaceFromLinodeInterface() to account for whether Dual Stack is enabled or not
Auto-assign VPC IPv6 address checkbox & VPC IPv6 input field added
Allow public IPv6 access checkbox added
Add IPv6 Range button added

Scope 🚢

Upon production release, changes in this PR will be visible to:

All customers (minor UX reorganization in VPC sub-section)
Some customers (the more substantive changes that are feature flagged)
No customers / Not applicable

Target release date 🗓️

9/23/25

Preview 📷

	Interfaces flag OFF	Interfaces flag ON (legacy configs selected)	Interfaces flag ON (Linode Interfaces selected)
Before
After

How to test 🧪

Prerequisites

Ensure the vpc-ipv6 tag is on your account and the VPC IPv6 feature flag is enabled in our Dev Tool. You can point to DevCloud or prod (in which case you should use the Oslo region).

Verification steps

Note

In addition to the conditions outlined below, IPv6 fields should only show if the selected VPC/subnet are Dual Stack.

Linode Interfaces --> enabled flag off...

VPC IPv6 flag off
- Nothing referencing VPC IPv6 is visible nor included in the payload
VPC IPv6 flag on
- Auto-assign VPC IPv6 address checkbox
- checked: interfaces[0].ipv6.slaac[0].range in payload should be "auto"
- unchecked: interfaces[0].ipv6.slaac[0].range in payload should be set to what you input into the VPC IPv6 field
- Allow public IPv6 access checkbox
  - checked: interfaces[0].ipv6.is_public should be true
  - unchecked: interfaces[0].ipv6.is_public should be false
- Assign IPv6 Range
  - interfaces[0].ipv6.ranges array should consist of { range: '...' } objects consisting of what you input into the IPv6 Range fields (empty array if you included none)

Linodes Interfaces --> enabled flag on...

VPC IPv6 flag off
- Nothing referencing VPC IPv6 is visible nor included in the payload
VPC IPv6 flag on
- Configuration Profile Interfaces (Legacy) selected
- See the steps for the previous Linode Interfaces --> enabled flag off... --> VPC IPv6 flag on section above
- Linode Interfaces selected
  - interfaces[0].vpc.ipv6.is_public, interfaces[0].vpc.ipv6.ranges, and interfaces[0].vpc.ipv6.slaac[0].range should have values matching what you'd expect per the previous section

Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support

I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

All tests and CI checks are passing
TypeScript compilation succeeded without errors
Code passes all linting rules

…elected

…elected (when user explicitly chooses them while the Linode Interfaces flag is on, or when Linode Interfaces flag is off and flow uses legacy interfaces)

…e-flow

…ange in E2E and unit tests related to Linode Create and networking flows

hana-akamai

Can we include the VPC IPv6 helper text in the Linode Create flow? (similar to Add Network Interface / Assign Linode to Subnet flows)

hana-akamai · 2025-09-22T20:15:52Z

                        errors.linodeInterfaces?.[index]?.vpc?.ipv6?.slaac?.[0]
                          ?.range?.message
                      }
+                      helperText={generateVPCIPv6InputHelperText(


The helper text doesn't seem to be updating when switching selected subnets

Screen.Recording.2025-09-22.at.4.13.01.PM.mov

Nice catch, I've made a note of it -- the UI for that field and helper text will be changing with a forthcoming PR in the next few days, so we can bundle a fix with that (if the helper text is retained in the updated design)

linode-gh-bot · 2025-09-22T20:29:47Z

Cloud Manager UI test results

🎉 813 passing tests on test run #11 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
`0 Failing`	`813 Passing`	`11 Skipped`	`37m 29s`

hana-akamai

Functionality LGTM!

One thing I noticed is that when the feature flag is off, creating a Linode with a dual-stack VPC still results in an IPv6 address assigned even though the IPv6 options are hidden from the UI and not present in the payload. Not sure if this is expected behavior.

dwiley-akamai · 2025-09-22T21:15:29Z

Functionality LGTM!

One thing I noticed is that when the feature flag is off, creating a Linode with a dual-stack VPC still results in an IPv6 address assigned even though the IPv6 options are hidden from the UI and not present in the payload. Not sure if this is expected behavior.

I believe the back-end logic will still auto-assign one if the user has the Dual Stack account capability

mjac0bs

Thanks for the clear explanation of the various flows.

Things looked good overall when toggling various flags, single vs. dual stack VPCs, and settings. I noticed one discrepancy between the testing instructions and the API payloads:

Linode Interfaces --> enabled flag off...

VPC IPv6 flag on
Allow public IPv6 access checkbox
checked: interfaces[0].ipv6.is_public should be true ✅

unchecked: interfaces[0].ipv6.is_public should be false ❓ <-- The interfaces[0].ipv6.is_public field appears to just not show up in the payload at all when it is false. Just wanted to confirm whether that was intentional.

dwiley-akamai · 2025-09-23T14:41:07Z

unchecked: interfaces[0].ipv6.is_public should be false ❓ <-- The interfaces[0].ipv6.is_public field appears to just not show up in the payload at all when it is false. Just wanted to confirm whether that was intentional.

Good find 🔍 Not intentional, but the API's default value for that field is false -- I verified a linode created through this sub-flow with an unchecked public IPv6 checkbox ends up with a VPC interface where is_public is false

dwiley-akamai self-assigned this Sep 16, 2025

dwiley-akamai added the VPC IPv6 label Sep 16, 2025

github-project-automation Bot added this to Cloud Manager Sep 16, 2025

github-project-automation Bot moved this to Review in Cloud Manager Sep 16, 2025

VPC IPv6 functionality in Linode Create flow when Linode Interfaces s…

fbda2de

…elected

dwiley-akamai changed the base branch from develop to vpc-ipv6-remaining September 18, 2025 19:07

dwiley-akamai force-pushed the M3-10597-vpc-ipv6-linode-create-flow branch from 2fa85f2 to fbda2de Compare September 18, 2025 20:43

DevDW added 4 commits September 19, 2025 17:31

VPC IPv6 functionality in Linode Create flow when legacy interfaces s…

f210562

…elected (when user explicitly chooses them while the Linode Interfaces flag is on, or when Linode Interfaces flag is off and flow uses legacy interfaces)

Update copy in tests

125c3d4

Passing VPCPanel.test.tsx

1f83b7a

Update referenced copy in linode-config.spec.ts

9d2b9f4

dwiley-akamai marked this pull request as ready for review September 22, 2025 17:20

dwiley-akamai requested review from a team as code owners September 22, 2025 17:20

dwiley-akamai requested review from cpathipa, hana-akamai, jdamore-linode and mjac0bs and removed request for a team September 22, 2025 17:20

DevDW added 4 commits September 22, 2025 13:21

Merge branch 'vpc-ipv6-remaining' into M3-10597-vpc-ipv6-linode-creat…

11eff13

…e-flow

Added changeset: Add VPC IPv6 support in Linode Create flow

d9bfe22

Added changeset: Reflect 'Allow public IPv4 access (1:1 NAT)' copy ch…

f1fea64

…ange in E2E and unit tests related to Linode Create and networking flows

Remove changesets and update changelog directly

e6ae3b4

hana-akamai reviewed Sep 22, 2025

View reviewed changes

Helper text for VPC IPv6 fields for parity with Assign Linodes drawer

8af1b35

hana-akamai reviewed Sep 22, 2025

View reviewed changes

dwiley-akamai mentioned this pull request Sep 22, 2025

feat: [M3-9182] - vpc-ipv6-remaining feature branch → staging #12900

Merged

hana-akamai approved these changes Sep 22, 2025

View reviewed changes

github-project-automation Bot moved this from Review to Approved in Cloud Manager Sep 22, 2025

mjac0bs approved these changes Sep 22, 2025

View reviewed changes

dwiley-akamai merged commit c406455 into linode:vpc-ipv6-remaining Sep 23, 2025
35 checks passed

github-project-automation Bot moved this from Approved to Merged in Cloud Manager Sep 23, 2025

Navigation Menu

Uh oh!

upcoming: [M3-10597] – Add VPC IPv6 support in Linode Create flow - #12885

upcoming: [M3-10597] – Add VPC IPv6 support in Linode Create flow#12885
dwiley-akamai merged 10 commits into
linode:vpc-ipv6-remainingfrom
dwiley-akamai:M3-10597-vpc-ipv6-linode-create-flow

dwiley-akamai commented Sep 16, 2025 •

edited

Loading

Uh oh!

hana-akamai left a comment

Uh oh!

hana-akamai Sep 22, 2025

Uh oh!

dwiley-akamai Sep 22, 2025

Uh oh!

linode-gh-bot commented Sep 22, 2025

Uh oh!

hana-akamai left a comment

Uh oh!

dwiley-akamai commented Sep 22, 2025

Uh oh!

mjac0bs left a comment

Uh oh!

dwiley-akamai commented Sep 23, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Uh oh!

Conversation

dwiley-akamai commented Sep 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description 📝

Changes 🔄

Scope 🚢

Target release date 🗓️

Preview 📷

How to test 🧪

Prerequisites

Verification steps

As an Author, to speed up the review process, I considered 🤔

As an Author, before moving this PR from Draft to Open, I confirmed ✅

Uh oh!

hana-akamai left a comment

Choose a reason for hiding this comment

Uh oh!

hana-akamai Sep 22, 2025

Choose a reason for hiding this comment

Uh oh!

dwiley-akamai Sep 22, 2025

Choose a reason for hiding this comment

Uh oh!

linode-gh-bot commented Sep 22, 2025

Cloud Manager UI test results

🎉 813 passing tests on test run #11 ↗︎

Uh oh!

hana-akamai left a comment

Choose a reason for hiding this comment

Uh oh!

dwiley-akamai commented Sep 22, 2025

Uh oh!

mjac0bs left a comment

Choose a reason for hiding this comment

Uh oh!

dwiley-akamai commented Sep 23, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

dwiley-akamai commented Sep 16, 2025 •

edited

Loading