Deployment with Docker Images fails to Issue Credentials for Consumer and Provider

[gsergiu]

We are working to deploy the MVD on K8S using the MVD Docker Images and we encountered several issues:

1. We cannot access the latest Docker Images from repository: ghcr.io/eclipse-dataspace-hub/minimumviabledataspace/ we had to switch back to ghcr.io/eclipse-edc/minimumviabledataspace/ repository
2. We managed to configure our custom deployment (main kustomization.yaml), but the identity hub seeding jobs are failing to issue credentials for provider and consumer. The Credentials are created and reach the Approved Status, but the delivery fails

Here the logs from the seeding job:
`================================================
Step 1: Create Consumer Holder in IssuerService

✓ Consumer holder created in IssuerService
Debug Response body:

Step 2: Create Consumer Participant Context in IdentityHub

✓ Consumer participant context created
Debug Response body: {"apiKey":"Y29...=.ng0d.../Shf23..==","clientId":"did:web:identityhub.consumer-test.svc.cluster.local%3A7083:consumer","clientSecret":"..."}

Step 3: Requesting credential issuance

✓ Consumer participant context created
Debug Response body: {"apiKey":"Y29...=.ng0d../VSD../Shf23..==","clientId":"did:web:identityhub.consumer-test.svc.cluster.local%3A7083:consumer","clientSecret":"..."}

Step 4: Wait for credentials to be issued

Debug Response body: {"issuerDid":"did:web:issuerservice.dsp-issuer-test.svc.cluster.local%3A10016:issuer","holderPid":"credential-request-1","issuerPid":null,"status":"CREATED","typesAndFormats":[{"id":"membership-credential-def","credentialType":"MembershipCredential","format":"VC2_0_JOSE"},{"id":"manufacturer-credential-def","credentialType":"ManufacturerCredential","format":"VC2_0_JOSE"}]}
Credential status: CREATED
Debug Response body: {"issuerDid":"did:web:issuerservice.dsp-issuer-test.svc.cluster.local%3A10016:issuer","holderPid":"credential-request-1","issuerPid":"","status":"REQUESTED","typesAndFormats":[{"id":"membership-credential-def","credentialType":"MembershipCredential","format":"VC2_0_JOSE"},{"id":"manufacturer-credential-def","credentialType":"ManufacturerCredential","format":"VC2_0_JOSE"}]}
Credential status: REQUESTED

IH Logs:
�[0;34mDEBUG 2026-07-10T01:04:29.834627644 [CredentialRequestManagerImpl] HolderCredentialRequest credential-request-1 is now in state CREATED�[0m
�[0;34mDEBUG 2026-07-10T01:04:30.514907173 Processing 'CREATED' request 'credential-request-1'�[0m
�[0;34mDEBUG 2026-07-10T01:04:30.576869276 [CredentialRequestManagerImpl] HolderCredentialRequest credential-request-1 is now in state REQUESTING�[0m
�[0;34mDEBUG 2026-07-10T01:04:30.688179272 [CredentialRequestManagerImpl] HolderCredentialRequest credential-request-1 is now in state REQUESTED�[0m
�[0;34mDEBUG 2026-07-10T01:05:17.700216981 [CredentialWatchdog] checking 0 credentials�[0m
�[0;34mDEBUG 2026-07-10T01:06:17.698966819 [CredentialWatchdog] checking 0 credentials�[0m
�[0;34mDEBUG 2026-07-10T01:07:17.69947485 [CredentialWatchdog] checking 0 credentials�[0m
�[0;34mDEBUG 2026-07-10T01:08:17.69883246 [CredentialWatchdog] checking 0 credentials�[0m
�[0;34mDEBUG 2026-07-10T01:09:17.700170403 [CredentialWatchdog] checking 0 credentials�[0m
�[0;34mDEBUG 2026-07-10T01:10:12.817767188 [CredentialRequestManagerImpl] HolderCredentialRequest credential-request-1 is now in state CREATED�[0m
�[0;34mDEBUG 2026-07-10T01:10:13.412030431 Processing 'CREATED' request 'credential-request-1'�[0m
�[0;34mDEBUG 2026-07-10T01:10:13.437302349 [CredentialRequestManagerImpl] HolderCredentialRequest credential-request-1 is now in state REQUESTING�[0m
�[0;34mDEBUG 2026-07-10T01:10:13.505843537 [CredentialRequestManagerImpl] HolderCredentialRequest credential-request-1 is now in state REQUESTED�[0m

ISSUER Logs:
�[0;34mDEBUG 2026-07-10T01:06:18.422420335 IssuanceProcess: ID eecf7fca-1f55-4353-aa94-a395b05bbdfb. Attempt #6 failed to Deliver Credentials. Cause: �[0m
�[0;34mDEBUG 2026-07-10T01:06:18.432647054 [IssuanceProcessManagerImpl] IssuanceProcess eecf7fca-1f55-4353-aa94-a395b05bbdfb is now in state APPROVED�[0m
�[0;34mDEBUG 2026-07-10T01:06:18.440961971 Entity 03abf65b-6b3d-4bd4-8cd2-a3d71114e7c4 IssuanceProcess retry #7 will not be attempted before 714 ms.�[0m
�[0;34mDEBUG 2026-07-10T01:06:18.443898236 Entity 28d9c5ea-c511-4063-a61f-0265e079d68a IssuanceProcess retry #6 will not be attempted before 21940 ms.�[0m
�[0;34mDEBUG 2026-07-10T01:06:18.446009573 Entity eecf7fca-1f55-4353-aa94-a395b05bbdfb IssuanceProcess retry #6 will not be attempted before 63977 ms.�[0m
�[0;34mDEBUG 2026-07-10T01:06:19.452821749 Entity 03abf65b-6b3d-4bd4-8cd2-a3d71114e7c4 IssuanceProcess retry #7 of 7.�[0m
�[0;31mSEVERE 2026-07-10T01:06:19.760299035 IssuanceProcess: ID 03abf65b-6b3d-4bd4-8cd2-a3d71114e7c4. Attempt #8 failed to Deliver Credentials. Retry limit exceeded. Cause: �[0m
�[0;33mWARNING 2026-07-10T01:06:19.760468661 �[0m
�[0;34mDEBUG 2026-07-10T01:06:19.766025076 [IssuanceProcessManagerImpl] IssuanceProcess 03abf65b-6b3d-4bd4-8cd2-a3d71114e7c4 is now in state ERRORED. errorDetail: �[0m

!!! Not sure if these errors play a role
Jul 10, 2026 12:57:14 AM org.glassfish.jersey.internal.Errors logErrors
WARNING: The following warnings have been detected: WARNING: The (sub)resource method requestCredential in org.eclipse.edc.identityhub.protocols.dcp.issuer.api.v1alpha.credentialrequest.CredentialRequestApiController contains empty path annotation.
WARNING: The (sub)resource method getIssuerMetadata in org.eclipse.edc.identityhub.protocols.dcp.issuer.api.v1alpha.issuermetadata.IssuerMetadataApiController contains empty path annotation.

....`

[gsergiu]

I'm trying to investigate the issue and I discovered that the Participant cannot be retrieved by IDs.
I'm using the bruno requests to make run the following HTTP requests
The Query Participants (POST Method {{ISSUER_ADMIN_URL}}/api/admin/v1alpha/participants/{{ISSUER_CONTEXT_ID}}/holders/query) Returns the entry:
{ "id": null, "createdAt": 1783805111631, "participantContextId": "issuer", "holderId": "did:web:identityhub.consumer-test.svc.cluster.local%3A7083:consumer", "did": "did:web:identityhub.consumer-test.svc.cluster.local%3A7083:consumer", "holderName": "MVD Consumer Participant", "anonymous": false, "properties": {}, "lastModifiedAt": 1783805111631 }

However the retireval (GET {{ISSUER_ADMIN_URL}}/api/admin/v1alpha/participants/{{ISSUER_CONTEXT_ID}}/holders/:participantId)
With participantID: "did:web:identityhub.consumer-test.svc.cluster.local%3A7083:consumer"

Returns NOT Found:
{
"message": "Object of type Holder with ID=did:web:identityhub.consumer-test.svc.cluster.local:7083:consumer was not found",
"type": "ObjectNotFound",
"path": null,
"invalidValue": null
}
Please note that in the response the ": " before the port gets unescaped

[gsergiu]

I found two issues in our configurations which were fixed and now I was able to correctly deploy the MVD with the Dashboard.
However, we would have some suggestions for improving/templating the configurations so that we can have multiple deployments in the same k8s cluster (i.e. for staging).
Probably the best way would be co create a separate ticket