Align helm charts values with compose yaml

[chensuyue]

Description

Align helm charts values with compose yaml, fix the release test issues.

Issues

ChatQnA, xeon, cpu-qdrant-values.yaml
https://github.com/opea-project/GenAIExamples/actions/runs/17062358312/job/48463719735#step:6:89

CodeTrans, gaudi, gaudi-values.yaml
https://github.com/opea-project/GenAIExamples/actions/runs/17060819842/job/48367158782#step:6:516

Type of change

List the type of change like below. Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds new functionality)
• Breaking change (fix or feature that would break existing design and interface)

Dependencies

List the newly introduced 3rd party dependency if exists.

Tests

Describe the tests that you ran to verify your changes.

[eero-t]

Otherwise looks fine, but README update is incomplete.

[chensuyue]

@eero-t the qdrant test still failed, do you have any suggestion for this issue? https://github.com/opea-project/GenAIInfra/actions/runs/17091504542/job/48466101925

[eero-t]

@eero-t the qdrant test still failed, do you have any suggestion for this issue? https://github.com/opea-project/GenAIInfra/actions/runs/17091504542/job/48466101925

@chensuyue Looking at the CI test logs...

"data-prep redis-values" test seems to be failing due to data-prep using invalid URL (/) to query TEI:

[pod/data-prep20142932-55884975f5-6p4l5/data-prep] requests.exceptions.ConnectionError: HTTPConnectionPool(host='data-prep20142932-tei', port=80): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7ff864961dd0>: Failed to establish a new connection: [Errno 111] Connection refused'))

And "data-prep qdrant-values" fails to data-prep-qdrant using PVC that tries to bind a K8s Volume object that does not exist:

#kubectl logs data-prep20142908-df4d5f986-74gbt -n infra-data-prep-d5de51d3
[pod/data-prep20142908-df4d5f986-74gbt/wait-for-db] ERROR: data-prep20142908-qdrant:6333 is NOT reachable in 61 seconds!
Error from server (BadRequest): container "data-prep" in pod "data-prep20142908-df4d5f986-74gbt" is waiting to start: PodInitializing
...
 Volumes:
  qdrant-storage:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  qdrant-storage-data-prep20142908-qdrant-0
    ReadOnly:   false
...
  Warning  FailedScheduling  4m49s (x2 over 10m)  default-scheduler  0/3 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.

=> Please logs status of PVC & PV objects in that namespace, and what PV that PVC tries to use.

I guess there should be a NFS volume: https://kubernetes.io/docs/concepts/storage/volumes/#nfs ?

[eero-t]

Approved.

[poussa]

@chensuyue can you fix the CI errors before we merge?

[chensuyue]

@chensuyue can you fix the CI errors before we merge?

Fixed.

[chensuyue]

=> Please logs status of PVC & PV objects in that namespace, and what PV that PVC tries to use.

I guess there should be a NFS volume: https://kubernetes.io/docs/concepts/storage/volumes/#nfs ?

Thanks for the analysis, I setup a PV for the test, and it pass.