The specific implementation of microservice K8S devops?

problem description

recently, I have been looking at things related to automated operation and maintenance devops, and some problems are not quite clear for the time being. Hope God to inform
premise: springcloud deployment, there are probably registry, configuration center, message center, order center, user center, activity center. 2 instances per center

1. If you use K8S and jenkins, to look at the materials on the Internet, it seems that you can only do it, and you can only build one center at a time. In other words, I have to build 6 new tasks on jenkins, and each time I launch it, it is my turn to build it. It seems normal to think about it. If I only change the code of a certain center, all I have to do is build the code of that center. Do big companies do this?

2. In fact, I don"t quite understand how to ask this question, but it seems that the specific implementation of devops can not be found on the Internet, it is all conceptual things. My understanding of devops is that it only needs to be built, and the online environment is all done. But it doesn"t seem to be possible. Are there any great gods who have this kind of experience? give me some guidance.


can do it.

you can not order at all.

if you are still using Jenkins. In fact, the essence is that Jenkins gives you a bunch of orders and one-stop service.

from pull substitution code to build image, then deploy to K8s to complete launch.

how do you do that in Jenkins? The answer is JenkinsFile or manually maintain the deployment script for each project.

it's too troublesome to click six times. I guess you don't know much about several trigger construction methods of Jenkins.

Jenkins task trigger can detect source code changes regularly / can be triggered by Gitlab or something sent Webhook / can be triggered manually.

I recently wrote hand-in-hand teaching you to use Jenkins to do Docker automatic publishing

although it is not the same as deploying to k8s, the process is basically the same.

our company also maintained jenkins-library to do this process before. When it is empty, I can sort it out and send it out.

build tasks triggered by: develop merge to master.

Jenkins.

Gitlab CI/CD,.

Gitlab CI depends on Gitlab runner, and then controls the overall release process by configuring. Gitlab-ci.yml.

there is nothing to say about this, just look at the official documents or other materials.

Menu