Deploy to Kubernetes

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:

. ~/workshop/petclinic/scripts/set_local.sh

Script execution completed. Modified content saved to /home/splunk/workshop/petclinic/petclinic-local.yaml

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:

kubectl delete -f ~/workshop/petclinic/petclinic-deploy.yaml

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

followed by:

kubectl apply -f ~/workshop/petclinic/petclinic-local.yaml

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

This will cause the containers to be replaced with the local version, you can verify this by checking the containers:

kubectl describe pods api-gateway | grep Image:

The resulting output will show localhost:9999:

  Image:         localhost:9999/spring-petclinic-api-gateway:local

However, as we only patched the deployment before, the new deployment does not have the right annotations for the automatic discovery and configuration, so let’s fix that now by running the patch command again:

Note

There will be no change for the admin-server, config-server and discovery-server as they are already annotated.

kubectl get deployments -l app.kubernetes.io/part-of=spring-petclinic -o name | xargs -I % kubectl patch % -p "{\"spec\": {\"template\":{\"metadata\":{\"annotations\":{\"instrumentation.opentelemetry.io/inject-java\":\"default/splunk-otel-collector\"}}}}}"

deployment.apps/config-server patched (no change)
deployment.apps/admin-server patched (no change)
deployment.apps/customers-service patched
deployment.apps/visits-service patched
deployment.apps/discovery-server patched (no change)
deployment.apps/vets-service patched
deployment.apps/api-gateway patched

Check the api-gateway container (again if you see two api-gateway containers, it’s the old container being terminated so give it a few seconds):

kubectl describe pods api-gateway | grep Image:

The resulting output will show the local api gateway version localhost:9999 and the auto-instrumentation container:

  Image:         ghcr.io/signalfx/splunk-otel-java/splunk-otel-java:v1.32.1
  Image:         localhost:9999/spring-petclinic-api-gateway:local

Now that the Pods have been patched validate they are all running by executing the following command:

kubectl get pods

NAME                                                           READY   STATUS    RESTARTS   AGE
splunk-otel-collector-certmanager-cainjector-cd8459647-d42ls   1/1     Running   0          22h
splunk-otel-collector-certmanager-85cbb786b6-xgjgb             1/1     Running   0          22h
splunk-otel-collector-certmanager-webhook-75d888f9f7-477x4     1/1     Running   0          22h
splunk-otel-collector-agent-nmmkm                              1/1     Running   0          22h
splunk-otel-collector-k8s-cluster-receiver-7f96c94fd9-fv4p8    1/1     Running   0          22h
splunk-otel-collector-operator-6b56bc9d79-r8p7w                2/2     Running   0          22h
petclinic-loadgen-deployment-765b96d4b9-gm8fp                  1/1     Running   0          21h
petclinic-db-774dbbf969-2q6md                                  1/1     Running   0          21h
config-server-5784c9fbb4-9pdc8                                 1/1     Running   0          21h
admin-server-849d877b6-pncr2                                   1/1     Running   0          21h
discovery-server-6d856d978b-7x69f                              1/1     Running   0          21h
visits-service-c7cd56876-grfn7                                 1/1     Running   0          21h
customers-service-6c57cb68fd-hx68n                             1/1     Running   0          21h
vets-service-688fd4cb47-z42t5                                  1/1     Running   0          21h
api-gateway-59f4c7fbd6-prx5f                                   1/1     Running   0          20h