Skip to content

upcoming: [M3-10267] - Address some loose ends with IP Table and Linode Interfaces #12473

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: develop
Choose a base branch
from

Conversation

coliu-akamai
Copy link
Contributor

@coliu-akamai coliu-akamai commented Jul 3, 2025

Description 📝

  • Fixes case where vpc nat 1 1 address appears twice for Linode Interfaces
  • Shows public IPv4 address if public interface is default IPv4 address for Linode interfaces

Notes - Linode Interfaces:

  • continuing to hide the public IPv4 for the case of having a default route IPv4 VPC interface with a NAT 1:1 address
  • in the case where the default route IPv4 isn't a VPC interface, still showing the VPC NAT 1:1 address to match the IP table behavior of legacy interfaces

Changes 🔄

  • Add new method to determine public IPv4s to show for Linode Interfaces

Preview 📷

row 1 - VPC interface is the default route
row 2 - public interface is the default route

Before After
image image
image image

How to test 🧪

  • Have a Linode using new Interfaces with a public interface and a VPC interface with a nat_1_1 address
  • Have a Linode using legacy interfaces with a VPC interface and a nat_1_1 address

Verification steps

  • confirm nat_1_1 address only shows up once as VPC NAT - IPv4
  • Confirm that if the public interface is the default route, the public IP address is shown
  • Confirm no behavior changes for legacy interface Linode
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 unit tests are passing
  • TypeScript compilation succeeded without errors
  • Code passes all linting rules

…twice and Public IPv4 address hidden when public interface is default route
Comment on lines -371 to -374
// If there is a VPC interface with 1:1 NAT, hide the Public IPv4 IP address row
if (ipv4.vpc.find((vpcIp) => vpcIp.nat_1_1)) {
ipDisplay.shift();
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

functionality moved into createPublicIPv4Display

@coliu-akamai coliu-akamai marked this pull request as ready for review July 3, 2025 20:56
@coliu-akamai coliu-akamai requested a review from a team as a code owner July 3, 2025 20:56
@coliu-akamai coliu-akamai requested review from cpathipa, harsh-akamai and bnussman-akamai and removed request for a team July 3, 2025 20:56
@coliu-akamai coliu-akamai added the Add'tl Approval Needed Waiting on another approval! label Jul 8, 2025
@linode-gh-bot
Copy link
Collaborator

Cloud Manager UI test results

🎉 675 passing tests on test run #6 ↗︎

❌ Failing✅ Passing↪️ Skipped🕐 Duration
0 Failing675 Passing4 Skipped129m 41s

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Review
Development

Successfully merging this pull request may close these issues.

3 participants