Deploy-btq: Deploying the micorservices
We're going to explain a few things about the deployment with Sealights and about the job
Before everything, deploying the microservices is done in the Deploy-btq job, we'll explain why we call it that later on, this is the only job that the groovy pipeline is not in the repository.
The Deploy-btq pulls the images from the ecr and runs helm upgrade to replace the Kubernetes microservices pods and/or change some deployment parameters.
When running the update-btq you should start seeing in the pods being replaced via kubectl get pods (if pods need to be replaced).
You should notice the adservice and cartservice have been updated, that is because they're using CD agent that scans the code on deployment (right before running the service).
Last updated