upcoming: [M3-10212] – Add VPC IPv6 support in Linode Add/Edit Config dialog #13209
Conversation
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
…odeConfigSchema for interfaces property
…per stakeholder feedback; passing VPCPanel.test.tsx
…AC range instead of address
…required() from range property in slaacSchema; make range property of IPv6SLAAC optional (edge case where it does not get returned) & minor related change in getLinodeInterfaceIPs() util
Collaborator
Cloud Manager UI test results🔺 2 failing tests on test run #7 ↗︎
Details
TroubleshootingUse this command to re-run the failing tests: pnpm cy:run -s "cypress/e2e/core/objectStorage/object-storage.e2e.spec.ts,cypress/e2e/core/linodes/clone-linode.spec.ts" |
||||||||||||||||||||
Member
|
For cases where we're using legacy config profile interfaces, an IPv6 VPC is attached, and I check "Allow public IPv6 access", should these notices go away?
|
bnussman-akamai
approved these changes
Dec 23, 2025
Member
bnussman-akamai
left a comment
bnussman-akamai
left a comment
There was a problem hiding this comment.
Things seems to be working well!
There may or may not be more work needed on what gets shown to the user when a VM has no internet connectivity
hana-akamai
approved these changes
Dec 23, 2025
| const [newVlan, setNewVlan] = React.useState(''); | ||
|
|
||
| const [autoassignIPv6VPCAddress, setAutoassignIPv6VPCAddress] = | ||
| React.useState<boolean>(false); |
Contributor
There was a problem hiding this comment.
Can we default this to true similar to IPv4?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Description 📝
Add VPC IPv6 support in Linode Add/Edit Config dialog
Changes 🔄
constants.tsandutilities.tsx, respectivelyUpdateConfigProfileInterfacesSchemaand use it inUpdateLinodeConfigSchemato avoid type/schema errorsScope 🚢
Upon production release, changes in this PR will be visible to:
Target release date 🗓️
January 2026
Preview 📷
How to test 🧪
Prerequisites
Ensure the VPC IPv6 feature flag is on and your account has VPC IPv6 customer tags.
Verification steps
ethslotsVPC IPv6and IPv6 range fieldsethslot, the payload and response should reflect no IPv6 data changes (this relates to thehandleChangefunctions inInterfaceSelect.tsx)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
As an Author, before moving this PR from Draft to Open, I confirmed ✅