[k8s] Add microservice.yaml

[mincong-h]

This is the teaching material for

• [L3] Update Lab Session 3 mincong-classroom/containers#8

[vertesia-code-review]

Changes

This pull request introduces a microservice.yaml file to the esigelec/lab/ directory. This file defines the deployment configurations for several microservices within a Kubernetes environment. These include a Config Server, API Gateway, Customer Service, Visits Service, Vets Service and a Tracing Server (Zipkin). Each service is defined with a Kubernetes Deployment and Service, specifying details such as the Docker image to use, resource requests and limits, and port mappings. The API Gateway also includes a ConfigMap to configure routes, predicates and filters such as CircuitBreaker and Retry.

Here is a breakdown of the changes:

Path

Description

esigelec/lab/microservice.yaml

This file defines Kubernetes deployments and services for several microservices: config-server, api-gateway, customers-service, visits-service, vets-service, and tracing-server (Zipkin). It includes configurations for resource allocation, port mappings, and environment variables.Key aspects:* Config Server: Uses springcommunity/spring-petclinic-config-server and disables discovery.* API Gateway: Uses a custom image (mincongclassroom/spring-petclinic-api-gateway:bcf6d05), configures routes and filters (CircuitBreaker, Retry) and mounts a ConfigMap.* Other Services: Use standard springcommunity/spring-petclinic-* images and disable discovery.

Purpose

The motivation of this pull request is to provide teaching material, specifically a microservice.yaml file. This file likely serves as an example configuration or deployment manifest for a microservice-based application, intended to be used in an educational context.

The context is a learning exercise. The microservice.yaml file is intended to be used in conjunction with a related pull request in another repository (mincong-classroom/containers/pull/8). The PR aims to support some teaching or demonstration of containers or microservices concepts.

Related issues: N/A

Code Review

You can start a code review by adding a comment: "Vertesia, please review".

Note that the motivation and context are rated as clear (4/5). The agent has a good understanding of the purpose of the pull request.