From 933c8b96f7ece80988b51685a97ffbbf4032cac3 Mon Sep 17 00:00:00 2001
From: Nox <5402193+Nox-404@users.noreply.github.com>
Date: Fri, 2 Feb 2024 09:48:53 +0100
Subject: [PATCH] feat(doc): deprecate scw-loadbalancer-force-internal-ip
 annotation (#157)

---
 docs/loadbalancer-annotations.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/loadbalancer-annotations.md b/docs/loadbalancer-annotations.md
index 5d5e76c..6d59532 100644
--- a/docs/loadbalancer-annotations.md
+++ b/docs/loadbalancer-annotations.md
@@ -128,8 +128,8 @@ This is the annotation that modifes what occurs when a backend server is marked
 The default value is `on_marked_down_action_none` and the possible values are `on_marked_down_action_none` and `shutdown_sessions`.
 
 ### `service.beta.kubernetes.io/scw-loadbalancer-force-internal-ip`
-This is the annotation that force the usage of InternalIP inside the loadbalancer.
-Normally, the cloud controller manager use ExternalIP to be nodes region-free (or public InternalIP in case of Baremetal).
+**This field is DEPRECATED**. This annotation is deprecated and will be removed in a future release.
+It used to make the CCM use internal IPs instead of public ones for Public only clusters.
 
 ### `service.beta.kubernetes.io/scw-loadbalancer-use-hostname`
 This is the annotation that force the use of the LB hostname instead of the public IP.
@@ -153,7 +153,7 @@ Expected format: `"Key1=Val1,Key2=Val2"`
 
 ### `service.beta.kubernetes.io/scw-loadbalancer-redispatch-attempt-count`
 This is the annotation to activate redispatch on another backend server in case of failure
-The default value is 0, which disable the redispatch.
+The default value is 0, which disable the redispatch. Only a value of 0 or 1 are allowed.
 
 ### `service.beta.kubernetes.io/scw-loadbalancer-max-retries`
 This is the annotation to configure the number of retry on connection failure