feat(faq): update faq lb to resolve conflict

Author: bene2k1

pages/load-balancer/faq.mdx

@@ -3,7 +3,7 @@ meta:
   title: Load Balancer FAQ
   description: Discover Scaleway Load Balancer and find the answers to all your questions about flexible IP addresses, IPv6, multi-cloud offers and more.
 content:
-  h1: Load Balancer FAQ
+  h1: Load Balancer
 dates:
   validation: 2024-09-25
 category: network
@@ -27,6 +27,8 @@ Yes: Check out our documentation on:
 
 By default, each [public](/load-balancer/concepts/#accessibility) Load Balancer is created automatically with a flexible IPv4 address. This is a public IP that can be held in your account even after you delete your Load Balancer. You can optionally also add an IPv6 address.
 
+**This IP address is fixed and does not risk changing once attached to your Load Balancer**.
+
 Your frontend listens to your Load Balancer's public flexible IP address. In case of a failure of the Load Balancer, a replica Load Balancer is immediately spawned and deployed, and the IP address is automatically rerouted to this replica. This is done automatically, by the Load Balancer control subsystems.
 
 When you delete a Load Balancer, you can choose to keep its flexible IP(s) in your account, to reuse later with a new Load Balancer. These flexible IPs are not compatible with other Scaleway products (e.g. Instances, Elastic Metal servers, Public Gateways): each resource has its own set of flexible IPs.
@@ -35,6 +37,12 @@ When you delete a Load Balancer, you can choose to keep its flexible IP(s) in yo
 
 Each Load Balancer can have one public IPv4 address and one public IPv6 address. Currently, it is not possible to assign more than one of each type of IP to a given Load Balancer.
 
+## How can I move my Instance's flexible IP address to my Load Balancer?
+
+This is not possible: flexible IPs are scoped to the resource-type that they were created for. You can move a flexible IP between different Instances, but not move it to a Load Balancer. 
+
+Watch this space for resource-agnostic flexible IPs in the future.
+
 ## Do Load Balancers support external IPv6 connections?
 
 Yes, Load Balancer supports both IPv4 and IPv6 addresses at the frontend. IPv6 can also be used to communicate between the Load Balancer and your backend servers.
@@ -60,6 +68,8 @@ To take advantage of multi-cloud, you must choose a compatible Load Balancer off
 
 All protocols based on `TCP` are supported. This includes `database`, `HTTP`, `LDAP`, `IMAP` and so on. You can also specify `HTTP` to benefit from support and features that are exclusive to this protocol.
 
+Scaleway Load Balancer does not currently support `UDP`.
+
 ## Is it possible to add security to restrict access to a URL or port on the Load Balancer?
 
 Yes, you can restrict the use of a `TCP` port or `HTTP` URL using ACLs. Find more information in our [ACL documentation](/load-balancer/how-to/create-manage-acls/).
@@ -78,4 +88,8 @@ A health check is one of the core concepts for a well-functioning Load Balancer.
 
 ## Can I set up a caching service for my load balanced application?
 
-Yes, this is possible with Scaleway's [Edge Services](/edge-services/) product, currently in Public Beta. By creating an Edge Services pipeline for your Load Balancer, you can access Edge Services caching service reduce load on your origin.
+Yes, this is possible with Scaleway's [Edge Services](/edge-services/) product, currently in Public Beta. By creating an Edge Services pipeline for your Load Balancer, you can access Edge Services caching service reduce load on your origin.
+
+## How can I add extra security such as a firewall or anti-DDOS to my Load Balancer?
+
+This will be available soon via [Edge Services](/edge-services/), watch this space.