docs(readme): improve documentation to mention replicacount should be 3

Author: Frederic Spiers

README.md

@@ -39,10 +39,23 @@ The project offers two deployment methods:
 
 ### Docker deployment
 
+> [!WARNING]  
+> Please consider that [Docker deployment](#docker-deployment) mode is intended for testing purposes. We highly recommend using [Helm deployment](#helm-deployment) mode.
+
 Deploy the ggbridge client via Docker Compose by performing the following actions:
 
 - Create `docker-compose.yml` file
 
+> [!IMPORTANT]  
+> GGBridge is designed by default to work as HA, so it needs `3` client deployments to work properly. Ensure `replicas: 3` in your `docker-compose.yml` file.
+>
+> ```yaml
+> services:
+>   client:
+>     deploy:
+>       replicas: 3
+> ```
+
 ```yaml
 name: ggbridge
 
@@ -53,7 +66,6 @@ services:
       SERVER_ADDRESS: <my-subdomain>.ggbridge.gitguardian.com
       TLS_ENABLED: 'true'
     deploy:
-      mode: replicated
       replicas: 3
     volumes:
       - ./tls/ca.crt:/etc/ggbridge/tls/ca.crt:ro
@@ -102,11 +114,18 @@ kubectl -n ggbridge create secret generic ggbridge-client-crt \
 Edit your Helm values file to point to your bridge server and the secret created above  
 (see the [Helm chart values documentation](./helm/ggbridge) for all available configuration options):
 
+> [!IMPORTANT]  
+> GGBridge is designed by default to work as HA, so it needs `3` client deployments to work properly. Leave it blank or ensure `deploymentCount: 3` in your `values.yaml` file.
+>
+> ```yaml
+> deploymentCount: 3
+> ```
+
 ```yaml
 hostname: <my-subdomain>.ggbridge.gitguardian.com
 
 image:
-  tag: latest-shell
+  tag: latest
 
 tls:
   enabled: true
@@ -117,6 +136,15 @@ tls:
     key: tls.key
 ```
 
+> [!TIP]
+> If you need to debug the deployment, you can use the image `latest-shell` instead of `latest`. This image comes with embedded tooling for debugging purposes. :
+>
+> ```yaml
+> image:
+>   tag: latest-shell
+> ```
+
+
 For **OpenShift** deployment, use the following values:
 
 ```yaml