docs: Create step-by-step GCloud deployment configuration

Author: MirkoZETA

README.md

@@ -72,4 +72,79 @@ docker run -p 8080:8080 fns-api
 To stop:
 ```bash
 docker stop fns-api
-```
+```
+
+## Docs: GCloud Deployment Configuration
+
+For detailed step-by-step instructions on configuring Google Cloud (GCloud) aspects such as Kubernetes Cluster creation, Artifact Registry, Service Account creation, and IAM policy binding, please refer to the following video tutorial:
+
+[GCloud Configuration Video Tutorial](https://www.youtube.com/watch?v=KQUKDiBz3IA)
+
+This video will guide you through the necessary configurations in the Google Cloud Console to prepare your project for Kubernetes deployments using GitHub Actions.
+
+**Key Reminders from the Video & for Successful Deployment:**
+
+*   **Keep Track of Docker Image Name, Project ID, and Kubernetes Cluster Name:**  Note these down during the video configuration, as you will need them in subsequent steps and for your GitHub Actions workflow.
+*   **Service Account Email:** Ensure you create a Service Account as shown in the video and securely download and store the JSON key file. You'll also need to note the Service Account's email address.
+
+**Post-Configuration Steps (using `gcloud` and `kubectl`):**
+
+1.  **Create a Kubernetes Cluster in GCloud:**
+
+    *   Navigate to the Kubernetes Engine section in your Google Cloud Console.
+    *   Click **Create Cluster**.
+    *   Choose a cluster name (e.g., `flex-net-sim-cluster`). **Remember this name.**
+    *   Select a region for your cluster (e.g., `us-central1`).
+    *   For the purpose of this guide, you can use the default settings for node pools, networking, and other configurations, or adjust them based on your specific needs.
+    *   Click **Create** to create the cluster. It will take a few minutes for the cluster to be provisioned.
+
+2.  **Set IAM Policy Binding (using `gcloud`):**
+
+    Replace `<YOUR-GOOGLE-PROJECT-ID>` and `<SERVICE_ACCOUNT_EMAIL>` with your actual Google Cloud Project ID and the Service Account Email you noted down.
+
+    ```bash
+    gcloud projects add-iam-policy-binding <YOUR-GOOGLE-PROJECT-ID> --member="serviceAccount:<SERVICE_ACCOUNT_EMAIL>" --role="roles/container.admin"
+    ```
+
+3.  **Get Kubernetes Cluster Credentials (using `gcloud`):**
+
+    Replace `<CLUSTER-NAME>` and `<YOUR-GOOGLE-PROJECT-ID>` with your Kubernetes Cluster Name and Google Cloud Project ID. Ensure the region is set to `us-central1`.
+
+    ```bash
+    gcloud container clusters get-credentials <CLUSTER-NAME> --region us-central1 --project <YOUR-GOOGLE-PROJECT-ID>
+    ```
+
+    The command will fetch the cluster credentials and configure `kubectl` to use them. You should see output similar to:
+
+    ```
+    Fetching cluster endpoint and auth data.
+    kubeconfig entry generated for <CLUSTER-NAME>.
+    ```
+
+4.  **Verify `kubectl` Configuration and Service Deployment (using `kubectl`):**
+
+    After the command is successful, verify your `kubectl` configuration and check for the `fns-api-service`:
+
+    ```bash
+    kubectl get service fns-api-service
+    ```
+
+    If the service is correctly deployed (after your GitHub Actions workflow runs), it should display information about your service, including the `EXTERNAL-IP`.
+
+    You should see output similar to this (the `EXTERNAL-IP` will likely be different):
+
+    ```
+    NAME              TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)        AGE
+    fns-api-service   LoadBalancer   10.3.xxx.xxx    34.56.1.247     80:8080/TCP    20h
+    kubernetes        ClusterIP      10.3.xxx.xxx     <none>          443/TCP        21h
+    ```
+
+5.  **Test the Deployed API (using `curl`):**
+
+    Use the `curl` command with the `EXTERNAL-IP` you obtained from the previous step to test your deployed API. Replace `<YOUR-EXTERNAL-IP>` with the actual `EXTERNAL-IP`.
+
+    ```bash
+    curl -X POST -H "Content-Type: application/json" -d '{"algorithm": "FirstFit", "networkType": 1, "bitrate": "bitrate"}' http://<YOUR-EXTERNAL-IP>/run_simulation
+    ```
+
+**Remember**: These GCloud configurations, along with the repository's `gke-cd.yml` GitHub Actions workflow and correctly configured GitHub secrets, are essential for successful automated deployment of your FlexNetSim-API application to Google Cloud Kubernetes Engine.