DTASK3

DevOps Task 3:

Perform task on top of Kubernetes where we use Kubernetes resources like Pods, ReplicaSet, Deployment, PVC and Service.

1. Create container image that’s has Jenkins installed using Dockerfile or you can use the Jenkins Server on RHEL 8/7

2. When we launch this image, it should automatically starts Jenkins service in the container.

3. Create a job chain of job1, job2, job3 and job4 using build pipeline plugin in Jenkins 

4. Job1: Pull the Github repo automatically when some developers push the repo to Github.

5. Job2 : 

  1. By looking at the code or program file, Jenkins should automatically start the respective language interpreter installed image container to deploy code on top of Kubernetes ( eg. If code is of PHP, then Jenkins should start the container that has PHP already installed )

  2. Expose your pod so that testing team could perform the testing on the pod

  3. Make the data to remain persistent ( If server collects some data like logs, other user information )

6. Job3: Test your app if it is working or not.

7. Job4: if the app is not working, then send email to the developer with error messages and redeploy the application after code is being edited by the developer

---------------------------------------------------------------------------------------------------------------

Creating Dockerfile for Jenkins

Launching docker with the same image which was created by above dockerfile

Starting Jenkins service and httpd server

Job1:

Pulling files from Github to "data" folder. If files with extension html and php are there then copy it into /var/www/html folder.

Copying configuration file which is present in ".kube" folder, also some certificates from the base system.

Config file which was copied to .kube folder.

In Jenkins container: PV, PVC, and deployment files there.

Job2-a:

This job runs when job1 runs successfully.

If html files are present then check if that file works or not from Jenkins container, if it works fine then from creating Persistent Volume, then claim it with PersistentVolumeClaim. Then, create deployment and then expose it. Lastly. it will send mail if doesn't works fine.

[Here deployment is created because if pod fails, then other one launches automatically.]

Job2-b:

This job runs when job1 runs successfully.

If php files are present then check if that file works or not from Jenkins container, if it works fine then from creating Persistent Volume, then claim it with PersistentVolumeClaim. Then, create deployment and then expose it. Lastly. it will send mail if doesn't works fine.

Mail is sent with logs attached with it to developer.

See PVC is created or not, and deployment is working or not.