@@ -218,9 +218,9 @@ All commands are executed from the **repository's root folder** unless stated ot
218218> Since this is not a production deployment, all applications are deployed _ in the same cluster_ and in the same
219219> namespace, plainly for the sake of simplicity.
220220
221- This builds the runtime images and creates the following docker images: ` ghcr.io/eclipse-edc/mvd /controlplane:latest ` ,
222- ` ghcr.io/eclipse-edc/mvd /dataplane:latest ` , ` ghcr.io/eclipse-edc/mvd /issuerservice:latest ` and
223- ` ghcr.io/eclipse-edc/mvd /identity-hub:latest ` in the local docker image cache.
221+ This builds the runtime images and creates the following docker images: ` ghcr.io/eclipse-edc/minimumviabledataspace /controlplane:latest ` ,
222+ ` ghcr.io/eclipse-edc/minimumviabledataspace /dataplane:latest ` , ` ghcr.io/eclipse-edc/minimumviabledataspace /issuerservice:latest ` and
223+ ` ghcr.io/eclipse-edc/minimumviabledataspace /identity-hub:latest ` in the local docker image cache.
224224
225225PostgreSQL and Hashicorp Vault obviously require additional configuration, which is handled by the Kubernetes manifests
226226via batch jobs.
@@ -257,10 +257,10 @@ grep -rlZ "imagePullPolicy: Always" k8s | xargs sed -i "s/imagePullPolicy: Alway
257257
258258# Load docker images into KinD
259259kind load docker-image \
260- ghcr.io/eclipse-edc/mvd /controlplane:latest \
261- ghcr.io/eclipse-edc/mvd /dataplane:latest \
262- ghcr.io/eclipse-edc/mvd /identity-hub:latest \
263- ghcr.io/eclipse-edc/mvd /issuerservice:latest -n mvd
260+ ghcr.io/eclipse-edc/minimumviabledataspace /controlplane:latest \
261+ ghcr.io/eclipse-edc/minimumviabledataspace /dataplane:latest \
262+ ghcr.io/eclipse-edc/minimumviabledataspace /identity-hub:latest \
263+ ghcr.io/eclipse-edc/minimumviabledataspace /issuerservice:latest -n mvd
264264```
265265
266266#### 4.2.3 Deploy MVD components
0 commit comments