Deprecate machine-scoped egress IPs and add documentation about the migration process#2382
Merged
Deprecate machine-scoped egress IPs and add documentation about the migration process#2382
Conversation
kcmartin
reviewed
Apr 19, 2026
Contributor
kcmartin
left a comment
kcmartin
left a comment
There was a problem hiding this comment.
Added a couple suggestions, otherwise LGTM!
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Summary of changes
Remove all mentions of how to allocate a new machine-scoped egress IP.
Add documentation about the new
fly machine egress-ip promotecommand for migrating between machine-scoped and app-scoped egress IPs.Notes
Ship this change after the next
flyctlrelease (likely Monday, Apr 20)