Repository navigation
Add IPv4 ingress & egress IP prefixes for Azure regions - #319
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).
|
Thank you for your feedback! We will look into it and come back to you if we have any questions. |
|
Hi @Florian-Wittl , Sincerely, |
|
Please make sure your changes are available in the Ops2go table at https://ops2go.internal.cfapps.eu12.hana.ondemand.com/detailed/centrallandscapes before you request them for the Cloud Foundry environment. |
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.