Skip to content

upcoming: [UIE-10179] - Use new hostname endpoints in Service URIs#13439

Open
hana-akamai wants to merge 10 commits intolinode:developfrom
hana-akamai:UIE-10179-service-uri-hosts-endpoints
Open

upcoming: [UIE-10179] - Use new hostname endpoints in Service URIs#13439
hana-akamai wants to merge 10 commits intolinode:developfrom
hana-akamai:UIE-10179-service-uri-hosts-endpoints

Conversation

@hana-akamai
Copy link
Contributor

@hana-akamai hana-akamai commented Feb 25, 2026

Description 📝

Use new hosts endpoints field to populate General and PgBouncer Service URIs. If a VPC is public, display both public and private Service URIs

Changes 🔄

  • Use new hosts endpoints field to populate General and PgBouncer Service URIs
    • If a VPC is public, display both public and private Service URIs
  • Remove deprecated connection_pool_port property
  • Minor refactoring

Scope 🚢

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

  • All customers
  • Some customers (e.g. in Beta or Limited Availability)
  • No customers / Not applicable

Target release date 🗓️

March

Preview 📷

Summary Service URIs Networking Service URIs
No VPC no vpc n no vpc
VPC with no public access private vpc n vpc private
VPC with public access public vpc n vpc public

How to test 🧪

Prerequisites

(How to setup test environment)

  • Use the legacy MSW and ensure you have the pgbouncer and hostnamesEndpoint feature flag on

Verification steps

(How to verify changes)

  • In the makeMockDatabase function in serverHandlers.ts, comment/uncomment out some of the values to simulate No VPC (public only), VPC with no public access (private only), VPC with public access (private and public)
  • Go to a postgres Database cluster's details page
  • If there is no VPC, you should see a general and pgbouncer service URI with public addresses
  • If there is a VPC with no public access, you should see a general and pgbouncer service URI with private addresses
  • If there is a VPC with public access, you should see 2 general and pgbouncer service URIs with public and private addresses along with an info tooltip for the private address
  • Test different screen sizes, test mysql database (there should be no pgbouncer service URIs, only general)
pnpm test ServiceURI
pnpm test DatabaseConnectionPools

@hana-akamai hana-akamai self-assigned this Feb 25, 2026
@hana-akamai hana-akamai added the DBaaS Relates to Database as a Service label Feb 25, 2026
@hana-akamai hana-akamai marked this pull request as ready for review February 26, 2026 21:18
@hana-akamai hana-akamai requested a review from a team as a code owner February 26, 2026 21:18

// Mock a database cluster with a public VPC Configuration
database.private_network = {
public_access: true,
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
public_access: true, // Set to false to mock a private VPC configuration

role: 'standby',
address: 'private-replica-db-mysql-standby-0.b.linodeb.net',
port: 15847,
port: 3306,
Copy link
Contributor

Choose a reason for hiding this comment

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

What was the reason for the port change in the mock data?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

To more explicitly display the difference between general service URI port and PgBouncer service URI port

}}
text={
'Private endpoints are resolvable only for resources within the VPC Subnet. Public endpoints are resolvable outside the VPC.'
}
Copy link
Contributor

@smans-akamai smans-akamai Feb 27, 2026

Choose a reason for hiding this comment

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

For the tooltip that appears when both private and public Service URIs are displayed. It looks like the Private Service URI tooltip explains the behavior for the endpoints used in both the private and public service URI fields.

Would it make sense to have a tooltip for each field that displays the public and private parts of the message in this case?

Image

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think it makes sense to keep the tooltip for the private field since public is self-explanatory

Copy link
Contributor

@smans-akamai smans-akamai left a comment

Choose a reason for hiding this comment

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

Tested out the behavior and the changes look good!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

DBaaS Relates to Database as a Service

Projects

Status: Review

Development

Successfully merging this pull request may close these issues.

2 participants