chore(camel-test-infra-milvus): upgrade milvus.container.ppc64le to v2.6.5

[github-actions]

This PR updates the milvus.container.ppc64le container image to version v2.6.5.

Update Details

• Property: milvus.container.ppc64le
• Image: icr.io/ppc64le-oss/milvus-ppc64le
• File: /home/runner/work/camel/camel/test-infra/camel-test-infra-milvus/src/main/resources/org/apache/camel/test/infra/milvus/services/container.properties
• Old version: v2.4.11
• New version: v2.6.5

Verification

Please verify:

• Container image version is compatible with existing tests
• No breaking changes in the updated version
• Tests pass with the new version

Run the following to rebuild the test infra:

mvn clean verify -pl camel-test-infra-milvus

Then test the impacted components.

---

This PR was automatically created by the Container Version Upgrade workflow.

[oscerd]

A big jump

[apupier]

known to be not working https://issues.apache.org/jira/browse/CAMEL-23242

[orpiske]

🤖 ✅ Successfully tested with component(s): components/camel-ai/camel-milvus

[orpiske]

Obs: tested on x86, but this is for ppc64le, so moving back the review to comment.

[gnodet]

Claude Code review on behalf of @gnodet

Review: Upgrade Milvus ppc64le container v2.4.11 → v2.6.5

The diff is minimal — upgrades the ppc64le-specific Milvus container image from icr.io/ppc64le-oss/milvus-ppc64le:v2.4.11 to v2.6.5.

Concerns

@apupier has already noted this is known to be not working (referencing CAMEL-23242), and @orpiske has also requested changes. This PR appears to have been stale since April 2026.

The main x86 container is already at v2.6.13, so bringing ppc64le up to v2.6.5 makes sense in principle — but not if it's known to be broken.

Questions: Is CAMEL-23242 still relevant? Has the ppc64le image been fixed upstream since this PR was opened?