Validate Jaeger demo configurations in CI workflow (#7464)

## Which problem is this PR solving?
- Part of #7115 
- We needed validation workflow of jaeger demo configurations , Instead
of creating workflow from scratch we could reuse already created
workflow with minor changes present in
.github/workflows/ci-docker-hotrod.yml

## Description of the changes
- Update the build hotrod script to use oci example's deployment script
.

## How was this change tested?
- 

## Checklist
- [ ] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [ ] I have signed all commits
- [ ] I have added unit tests for the new functionality
- [ ] I have run lint and test steps successfully
  - for `jaeger`: `make lint test`
  - for `jaeger-ui`: `npm run lint` and `npm run test`

---------

Signed-off-by: chahat sagar <109112505+chahatsagarmain@users.noreply.github.com>

Author: chahatsagarmain

.github/workflows/ci-deploy-demo.yml

@@ -33,11 +33,10 @@ jobs:
 
     - name: Deploy using appropriate script
       run: |
-        cd ./examples/oci
         if [ "${{ github.event_name }}" = "schedule" ]; then
           echo "🕒 Scheduled run - using deploy-all.sh (upgrade mode)"
-          bash ./deploy-all.sh
+          bash ./examples/oci/deploy-all.sh
         else
           echo "🔄 Manual run - using deploy-all.sh with clean mode (uninstall/install)"
-          bash ./deploy-all.sh clean
+          bash ./examples/oci/deploy-all.sh clean
         fi         

.github/workflows/ci-docker-hotrod.yml

@@ -24,6 +24,9 @@ jobs:
       matrix:
         runtime: [docker, k8s]
         jaeger-version: [v1, v2]
+        exclude:
+          - runtime: k8s
+            jaeger-version: v1
 
     steps:
     - uses: step-security/harden-runner@ec9f2d5744a09debf3a187a3f4f675c53b671911 # v2.13.0
@@ -64,10 +67,6 @@ jobs:
       with:
         version: 'latest'
 
-    - name: Install Kustomize
-      if: matrix.runtime == 'k8s'
-      uses: imranismail/setup-kustomize@2ba527d4d055ab63514ba50a99456fc35684947f # v2
-
     - name: Create k8s Kind Cluster
       if: matrix.runtime == 'k8s'
       uses: helm/kind-action@a1b0e391336a6ee6713a0583f8c6240d70863de3 # v1

examples/hotrod/kubernetes/README.md

@@ -1,17 +1,69 @@
 # Hot R.O.D. - Rides on Demand on Kubernetes
 
-Example k8s manifests for deploying the [hotrod app](..) to your k8s environment of choice. e.g. minikube, k3s, EKS, GKE
+Example deployment for the [hotrod app](..) using Helm charts in your Kubernetes environment (Kind, minikube, k3s, EKS, GKE).
+
+## Prerequisites
+
+- Kubernetes cluster
+- Helm 3.x installed
+- kubectl configured
 
 ## Usage
 
+### Deploy with Default Configuration
+
 ```bash
-kustomize build . | kubectl apply -f -
-kubectl port-forward -n example-hotrod service/example-hotrod 8080:frontend
-# In another terminal
-kubectl port-forward -n example-hotrod service/jaeger 16686:frontend
+cd examples/oci
+./deploy-all.sh clean
+```
+
+### Deploy with Local Images (for development)
 
-# To cleanup
-kustomize build . | kubectl delete -f -
+```bash
+# For Jaeger v2 with local images
+cd examples/oci
+./deploy-all.sh local <image-tag>
 ```
 
-Access Jaeger UI at <http://localhost:16686> and HotROD app at <http://localhost:8080>
+### Deploy Modes
+
+- **`upgrade`** (default): Upgrade existing deployment or install if not present
+- **`local`**: Deploy using local registry images (localhost:5000)
+- **`clean`**: Clean install (removes existing deployment first)
+
+### Access Applications
+
+After deployment completes, use port-forwarding:
+
+```bash
+# Jaeger UI
+kubectl port-forward svc/jaeger-query 16686:16686
+
+# HotROD application
+kubectl port-forward svc/jaeger-hotrod 8080:80
+
+# Prometheus (optional)
+kubectl port-forward svc/prometheus 9090:9090
+
+# Grafana (optional)
+kubectl port-forward svc/prometheus-grafana 9091:80
+```
+
+Then access:
+- 🔍 **Jaeger UI**: http://localhost:16686/jaeger
+- 🚕 **HotROD App**: http://localhost:8080/hotrod
+- 📈 **Prometheus**: http://localhost:9090
+- 📊 **Grafana**: http://localhost:9091
+
+## Configuration
+
+The deployment uses:
+- **Helm charts** from [jaeger-helm-charts](https://github.com/jaegertracing/helm-charts)
+- **Prometheus** for metrics collection
+- **Load generator** for creating sample traces
+
+Configuration files:
+- `jaeger-values.yaml` - Jaeger Helm chart values
+- `config.yaml` - Jaeger configuration
+- `ui-config.json` - Jaeger UI configuration
+- `monitoring-values.yaml` - Prometheus configuration