docs(warn): include warning for production ready setup

Author: Frederic Spiers

README.md

@@ -37,6 +37,11 @@ The project can be deployed on Kubernetes-like infrastructure (k0s, k3s, Talos,
 - If you already have a Kubernetes cluster, please follow the [below documentation](#helm-deployment). 
 - If you do not have a dedicated Kubernetes cluster, you can deploy GGBridge with a `k3d` cluster on a single VM. Please follow the [k3d installation documentation](./docs/k3d-install.md)
 
+> [!WARNING]  
+> The `k3d` installation method is not recommended for production due to single point of failure and lack of high availability.
+>
+> **For production setup**, we recommend deploying on a multi-node Kubernetes cluster across multiple AZs with proper redundancy and monitoring.
+
 ### Helm deployment
 
 To deploy the ggbridge client in your Kubernetes cluster using Helm, follow these steps:

docs/k3d-install.md

@@ -2,6 +2,11 @@
 
 This guide will help you deploy and manage local Kubernetes clusters using k3d for GGBridge deployment.
 
+> [!WARNING]  
+> This setup is not recommended for production due to single point of failure and lack of high availability.
+>
+> **For production setup**, we recommend deploying on a multi-node Kubernetes cluster across multiple AZs with proper redundancy and monitoring.
+
 ## 📋 Prerequisites
 For this installation method, you will need a single server (VM, bare metal...) and install following components: