Updating for new repository location

Author: jorgemoralespou

projects/frontend/Dockerfile

@@ -1,4 +1,4 @@
-FROM getwarped/warp0-debian10-python37:latest
+FROM getwarped/warp0-debian10-python38:latest
 
 COPY --chown=1001:0 . /opt/app-root/src
 

templates/frontend-v1/deployment.yaml

@@ -21,7 +21,7 @@ spec:
         runAsUser: 1001
       containers:
       - name: blog
-        image: ghcr.io/vmware-tanzu-labs/lab-k8s-fundamentals-frontend:2.0
+        image: ghcr.io/educates/lab-k8s-fundamentals-frontend:2.0
         securityContext:
           allowPrivilegeEscalation: false
           capabilities:

templates/frontend-v2/deployment.yaml

@@ -21,7 +21,7 @@ spec:
         runAsUser: 1001
       containers:
       - name: blog
-        image: ghcr.io/vmware-tanzu-labs/lab-k8s-fundamentals-frontend:2.0
+        image: ghcr.io/educates/lab-k8s-fundamentals-frontend:2.0
         securityContext:
           allowPrivilegeEscalation: false
           capabilities:

templates/frontend-v3/deployment.yaml

@@ -21,7 +21,7 @@ spec:
         runAsUser: 1001
       containers:
       - name: blog
-        image: ghcr.io/vmware-tanzu-labs/lab-k8s-fundamentals-frontend:2.0
+        image: ghcr.io/educates/lab-k8s-fundamentals-frontend:2.0
         securityContext:
           allowPrivilegeEscalation: false
           capabilities:

templates/frontend-v4/deployment.yaml

@@ -21,7 +21,7 @@ spec:
         runAsUser: 1001
       containers:
       - name: blog
-        image: ghcr.io/vmware-tanzu-labs/lab-k8s-fundamentals-frontend:2.0
+        image: ghcr.io/educates/lab-k8s-fundamentals-frontend:2.0
         securityContext:
           allowPrivilegeEscalation: false
           capabilities:

templates/frontend-v5/deployment.yaml

@@ -33,7 +33,7 @@ spec:
                 - blog
       containers:
       - name: blog
-        image: ghcr.io/vmware-tanzu-labs/lab-k8s-fundamentals-frontend:2.0
+        image: ghcr.io/educates/lab-k8s-fundamentals-frontend:2.0
         securityContext:
           allowPrivilegeEscalation: false
           capabilities:

templates/frontend/deployment.yaml

@@ -33,7 +33,7 @@ spec:
                 - blog
       containers:
       - name: blog
-        image: ghcr.io/vmware-tanzu-labs/lab-k8s-fundamentals-frontend:2.0
+        image: ghcr.io/educates/lab-k8s-fundamentals-frontend:2.0
         securityContext:
           allowPrivilegeEscalation: false
           capabilities:

workshop/content/exercises/06-deployment-resource.md

@@ -16,12 +16,12 @@ An alternative is to have `kubectl` create it for you. For a `deployment`, you c
 kubectl create deployment --help
 ```
 
-For the deployment of the front end web application, the container image we want to use is `ghcr.io/vmware-tanzu-labs/lab-k8s-fundamentals-frontend:2.0`.
+For the deployment of the front end web application, the container image we want to use is `ghcr.io/educates/lab-k8s-fundamentals-frontend:2.0`.
 
 To see what `kubectl create deployment` would create for us run:
 
 ```execute
-kubectl create deployment blog --image ghcr.io/vmware-tanzu-labs/lab-k8s-fundamentals-frontend:2.0 --port 8080 --replicas=2 --dry-run=client -o yaml
+kubectl create deployment blog --image ghcr.io/educates/lab-k8s-fundamentals-frontend:2.0 --port 8080 --replicas=2 --dry-run=client -o yaml
 ```
 
 This should yield:
@@ -49,7 +49,7 @@ spec:
       securityContext:
         runAsUser: 1001
       containers:
-      - image: ghcr.io/vmware-tanzu-labs/lab-k8s-fundamentals-frontend:2.0
+      - image: ghcr.io/educates/lab-k8s-fundamentals-frontend:2.0
         name: app-k8s-fundamentals-frontend
         ports:
         - containerPort: 8080

workshop/content/exercises/07-replicasets-and-pods.md

@@ -44,7 +44,7 @@ In this you will see that the `spec` section contains:
           pod-template-hash: 7b747746cc
       spec:
         containers:
-        - image: ghcr.io/vmware-tanzu-labs/lab-k8s-fundamentals-frontend:2.0
+        - image: ghcr.io/educates/lab-k8s-fundamentals-frontend:2.0
           imagePullPolicy: Always
           name: blog
           ports: