Hands-On Microservices with Spring Boot and Spring Cloud

Service and deployment objects for concurrent versions of microservices

To be able to run multiple versions of a microservice concurrently, the deployment objects and their corresponding pods must have different names, for example, product-v1 and product-v2. There must, however, be only one Kubernetes service object per microservice. All traffic to a specific microservice always goes through one and the same service object, irrespective of what version of the pod the request will be routed to in the end. This is achieved using Kustomize by splitting up deployment objects and service objects into different folders.

To give deployment objects and their pods version-dependent names, the kustomization.yml file can use the nameSuffix directive ...