more outputs added

Author: hagen-p

content/en/conf24/1-zero-config-k8s/7-log-observer-connect/3-deploy.md

@@ -6,22 +6,99 @@ weight: 3
 
 To see the changes in effect, we need to redeploy the services, First, let's change the location of the images from the external repo to the local one by running the following script:
 
+{{< tabs >}}
+{{% tab title="Change deployment to local containers" %}}
+
 ```bash
 . ~/workshop/petclinic/scripts/set_local.sh
 ```
 
+{{% /tab %}}
+{{% tab title="Output" %}}
+
+```text
+Script execution completed. Modified content saved to /home/splunk/workshop/petclinic/petclinic-local.yaml
+```
+
+{{% /tab %}}
+{{< /tabs >}}
+
 The result is a new file on disk called `petclinic-local.yaml`. Switch to the local versions by using the new version of the deployment YAML. First delete the old containers from the original deployment with:
 
+{{< tabs >}}
+{{% tab title="Deleting remote Petclinic services" %}}
+
 ```bash
 kubectl delete -f ~/workshop/petclinic/petclinic-deploy.yaml
 ```
 
+{{% /tab %}}
+{{% tab title="Output" %}}
+
+```text
+deployment.apps "config-server" deleted
+service "config-server" deleted
+deployment.apps "discovery-server" deleted
+service "discovery-server" deleted
+deployment.apps "api-gateway" deleted
+service "api-gateway" deleted
+service "api-gateway-external" deleted
+deployment.apps "customers-service" deleted
+service "customers-service" deleted
+deployment.apps "vets-service" deleted
+service "vets-service" deleted
+deployment.apps "visits-service" deleted
+service "visits-service" deleted
+deployment.apps "admin-server" deleted
+service "admin-server" deleted
+service "petclinic-db" deleted
+deployment.apps "petclinic-db" deleted
+configmap "petclinic-db-initdb-config" deleted
+deployment.apps "petclinic-loadgen-deployment" deleted
+configmap "scriptfile" deleted
+```
+
+{{% /tab %}}
+{{< /tabs >}}
+
 followed by:
 
+{{< tabs >}}
+{{% tab title="Starting local Petclinic  services" %}}
+
 ```bash
 kubectl apply -f ~/workshop/petclinic/petclinic-local.yaml
 ```
 
+{{% /tab %}}
+{{% tab title="Output" %}}
+
+```text
+deployment.apps/config-server created
+service/config-server created
+deployment.apps/discovery-server created
+service/discovery-server created
+deployment.apps/api-gateway created
+service/api-gateway created
+service/api-gateway-external created
+deployment.apps/customers-service created
+service/customers-service created
+deployment.apps/vets-service created
+service/vets-service created
+deployment.apps/visits-service created
+service/visits-service created
+deployment.apps/admin-server created
+service/admin-server created
+service/petclinic-db created
+deployment.apps/petclinic-db created
+configmap/petclinic-db-initdb-config created
+deployment.apps/petclinic-loadgen-deployment created
+configmap/scriptfile created
+```
+
+{{% /tab %}}
+{{< /tabs >}}
+
 This will cause the containers to be replaced with the local version, you can verify this by checking the containers:
 
 ```bash

content/en/conf24/1-zero-config-k8s/8-rum/1-rebuild-app.md

@@ -44,32 +44,91 @@ cat ~/spring-petclinic-microservices/spring-petclinic-api-gateway/src/main/resou
   RUM_AUTH: '[redacted]',
   RUM_APP_NAME: 'k8s-petclinic-workshop-store',
   RUM_ENVIRONMENT: 'k8s-petclinic-workshop-workshop'
-}
 
+}
 ```
 
 {{% /tab %}}
 {{< /tabs >}}
 
 Change into the `api-gateway` directory and force a new build for just the `api-gateway` service:
 
+{{< tabs >}}
+{{% tab title="Building api-gateway" %}}
+
 ``` bash
 cd  ~/spring-petclinic-microservices/spring-petclinic-api-gateway
 ../mvnw clean install -D skipTests -P buildDocker
 ```
 
-and push the new container to the local registry
+{{% /tab %}}
+{{% tab title=" Output" %}}
+
+```text
+Successfully built 2d409c1eeccc
+Successfully tagged localhost:9999/spring-petclinic-api-gateway:local
+[INFO] Built localhost:9999/spring-petclinic-api-gateway:local
+[INFO] ------------------------------------------------------------------------
+[INFO] BUILD SUCCESS
+[INFO] ------------------------------------------------------------------------
+[INFO] Total time: 26.250 s
+[INFO] Finished at: 2024-05-31T15:51:20Z
+[INFO] ------------------------------------------------------------------------
+```
+
+{{% /tab %}}
+{{< /tabs >}}
+
+and now push the new container to the local registry, the others get skipped:
+
+{{< tabs >}}
+{{% tab title="Updating docker repo with RUM api-gateway" %}}
 
 ``` bash
 . ~/workshop/petclinic/scripts/push_docker.sh
 ```
 
+{{% /tab %}}
+{{% tab title="Verifying only change to api-gateway gets pushed" %}}
+
+```text
+The push refers to repository [localhost:9999/spring-petclinic-api-gateway]
+9a7b16677cf9: Pushed
+f2e09ed98998: Layer already exists
+291752eeb66b: Layer already exists
+ac28fe526c24: Layer already exists
+0a37fe4a02de: Layer already exists
+4b1e7b998de9: Layer already exists
+a2a8ef39e636: Layer already exists
+86cb6a9eb3cd: Layer already exists
+985fdc63de98: Layer already exists
+4ab2850febd7: Layer already exists
+2db7720a8970: Layer already exists
+629ca62fb7c7: Layer already exists
+```
+
+{{% /tab %}}
+{{< /tabs >}}
+
 As soon as the container is pushed into the repository, just restart the `api-gateway` to apply the changes:
 
+{{< tabs >}}
+{{% tab title="Rollout restart api-gateway" %}}
+
 ``` bash
 kubectl rollout restart deployment api-gateway
 ```
 
+{{% /tab %}}
+{{% tab title=" Output" %}}
+
+```text
+deployment.apps/api-gateway restarted
+```
+
+{{% /tab %}}
+{{< /tabs >}}
+
 Validate that the application is running by visiting **http://<IP_ADDRESS>:81** (replace **<IP_ADDRESS>** with the IP address you obtained above). Make sure the application is working correctly by visiting the **All Owners** **(1)** and select an owner, then add a **visit** **(2)**.  We will use this action when checking RUM 
 
 ![pet](../../images/petclinic-pet.png)