Skip to content

RC: Seamless endpoint migration - Dynamic endpoints/Endpoint redirection#2751

Open
cmilesb wants to merge 35 commits intomainfrom
DOC-5431
Open

RC: Seamless endpoint migration - Dynamic endpoints/Endpoint redirection#2751
cmilesb wants to merge 35 commits intomainfrom
DOC-5431

Conversation

@cmilesb
Copy link
Copy Markdown
Contributor

@cmilesb cmilesb commented Feb 5, 2026

Note

Medium Risk
Mostly documentation changes, but it introduces new guidance for endpoint redirection/migration where inaccuracies could mislead users during production cutovers. Also removes a Rust Cargo.lock, which can impact reproducibility of that example’s builds.

Overview
Adds Redis Cloud documentation for dynamic endpoints and endpoint redirection to enable seamless traffic migration between databases without changing application endpoints.

Updates existing connection and migration guides to explain legacy static vs dynamic endpoints (post–Apr 21, 2026 behavior), recommend migrating clients to dynamic endpoints, and describe redirecting endpoints as a post-migration step; also expands the Essentials→Pro upgrade flow to include endpoint migration requirements (including port matching) and revert behavior.

Standardizes Prometheus setup instructions by introducing a reusable embed for retrieving the Prometheus endpoint and wiring it into Prometheus/New Relic/Dynatrace integration docs, plus a new “Connect to Prometheus” section in monitor-performance.

Removes the Rust rate-limiter demo Cargo.lock.

Reviewed by Cursor Bugbot for commit a408c18. Bugbot is set up for automated code reviews on this repo. Configure here.

@cmilesb cmilesb requested review from a team and NoamSternRedis February 5, 2026 22:35
@cmilesb cmilesb self-assigned this Feb 5, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Feb 5, 2026

DOC-5431

Copy link
Copy Markdown
Contributor

@andy-stark-redis andy-stark-redis left a comment

Choose a reason for hiding this comment

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

Embed paths need to be fixed but otherwise LGTM.


### Dynamic endpoints

As of {{RELEASE DATE}}, Redis Cloud now generates dynamic endpoints for all databases. Databases created before {{RELEASE DATE}} can still view both static endpoints and dynamic endpoints. Static endpoints will still work at this time, but they may be deprecated in the future.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Just checking that the {{ RELEASE DATE}} still isn't known yet?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

current eta is March 22

cmilesb and others added 2 commits February 6, 2026 15:56
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
@cmilesb cmilesb requested a review from a team February 9, 2026 21:41
Copy link
Copy Markdown
Contributor

@kaitlynmichael kaitlynmichael left a comment

Choose a reason for hiding this comment

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

Didn't get through it all yet, but here's a few small things.

Co-authored-by: Kaitlyn Michael <76962844+kaitlynmichael@users.noreply.github.com>
@cmilesb cmilesb requested a review from a team February 18, 2026 18:08
Copy link
Copy Markdown
Contributor

@andy-stark-redis andy-stark-redis left a comment

Choose a reason for hiding this comment

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

A few minor style suggestions, otherwise LGTM.


### Dynamic endpoints

As of {{RELEASE DATE}}, Redis Cloud now generates dynamic endpoints for all databases. Databases created before {{RELEASE DATE}} can still view both static endpoints and dynamic endpoints. Static endpoints will still work at this time, but they may be deprecated in the future.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

current eta is March 22


### Dynamic endpoints

As of {{RELEASE DATE}}, Redis Cloud now generates dynamic endpoints for all databases. Databases created before {{RELEASE DATE}} can still view both static endpoints and dynamic endpoints. Static endpoints will still work at this time, but they may be deprecated in the future.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think we need a section in the docs on "Dynamic endpoints" (maybe in the configuration page, or connectivity?). That would explain a few sentences what Dynamic endpoints are and that you can redirect endpoints, alias of the dB endpoint, bla bla bla.
And link it from here and from other places in the docs

cmilesb and others added 2 commits February 24, 2026 14:03
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
@jit-ci
Copy link
Copy Markdown

jit-ci bot commented Feb 24, 2026

🛡️ Jit Security Scan Results

CRITICAL HIGH MEDIUM

✅ No security findings were detected in this PR


Security scan by Jit

To illustrate, suppose you want to migrate a 1&nbsp;GB source database without replication to a target database with replication enabled. Here, the target database memory limit should be at least 2.5&nbsp;GB to avoid data loss.

Once the databases are synced, you can disable Active-Passive for the target database. Before doing so, however, verify that apps and other connections have switched to the target database; otherwise, you may lose data.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Here I want to add a note regarding the API. I'll describe the process and you will do your magic to make it clear and put here where you think:)

  • In the UI, the process is as you described. You just search for your DB in the search
  • Using the API is different. Because the Dynamic endpoint can move, the user needs to give us the cluster endpoint and not dynamic one. In the UI we don't need to do adjustments because we just choose the actual DB.. not the endpoint
  • What we did:
  • We exposed a new attribute in the API on the GET DB call: replicaAsSourceEndpoints
  • So the customer will need to use those endpoints if they want to set the replica of the program programmatically.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

We should definitely put this in the API docs. I'll work on adding this to the user docs later.

@cmilesb cmilesb requested a review from NoamSternRedis March 3, 2026 21:05
@cmilesb cmilesb requested a review from a team March 12, 2026 19:45
1. [Create a new database in Redis Cloud Pro](#create-rcp) with the right specifications to be able to migrate your database.

1. [Migrate your Essentials database](#migrate-database) to your new Redis Cloud Pro database.
1. [Migrate the data in your Essentials database](#migrate-database) to your new Redis Cloud Pro database.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Broken anchor link to renamed heading

Medium Severity

The link at line 28 points to #migrate-database, but the heading it references was renamed from ### Migrate database to ### Migrate data, which generates the auto-anchor #migrate-data. This results in a broken in-page navigation link.

Additional Locations (1)
Fix in Cursor Fix in Web

1. [Migrate your Essentials database](#migrate-database) to your new Redis Cloud Pro database.
1. [Migrate the data in your Essentials database](#migrate-database) to your new Redis Cloud Pro database.

1. [Migrate your endpoints](#migrate-endpoints) to your new Redis Cloud Pro database.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Anchor #migrate-endpoints references nonexistent heading

Medium Severity

The new link at line 30 points to #migrate-endpoints, but the corresponding section heading at line 91 is ### Redirect database endpoints, which auto-generates the anchor #redirect-database-endpoints. No heading with anchor #migrate-endpoints exists anywhere on this page, so the link is broken.

Additional Locations (1)
Fix in Cursor Fix in Web

Copy link
Copy Markdown
Contributor

@andy-stark-redis andy-stark-redis left a comment

Choose a reason for hiding this comment

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

LGTM

@cmilesb cmilesb requested review from a team and andy-stark-redis April 13, 2026 21:04
Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 3 total unresolved issues (including 2 from previous reviews).

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit a408c18. Configure here.





Copy link
Copy Markdown

Choose a reason for hiding this comment

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

TODO placeholder text left in published documentation

High Severity

The "Unblock traffic to the source database" section contains only a TODO placeholder (TODO - need a setup to work first) instead of actual documentation. This section is referenced earlier in the page (line 47 links to #unblock-traffic-to-the-source-database), so users following the endpoint redirection workflow will land on an incomplete section with no instructions.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit a408c18. Configure here.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants