Fix Trivy scan issues in habana-metrics configuration

Signed-off-by: gopal-raj-suresh <gopal.raj.dummugudupu@cloud2labs.com>

Author: gopal-raj-suresh

core/helm-charts/observability/habana-exporter/habana-metrics.yml

@@ -25,7 +25,7 @@ spec:
         operator: "Exists"
         effect: "NoSchedule"
       # Required for network monitoring
-      hostNetwork: true
+      hostNetwork: false
       containers:
       - name: metric-exporter
         image: vault.habana.ai/gaudi-metric-exporter/metric-exporter:1.20.1-97
@@ -34,7 +34,8 @@ spec:
         - name: LD_LIBRARY_PATH
           value: "/usr/lib/habanalabs"
         securityContext:
-          privileged: true
+          privileged: false
+          readOnlyRootFilesystem: true
         volumeMounts:
           - name: pod-resources
             mountPath: /var/lib/kubelet/pod-resources

sample_solutions/RAGChatbot/README.md

@@ -162,6 +162,51 @@ cp api/.env.example api/.env
 
 Then edit `api/.env` to set your `INFERENCE_API_ENDPOINT` and `INFERENCE_API_TOKEN`.
 
+Or manually create `api/.env` with:
+
+```bash
+# Inference API Configuration
+# INFERENCE_API_ENDPOINT: URL to your inference service (without /v1 suffix)
+#
+# **GenAI Gateway**: Provide your GenAI Gateway URL and API key
+#   - URL format: https://genai-gateway.example.com
+#   - To generate the GenAI Gateway API key, use the [generate-vault-secrets.sh] script
+#   - The API key is the litellm_master_key value from the generated vault.yml file
+#
+# **APISIX Gateway**: Provide your APISIX Gateway URL and authentication token
+#   - For APISIX, include the model name in the INFERENCE_API_ENDPOINT path
+#   - Example: https://apisix-gateway.example.com/Llama-3.1-8B-Instruct
+#   - Set EMBEDDING_API_ENDPOINT separately for the embedding model
+#   - Example: https://apisix-gateway.example.com/bge-base-en-v1.5
+#   - To generate the APISIX authentication token, use the [generate-token.sh] script
+#   - The token is generated using Keycloak client credentials
+#
+# INFERENCE_API_TOKEN: Authentication token/API key for the inference service
+INFERENCE_API_ENDPOINT=https://api.example.com
+INFERENCE_API_TOKEN=your-pre-generated-token-here
+
+# Model Configuration
+EMBEDDING_MODEL_NAME=BAAI/bge-base-en-v1.5
+INFERENCE_MODEL_NAME=meta-llama/Llama-3.1-8B-Instruct
+
+# APISIX Gateway Endpoints
+# Uncomment and set these when using APISIX Gateway:
+# IMPORTANT: Use exact APISIX route paths:
+# Example routes: /bge-base-en-v1.5/* and /Llama-3.1-8B-Instruct/*
+# INFERENCE_API_ENDPOINT=https://api.example.com/Llama-3.1-8B-Instruct
+# EMBEDDING_API_ENDPOINT=https://api.example.com/bge-base-en-v1.5
+
+# Local URL Endpoint (only needed for non-public domains)
+# If using a local domain like api.example.com mapped to localhost:
+#   Set this to: api.example.com (domain without https://)
+# If using a public domain, set any placeholder value like: not-needed
+LOCAL_URL_ENDPOINT=not-needed
+
+# SSL Verification Settings
+# Set to false only for dev with self-signed certs
+VERIFY_SSL=true
+```
+
 **Important Configuration Notes:**
 
 - **INFERENCE_API_ENDPOINT**: Your actual inference service URL (replace `https://your-actual-api-endpoint.com`)