https://github.com/shirshadatta/rolling-updates-with-zero-downtime

Rolling updates with Zero-downtime using K8s rollout features automatically by Jenkins Dynamic Slave
https://github.com/shirshadatta/rolling-updates-with-zero-downtime

dockerfile dynamic-jenkins-cluster shell web-app

Last synced: 15 days ago
JSON representation

Rolling updates with Zero-downtime using K8s rollout features automatically by Jenkins Dynamic Slave

• Host: GitHub
• URL: https://github.com/shirshadatta/rolling-updates-with-zero-downtime
• Owner: ShirshaDatta
• License: mit
• Created: 2020-07-23T10:36:20.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2020-10-09T12:28:06.000Z (over 4 years ago)
• Last Synced: 2024-11-19T19:26:05.106Z (3 months ago)
• Topics: dockerfile, dynamic-jenkins-cluster, shell, web-app
• Language: Dockerfile
• Homepage:
• Size: 15.6 KB
• Stars: 2
• Watchers: 0
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Rolling-Updates-with-Zero-Downtime

Create A dynamic Jenkins cluster and perform task-3 using the dynamic Jenkins cluster.

Steps to proceed as:

1.  Create container image that’s has Linux  and other basic configuration required to run Slave for Jenkins. ( example here we require kubectl to be configured )

2. When we launch the job it should automatically starts job on slave based on the label provided for dynamic approach.

3. Create a job chain of job1 & job2 using build pipeline plugin in Jenkins 

4.  Job1 : Pull  the Github repo automatically when some developers push repo to Github and perform the following operations as:

    1.  Create the new image dynamically for the application and copy the application code into that corresponding docker image

    2.  Push that image to the docker hub (Public repository) 

 ( Github code contain the application code and Dockerfile to create a new image )

5. Job2 ( Should be run on the dynamic slave of Jenkins configured with Kubernetes kubectl command): Launch the application on the top of Kubernetes cluster performing following operations:

    1.  If launching first time then create a deployment of the pod using the image created in the previous job. Else if deployment already exists then do rollout of the existing pod making zero downtime  for the user.

    2. If Application created first time, then Expose the application. Else don’t expose it.

    

    To know how have I done it, go through this:

    

    https://medium.com/@shirshadatta2000/web-server-with-live-rolling-updates-using-dynamic-jenkins-slave-node-and-kubernetes-28b13b04731e?sk=1f9406f4c6e55f158c413050ae3dd89f