Adding new BYOIP changelog entry for Gateway (#24605)

* Adding new BYOIP changelog entry for Gateway

* Discard changes to package-lock.json

* Discard changes to tsconfig.json

* Update procedure

* Update link

* Update alt text

---------

Co-authored-by: NuelEdeh <[email protected]>
Co-authored-by: Max Phillips <[email protected]>
Co-authored-by: Max Phillips <[email protected]>

Author: 3 people

src/assets/images/gateway/Gateway-byoip-dedicated-egress-ips.png

@@ -0,0 +1,17 @@
+---
+title: Gateway BYOIP Dedicated Egress IPs now available.
+description: Gateway now supports egressing customer traffic using IPv4/v6 prefixes they already own.
+products:
+  - gateway
+date: "2025-08-21"
+---
+
+Enterprise Gateway users can now use Bring Your Own IP (BYOIP) for dedicated egress IPs.
+
+Admins can now onboard and use their own IPv4 or IPv6 prefixes to egress traffic from Cloudflare, delivering greater control, flexibility, and compliance for network traffic.
+
+Get started by following the [BYOIP onboarding process](/cloudflare-one/policies/gateway/egress-policies/dedicated-egress-ips/#bring-your-own-ip-address-byoip). Once your IPs are onboarded, go to **Gateway** > **Egress policies** and select or create an egress policy. In **Select an egress IP**, choose _Use dedicated egress IPs (Cloudflare or BYOIP)_, then select your BYOIP address from the dropdown menu.
+
+![Screenshot of a dropdown menu adding a BYOIP IPv4 address as a dedicated egress IP in a Gateway egress policy](~/assets/images/gateway/Gateway-byoip-dedicated-egress-ips.png)
+
+For more information, refer to [BYOIP for dedicated egress IPs](/cloudflare-one/policies/gateway/egress-policies/dedicated-egress-ips/#bring-your-own-ip-address-byoip).