Add IPv4 ingress & egress IP prefixes for Azure regions - #319
Open
Florian-Wittl wants to merge 2 commits into
Open
Florian-Wittl wants to merge 2 commits into
Florian-Wittl wants to merge 2 commits into
Conversation
Adds new /26 NAT egress IP prefixes for AP20, AP21, BR20, CA20, CH20, EU20 (cf-eu20, cf-eu20-001, cf-eu20-002), EU22, JP20, UK20, US20, US21 (cf-us21, cf-us21-001).
|
Florian Wittl seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
Adds new /30 LB ingress IP prefixes for AP20, AP21, BR20, CA20, CH20, EU20 (cf-eu20, cf-eu20-001, cf-eu20-002), EU22, JP20, UK20, US20, US21 (cf-us21, cf-us21-001).
Florian-Wittl
changed the title
Contributor
|
Thank you for your feedback! We will look into it and come back to you if we have any questions. |
PlamiIG
added
type/outdated
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
3 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.
Add new IPv4 NAT egress and LB ingress IP prefixes for Azure regions
This PR updates both the NAT egress IPs and load balancer ingress IPs for all Azure-based Cloud Foundry regions.
As part of upgrading to the latest generation of Azure NAT Gateways and Load Balancers, which require a new IP SKU (the billing and feature tier of an Azure resource), we are introducing new egress and ingress IP prefixes. Instead of adding individual IP addresses, we have chosen to use CIDR prefixes (/26 for egress, /30 for ingress), which offer more flexibility and consistency for network configuration.
The following regions are affected: AP20, AP21, BR20, CA20, CH20, EU20, EU22, JP20, UK20, US20, US21.
Action required: If you maintain firewall allowlists for outbound or inbound traffic to/from SAP BTP Cloud Foundry applications, please add the new IP prefixes listed for your region to your firewall rules.