bug: Stack ingestion port-forward uses cluster name instead of Helm release name

[maximilien]

Description

weave stack ingest internal port-forward fails silently because StartMilvusPortForward() uses cluster name instead of Helm release name.

Steps to Reproduce

weave stack up --runtime kind
weave stack ingest Documents data/

Expected Behavior

Should port-forward to: my-rag-stack-weave-stack-milvus

Actual Behavior

Tries to port-forward to: weave-stack-milvus (doesn't exist)

Port-forward fails but error is suppressed, leading to connection issues.

Root Cause

src/pkg/stack/ingest.go:53 - StartMilvusPortForward() was using cluster name:

serviceName := fmt.Sprintf("%s-milvus", clusterInfo.Name) // Wrong!

Same issue as #45 but in the internal port-forward helper function.

Fix

Commit: 291a056

Load stack config and use Helm release name:

stackConfig, err := LoadStackConfig("")
serviceName := fmt.Sprintf("%s-weave-stack-milvus", stackConfig.Name)

Impact

HIGH - Ingestion port-forward fails, but masked by #44 (pipeline bug)

Related

• bug: Stack ingestion reports success but doesn't persist data to Milvus #44 - Pipeline not calling VDB (higher priority bug)
• bug: Port-forward uses cluster name instead of Helm release name #45 - Same issue in port-forward command

Status

✅ FIXED in commit 291a056

[maximilien]

✅ Fixed in commit 87c4dd9 (same fix as #45)

Problem: Stack ingestion port-forward used cluster name instead of Helm release name.

Fix: Updated to use correct Helm release name pattern.

Verification:

weave stack ingest MyCollection data/*.pdf
# Now correctly connects via port-forward

Ready for Client0 testing!