-
Notifications
You must be signed in to change notification settings - Fork 324
Open
Description
Thanks for the wonderful microservices code, I'm just opening this issue about installation steps which i followed inside my EKS cluster.
- From the master branch root directory https://github.com/piomin/sample-spring-microservices-kubernetes started the maven build using skip test case with value of true and build went successful.
- cd k8s applied all the files without ingress, i missed ingress due to verify the all the services locally using nondepot before going to create ingress.
- cd department-service, mvn build, docker build, pushed image into private repo, updated image name in deployment file applied all the files pod is up and running.
- cd employee-service,docker build, pushed image into private repo, updated image name in deployment file applied all the files pod is up and running.
- cd gateway-service, docker build, pushed image into private repo, updated image name in deployment file applied all the files pod is up and running.
- cd organization-service, docker build, pushed image into private repo, updated image name in deployment file applied all the files pod is up and running.
- cd admin-services, applied all the files but image being using piomin/admin:c45cd99-dirty.
Question - i think no need to perform the maven build here since I'm using loaded image which is coming from (piomin/admin:c45cd99-dirty)
I'm planning to integrate CI pipeline for all the above action which i performed manually, can you please provide the steps what are the module i need build using CI pipeline ? Do i need perform maven build from the main root directory using CI pipeline ?
NAME READY STATUS RESTARTS AGE
admin-5466c5fc46-8w2mx 1/1 Running 0 15s
department-69695856f6-4v4h6 1/1 Running 0 24m
employee-667d6547bb-qr5k5 1/1 Running 0 21m
gateway-6b97b6bff7-7q4n2 1/1 Running 0 19m
mongodb-5fd56f99c4-lfj6c 1/1 Running 0 25m
organization-7d749f7d65-vtzsh 1/1 Running 0 18m
Metadata
Metadata
Assignees
Labels
No labels
