Management API endpoints (8081) non-responsive in MVD 0.17.0 KinD deployment

[minaattr]

We are deploying Eclipse EDC Minimum Viable Dataspace (MVD) version 0.17.0 on Kubernetes (KinD) for research purposes. After multiple deployment attempts, we consistently encounter non-responsive management API endpoints.

Setup:

• Eclipse EDC MVD version: 0.17.0 (stable tag)
• Deployment: KinD cluster (Kubernetes v1.35.0)
• Images: Pre-built from ghcr.io/eclipse-edc/
• All pods healthy (1/1 Running, seed jobs Completed)
• Port-forwards active

Issue:
Management API endpoints return no response or 404 errors:

GET https://localhost:8081/api/mgmt/assets → 404 Not Found
GET https://localhost:8081/api/mgmt/ → 404 Not Found
GET https://localhost:8081/api/v3/assets → 404 Not Found

Controlplane logs show management API extensions started successfully:

Started Management API: Asset
Started Management API: Catalog
Started Management API: Contract Agreement
... (all management API extensions loaded)

However, HTTP requests to these endpoints fail. Testing from inside the pod yields the same 404 responses, ruling out port-forward issues.

Environment:

• Ubuntu 24.04
• KinD v0.x
• kubectl version: 1.x
• Docker: latest

Steps to reproduce:

1. Fresh KinD cluster: kind create cluster --name mvd
2. Install Gateway API CRDs: kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.0.0/standard-install.yaml
3. Clone and deploy: git clone <repo>; cd MinimumViableDataspace; git checkout 0.17.0; kubectl apply -k k8s/
4. Wait for pods to be Ready
5. Port-forward: kubectl port-forward -n provider svc/controlplane 8080:8081
6. Test: curl -k https://localhost:8080/api/mgmt/assets

Expected: Asset list or empty array []
Actual: 404 Not Found or connection reset

Question:

Is this a known issue in 0.17.0? Are there workarounds or a recommended version that resolves this?

[perher]

Hey @minaattr, I'm just an end-user so will just give some high level tips:

• I think main reason that curl is not working is because of wrong hostname. Containers are exposed behind HTTPRoute objects and they are bound to specific hostnames like cp.consumer.localhost, example, so your curl example should then use curl http://cp.consumer.localhost:8080/... (also note http).
• In general try to use the provided Bruno collection as they use the correct hostnames and path. Note though that Bruno collection assumes port 80 instead of 8080, so you would either have to change hostnames or your kubectl port-forward to use matching port number.
• Also note that MVD and EDC Connector are under heavy development in preparation for 1.0 release. Using the 0.17 tag that is now quite old is not guaranteed to work. If using this tag make sure that you build the images from source otherwise it would use the latest version of Connector images which might not be compatible with the config and Bruno collection provided by this tag.