Hello friends, and welcome back to my channel. I am Ashfaque, and in today's video, we will build a complete CI/CD pipeline using Jenkins, Maven, Docker, and the Elastic Kubernetes Services (EKS). In our CI/CD pipeline, if a developer makes any changes on the application repository on GitHub, then it will trigger the CI job of the Jenkins, which will pull the code from the application repository. It will build and test the artifact using Maven. Then we will do the static code analysis of the artifact using SonarQube. Then we will build the Docker image, and we will push that Docker image to the Docker Hub. After that, we will scan the Docker image using Trivy scan. Here, our CI job will end. Once our CI job has been completed, our CD job will automatically get triggered, and our CD job will first update the build number or the release number in the deployment YAML file on the GitOps repository on GitHub. And then ArgoCD will pull the manifest file, updated.

manifest file from the GitHub repository, and it will deploy the resources on the EKS cluster. Once our CD job is finished, it will send the notification over the slack or it can send the email also. So let's start building our project. First thing is we need to create the Jenkins Master virtual machine on the AWS console. I will go to instances, launch instance. I will give the name Jenkins master. I will select OS as Ubuntu, AMI. I will select which is free tier eligible instance type t2 micro, key pair. I will create a new key pair and hard disk. I will select 15 GB launch instance. I will copy the public IP of the virtual machine and I will access it from my local system. I will select the key pair. I will first do the system update. I will open the hostname file and I will change the hostname to Jenkins master. I have changed the hostname of the virtual machine so I will go ahead and reboot my system. System is rebooting. Meanwhile I will go to AWS console, I will go to Security Group.

and I will add the inbound rule because Jenkins works on the port 8080. Reboot completed, I will reconnect to Virtual Machine. I will install the Java with this command. If I give the command Java -version, so this is the version of the Java which has been installed in my system. I will go to Jenkins documentation page and under the Ubuntu, I will copy this weekly release and I will paste it here on my server to start the installation of Jenkins. This command will enable the Jenkins service to start at every boot. I will now give the command to start the Jenkins service and if I give the command system status Jenkins, so Jenkins is running in my server now. I will again go to AWS console and create one new virtual machine called Jenkins agent. Name I will give Jenkins agent. I will select Ubuntu. I will select my key pair hard disk. I will provide 15 GB launch instance. I will copy the public IP of the virtual machine and I will access it from my local system.

I will do the system update. I will open the hostname file and I will change the hostname of this virtual machine to Jenkins agent. I have changed the hostname of this virtual machine, so I will have to reboot my system. Reboot completed. I will reconnect to my machine. I will go ahead and install the Java in my server. Java has been installed in my system. All the builds will happen on this Server, so I will go ahead and install the docker in this server with this command. I will give the full rights to my current user on the docker with this command. So I have added my current user on the group Docker, so I will go ahead and reboot my system. Restart completed. I will reconnect to my machine and I will open the file SSH configuration file and in this file I will make public key authentication yes and I will uncomment this also, authorize key file. I will save and close this file. I will go to Jenkins master and here also I will open the same file and I will uncomment the public key authentication.

and authorized key file. I will save and close this file. Also, I will reload the SSH service on the agent. Also, I will reload the SSH service. I will now go to Jenkins Master node, and here I will generate the SSH key with this command SSH hyphen Keygen. Okay, so key has been generated. I'm inside the /home/ubuntu. I will go to .SSH directory, and inside this directory, I am having this public key, and this is the private key. So, I will open the public key, and I will copy the complete content of this key file, and I will go to Jenkins agent. On the Jenkins agent, I'm inside the /home/ubuntu. I will go to .SSH directory, and here I am having authorized keys file. I will open this file, and I will paste the copied content here, and I will save this file. So, if I open this file, inside the file, I am having the public key of the master node. I will now copy the public IP address of the Jenkins master.

and I will open it with the port 8080 on the Jenkins master. I will open this file, and I will copy and paste this password here. Install suggested plugins. I will give the username clouduser. I will set the password, save and continue, save and finish, just start using Jenkins. I will go to manage Jenkins, and under system configurations, I will go to nodes, built-in node, configure, and number of executors. I will make zero, and I will save it. I will again go to manage Jenkins, nodes, new node. I will give the name Jenkins agent permanent agent, create number of executors. I will make two, remote root directory. I will give /home/ubuntu, which is the home directory of the Ubuntu user on the agent server. Label. I will give Jenkins agent. Usage. Use this node as much as possible. Launch method. I will select launch agents via SSH. Host. I will copy the private IP address of the agent, and I will paste it here because both are in the same VPC. If they are not in the same VPC, you will have to provide here the public IP address.

credentials. We don't have any credential. I will click on Add. Jenkins kind SSH username with private key. ID I will give here Jenkins agent description. I will give Jenkins agent, username Ubuntu private key, enter directly. I will go to Master node and this is the private key. I will copy the private key. I will click here on Add and I will paste the private key here and I will click here on Add under the credentials. I will select the credentials which we have just created and host key verification strategy. I will select non-verifying verification strategy and I will click on Save so agent has been added to my Jenkins. I will go to my dashboard and I will create the new job. I will give the name as test pipeline, okay pipeline script. I will select hello world, apply, save and I will do the build now so the build completed successfully on the agent which means our connectivity between master node and the agent is successful. I will delete this test job. I will now install and configure the few plugins on the Jenkins so I will go to manage Jenkins.

plugins, available plugins, and I will search here Maven. I will select this plugin Maven integration, and pipeline Maven integration, and I will also search here Eclipse. I will select this Eclipse Timurin installer, and I will click on install. Okay, so installation completed. I will go to home, and now I need to configure these plugins. So I will go to manage Jenkins tools. I will go to Maven installations, add Maven. Name, I will give Maven3, and this name will be recalled in the pipeline script. I will tick here install automatically, apply, and Save. I will again go to tools, and this time I will go to JDK installations, add JDK, and name, I will give Java 17. This name again will be recalled in the pipeline script. I will tick on install automatically. I will click here add installer, and I will select install from adaptian.net. And in the drop-down, I will select the JDK version 17.0.5+8. This is the version we will use for the JDK.

apply and Save. I will now go ahead and add the GitHub credentials to the Jenkins. So I will go to Jenkins dashboard, manage Jenkins credentials under security, and here in the drop-down I will click on add credentials. Username with password. Username I will give my username for the GitHub. Password I will paste here my personal access token. If you want to create the personal access token on the GitHub, go to settings, developer setting, personal access token, token classic, and you can generate the token here. ID I will give the GitHub. Description I will give GitHub. We will recall this ID in the pipeline script. I will click on create. Okay, so I will go to my GitHub account and this is my Repository. Sorry, I will go to my Repository. This is my repository Register App on this Repository. I will create the Jenkins file. I will give the name Jenkins file and I will start creating the pipeline script. So first of all, I will define my agent in the pipeline. So this is our agent name in the Jenkins Jenkins agent and then I will recall the tools.

which are actually the plugins which we have configured in the Jenkins. So, the first tool is Java 7, which is the name we have given in the previous step, and this is the name for the Maven plugin Maven 3. Both we have defined in the Jenkins, in the previous step. Okay, so we have defined our agent and we have recalled the tools. Now we will start creating the stages. So under this stage, we will define our first stage. So our first stage will actually clean up the workspace. We have given the name cleanup workspace. It will clean our workspace. Now I will go ahead and create our second stage, which would be checked out from SCM. So our second stage is check out from SCM and this is my Repository Register App and this is the branch Main and this is the credential ID github which we have defined on the Jenkins dashboard. And the next stage we will add which would be build application build application with the command mvn clean package and I will create the next stage.

which will actually test our application with this command mvn test. I will save this file. I will go to my Jenkins dashboard new item. I will give the job name register-app-ci, pipeline. Okay, I will click on discard old bill under the log rotation max of builds to keep. I will type here 2. I will not set any build trigger as of now. Under pipeline, I will select pipeline script from SCM. I will give my repository name, repository url SCM git, and I will give my GitHub repository credentials. I will select the GitHub credentials branch main script path Jenkins file. Apply and Save. I will now go ahead and click on build now. Okay, so job completed. Next task is to set up the SonarQube. So on the AWS console, I will go to launch instances. I will give the name SonarQube Ubuntu and instance type. I will select t3 medium. T2 micro is insufficient because we will be installing postgresql and SonarQube in this VM.

I will select my key pair disk. I will select 15 GB launch instance. I will copy the public IP of the virtual machine and I will access it from my local system. First of all, I will update the package Repository. I will install the postgresql. Postgresql has been installed. I will enable it. Now I will create the database for the SonarQube. I will set the password. You have to remember this password. Okay, so database for the SonarQube has been created. I will now go ahead and add the adaptium repository. I will now go ahead and install the Java. So this is the version of the Java which has been installed. Now I need to do some Linux kernel tuning. So first of all, I will increase the limits. I will open this file and at the end of the file I will add these two lines. Now I will increase the mapped memory regions, so I will open this file and I will go to the end of this file and I will add this line. I will save and close this file.

okay, now I will go ahead and reboot my system. System is rebooting. Meanwhile, I will go to the virtual machine on the AWS console, and I will go to security groups, edit inbound rule, add rule, and I will allow the port 9000 because we will be accessing the SonarQube over the port 9000. Okay, reboot completed. I will reconnect to my server, and from here, we will actually start the SonarQube installation. So, first of all, I will download the packages. I will install the unzip in my system. I will now create the user and set the permission for that user. I will now update the SonarQube properties with the database credentials. So, I will open one file, and in this file, here Sonar JDBC username, I will uncomment and give the username as sonar, and I will give the password which we have set. And here Sonar JDBC URL, I will provide. I will save and close this file. I will now go ahead and create the service for the SonarQube.

so I will open this file, and I will give the entries in this file. I will save and close this file. I will now start the SonarQube, and I will enable the service. So SonarQube service is running in my system, and we can watch the log file and monitor the startup with this command. I will copy the public IP of the SonarQube server, and I will access it on the browser with port 9000. So username is admin, password is also admin. You will have to set the new password. So I will give the old password, which is the admin, and I will set the new password. So here we have set up our SonarQube server. Next step is to integrate the SonarQube with the Jenkins. So on the SonarQube home page, I will go to my account security. Under the generate tokens, I will give the name to the token, Jenkins SonarQube token, type I will select global analysis token.

expire in, no expiration and I will click on generate copy this token to your local system now using this token. I will create the credentials under the Jenkins. So on the Jenkins dashboard, I will go to manage Jenkins credentials add new credentials kind. I will select secret text and here I will paste our token which we have created just now and ID. I will give Jenkins SonarQube token. I will click on create. Okay, so token has been created in the Jenkins. Now I will install and configure the few plugins on the Jenkins. So I will go to manage Jenkins plugins available plugin and I will search here sonar. So I will select this one sonar qube scanner and sonar quality gates. And the quality gates I will click on install and here I will tick restart Jenkins when installation is completed. So you can see here quality gates plugin and sonar quality gates plugin has been installed and scanner also installed in my system. You can ignore this warning because in the previous

step we have given the database credentials in the plain text so it is giving the warning. If you want to ignore this warning, just go to configure which of these warnings are shown and here under the security warning untick these warnings. Apply and Save. I will now go ahead and add the SonarQube to my Jenkins. I will go to manage Jenkins, system, and here I will click on add SonarQube. Name I will give SonarQube server and the URL I will provide private IP address of the SonarQube server colon 9000. Server authentication token I will select this Jenkins SonarQube token which we had created using the SonarQube API token. Apply and Save. I will now go ahead and add the SonarQube scanner in my Jenkins. So I will go to manage Jenkins, tools, and under the SonarQube scanner installations I will click here on add SonarQube scanner. Name I will provide SonarQube scanner.

install automatically apply and Save. Now I need to add the stage for the 
SonarQube analysis in my pipeline script. So on my GitHub repository, I 
will go to edit the Jenkinsfile and after the test application stage, I will add one more stage. The name of this stage is SonarQube analysis. So this is the credential ID which we have 
given in the Jenkins. Jenkins SonarQube token. I will save this file. I will go to Jenkins job and I will click on build now. Okay, so build successful and the new stage has been added 
to our pipeline, which is the SonarQube analysis. If I go to SonarQube dashboard, under the 
projects, you can see this is my build. I need to now create the SonarQube webhook. Without this webhook, your pipeline will fail. 
So on the SonarQube dashboard, I will go to Administration and under the configuration, I 
will go to drop down and I will select webhooks. So as of now, there is no webhook on my SonarQube dashboard. I will click here on create.

I will give the name to the webhook, SonarQube webhook, and I will provide the URL. This is the IP address of the Jenkins server. I will click on create. I will now go ahead and create the one more stage under my pipeline script for the quality gate. So I will go to my repository. I will open the Jenkinsfile. I will edit it and I will add one more stage, and the name of the stage is quality gate. This is the step, and this is the credentials which we had defined for the SonarQube in the Jenkins. I will correct the indentation. I will save the file, and I will again go back to my job on the Jenkins, and I will click here on build now. So the job completed successfully, and the one more stage for the quality gate has been added to our pipeline. I will now go ahead and install the docker-related plugins in my Jenkins. So on the Jenkins dashboard, I will go to manage Jenkins, plugins available plugins, and I will search here docker.

so I will select this plugin: Docker Commons, Docker Pipeline, Docker API, Docker Build Step, and Cloud-based Docker Build and Push. So, total six plugins I have selected. I will click on install and I will tick here, restart Jenkins when installation completed. I will now add the Docker Hub credentials in my Jenkins. So, I will go to manage Jenkins credentials, add credentials, username with password. Username I will provide my username of the Docker Hub, password I will provide the access token. You can go to account setting on the Docker Hub security and you can create here the access token ID. I will give here Docker Hub. Create. I need to now define the variables in my pipeline script. So, on my GitHub repository, I will open the Jenkins file. I will go to edit and here I will add the environment variables. So, these are the environment variables which I will add here. So, this would be my application name: register-app-pipeline, and this will be my release, and this is my Docker Hub username.

and these are the credentials which we 
have just created for the docker hub. I will close the bracket. I will go ahead and add the one more 
stage for the build and push Docker image, and this stage will actually build the docker 
image and it will push it to the docker hub. So name would be build and push Docker image. I will commit these changes to the file and now if I go to, so this is my application name or 
image name, so if I go to my Docker hub there is no image present with 
this name on my Docker Hub account. I will go to Jenkins dashboard, I will go to my job and I will click on build now. Okay, so job completed. If I go to 
Docker Hub and do the refresh here, so you can see the image has been 
pushed here a few seconds ago. I will now go ahead and add two more 
stages on my Jenkins pipeline script, the first stage would be Trivy 
scan which will actually scan our.

Docker Hub image so or on the GitHub repository. I will edit the Jenkins file, and I will add the stage. So the stage name is trivy scan. It will scan the latest image on the Docker Hub with the name register-app-pipeline. This is my username of the Docker Hub, and I will add the one more stage with the name cleanup artifacts, which will actually clean the created artifacts from the workspace. So stage name is cleanup artifact. It will actually clean the previously created Docker image. I will save the Jenkins file. Next step is to create the eks bootstrap server. So on the AWS console, I will go to launch instances. I will give the name eks bootstrap server Ubuntu t2 micro. I will select my key pair launch. I will copy the public IP address, and I will access it from my local system. I will first do the system update. I will open the hostname file, and I will change the host name of this machine to eks bootstrap server. I will go ahead and reboot my system. Reboot completed. I will reconnect.

I will now go ahead and install the AWS CLI in this server. So, I will give the command to download the AWS CLI. I will install the unzip with this command. I will unzip the downloaded AWS CLI package. I will run it. So, this is the AWS CLI version installed in my system. I need to now download the I. I need to now install the kubectl in this server, so first of all I will download the kubectl with this command. So, kubectl is not having the executable permission, I will give it with this command. Now the kubectl is having executable permission. I will move the kubectl to /bin because all the executable files are present in the /bin. So, this is the version of the kubectl which is installed in my server. You can ignore this warning because we are not connected to any Kubernetes cluster. I need to now install the eksctl in this server. So, I will download the package in the temp folder with this command. I will go to tmp folder and if I do the ll, so eksctl is already having the

executable permissions here. So, I will move the eksctl file from the /tmp to /bin with this command, because all the executable files are present under the /bin. If I give the command eksctl version, this is the version of the eksctl which has been installed in my server. I have to now create the IAM role, which we will assign to eks bootstrap server. So, on the AWS console, I will go to IAM roles, create role, AWS service ec2. Next, I will give the administrator access, next, I will give the name to the role eksctl_score role, create role. Okay, so role has been created. I will go to ec2 instance of the bootstrap server, actions, security, modify IAM role, and here in the drop down, I will select the role which we have just created, update IAM role. I will now go ahead and create the EKS cluster. For that, I will go to terminal of the bootstrap server, and I will give here the command to create the EKS cluster. This would be the name of my cluster.

I will give the region in which I want to create my cluster. I will give the node type, which is t2 small. I will give the node count, which is 3. In my case, this EKS cluster creation will take some time. I will pause the recording here and I will resume once it is completed. EKS cluster creation completed. If I give the command kubectl get nodes, so these are three nodes in my cluster. Next task is ArgoCD installation and configuration. So first of all, on the bootstrap server, I will create the namespace for the Argo CD with this command: kubectl create namespace argocd. Okay, so namespace for the ArgoCD has been created. Let's apply the yaml configuration files to ArgoCD. I will give the command for that. Now we can view the Pods created in the ArgoCD namespace. So I will give the command kubectl get pods namespace argocd. So these are the pods running inside the ArgoCD namespace. To interact with the API server, we need to deploy the ArgoCD CLI.

I will give the command to deploy the ArgoCD CLI. I will give the executable permission. Now we need to expose the ArgoCD server to 
the external world by creating the load balancer. So we will do the same with this command. So it is creating the load balancer in the 
background, which may take three to five minutes. If I give the command kubectl get service namespace argocd. So this is the load balancer created for the ArgoCD. We can access the ArgoCD cluster with this URL. But before that, we need to extract 
the password for the ArgoCD. So I will give the command to get the password. Now we need to decode it. So I will decode 
with the command Echo and the password base64 --decode. So this is the decoded password. I will copy the DNS name for the load balancer created for 
the ArgoCD cluster. I will go to the browser and I will browse it. I will give the username and I will give the password which we have decoded.

okay, so we have signed into our ArgoCD cluster. I will go to user info, update password. I will give the current password, I will set the new password, I will confirm the password, save new password. I will do the log out and I will log in with the new password. Next task is to add our EKS cluster to the ArgoCD. For that, first of all, we will have to log in to ArgoCD from the CLI. So I will give the command ArgoCD login and I will provide the URL of the ArgoCD cluster. ArgoCD login and the name URL of the ArgoCD cluster hyphen hyphen username admin. So this is my complete command. I will hit enter. I will provide the password which we have set for the ArgoCD cluster on the browser. Okay, so login successful. We have successfully logged into the ArgoCD cluster over the CLI. If I go to ArgoCD dashboard, settings, cluster. So under the ArgoCD, we have only one cluster as of now.

which is the default cluster of the ArgoCD. If I give the command ArgoCD cluster list, so it is the same cluster which I have shown you in the browser. ArgoCD cluster. There is no other cluster added to ArgoCD now. This is the default cluster of the ArgoCD. Now I need to extract the name of my EKS cluster to give the command to add my EKS cluster to the ArgoCD. So if I give this command. Cubectl config get context. It will show the details of my EKS cluster. So this is my EKS cluster. I will now give the command to add my EKS cluster to the ArgoCD. So I will start the command argocd cluster add and the name of my EKS cluster. I will copy from here and provide it here --name. I will give the name to my EKS cluster which is easily identifiable under the ArgoCD. So this is the name I am giving to my EKS cluster under the ArgoCD.

virtualtechbox hyphen eks hyphencluster. I will hit the enter here. Yes, it actually creates the role binding if I give the command now argocd cluster list. So now I can see both the cluster. This is the default cluster of the Argo CD and this is my EKS cluster which I have added to ArgoCD just now. If I go to dashboard and do the refresh here, so you can see here both the cluster are available. Default cluster of the ArgoCD and my EKS cluster added to ArgoCD. This is my another repository on the GitHub which is having the Manifest file for the Kubernetes. I need to now connect this repository to my ArgoCD cluster. So I will go to ArgoCD dashboard and under the settings, I will go to repositories, connect repo via https type git, project default. I will give the Repository URL. I will give here my username for the GitHub and under the password, I will give my personal access token for the GitHub.

and I will click on connect. So, repository has been added to the ArgoCD dashboard. So, I have to now deploy the resources and application on my EKS cluster through the ArgoCD. So, one thing should be noted here in my Repository. If I go to deployment yaml file, the name and the version number of the image should match to my image and version number of the Docker Hub image. So, on the ArgoCD dashboard, I will go to new app. I will give the name Register App. Project name I will select default. Sync policy I will select automatic. I will tick these two options prone resources and selfheal. And the repository I will select my GitHub repository which I had added in the previous step. And this repository contains the manifest file for the kubernetes. Path I will select dot slash. Destination I will select my EKS cluster in the drop down. Namespace I will select default. It will deploy the resources on my eks cluster in the default namespace. I will click on create.

so cluster sorry the application has been created on my EKS cluster. On the terminal of the bootstrap server, if I give the command kubectl get pods, these are the pods running in the default namespace of my EKS cluster. And to get the external DNS name for my application, I will give the command kubectl get svc, which will show the service details of the service created in the default namespace. So this is the external DNS name of the load balancer created for this application through the service manifest file. So I will copy this DNS name and I will browse it on the new tab with the port 8080 because my container is running on the port 8080. This is the default home page of the Tomcat. And if I give the slash web app, this is my application deployment happening perfectly on the EKS cluster through the ArgoCD. Now we need to automate this deployment process. So I will go to Jenkins dashboard and I will create the CD job now.

I will give the name to the CD job, pipeline. Okay, discard old build. Max of build to keep, I will give two, and I will tick here. This project is parameterized, and I will click on add parameter, and I will select this string parameter. Name I will give image tag, because every time our CD job will change the image tag on the deployment manifest file on the GitHub repository. And then I will tick here on trigger builds remotely, and I will give the authentication token name git ops hyphen token, and pipeline definition. I will select pipeline script from SCM, and the SCM I will select Git. I will give the Repository gitps repository on my GitHub, which is having the manifest file for the Kubernetes credentials. I will select GitHub credentials. Branch I will select here Main, and then apply and Save. Now I will go to my application repository on the GitHub, and I will open the Jenkins file. And actually, I need to add one more stage on my Jenkins file, and the stage name would be trigger CD pipeline.

and this stage will actually trigger the CD pipeline. This would be the last stage of our pipeline script. So I will go to edit and here I will add one more stage. Stage name is trigger CD pipeline. In this command, this is the parameter which we have given in the previous step. This is actually the DNS name of my Jenkins server. So this DNS name for our Jenkins Master node. This is the CD Job which we have just created. And this is the token which we have just provided in the Jenkins job. I will correct the indentation. I will save this file in my Jenkins file. On the last stage, we have recalled this Jenkins API token, so we need to create this token and we need to define it as the variable in the pipeline script. And in this stage, Cloud user, this is my username on the Jenkins. So I will go to Jenkins dashboard and under my username, I will go to configure. And under API token, I will click on add new token. I will give the name

Jenkins API token, and I will click on generate. And this is the token generated. And note one thing here, if I click on this button copy token, so message is coming copy only supported with a secure https connection. And we are not using the https, we are using the HTTP. So this button will not work. So I will copy the plain text, and I will save it in my local system because it will not appear later. I will go to Jenkins dashboard. I will go to manage Jenkins credentials. Add credentials kind. I will select secret text. And here I will provide the Secret. Sometimes here copy doesn't work. So I will type my secret here. ID, I will give Jenkins API token. I will give the description. And I will click on create. Okay, so API token has been added. Now I will go to my GitHub repository because I have to define this API token as the variable in my pipeline script. So I will go to my GitHub repository. I will open the Jenkins file. I will edit it.

and I will provide here one more variable Jenkins API token. I will save it. Next task is to create the Jenkins file in our git ops repository because our CD job has been configured with that repository, and that repository is not having the Jenkins file. Our CD job has been configured as the declarative job which will pull the Jenkins file from the GitHub repository. So I will go to my git ops repository which has the manifest file for the Kubernetes. I will create the new file in this Repository. I have given the name Jenkins file. I will define my agent. So this is my Jenkins agent name, Jenkins agent. Then I will define the variables. So I'm giving the one environment variable which is the app name and our app name is register app pipeline. So we have defined the agent and we have defined the variable. Now I will go ahead and create the stages. Okay so I will create my first stage which will be cleanup workspace, which will clean the workspace with this command.

and then I will add another stage checkout from SCM. So it will use the credential ID GitHub defined in the Jenkins. And this is my git Ops Repository and the branch is Main. So we have defined the two stages. Now I will Define my another stage which will actually update the deployment tags but locally. And this is my deployment manifest file present in this Repository. Once it it has changed, it has updated the tags in the deployment manifest file. It will push that changes to the GitHub repository which would be done in the next stage push the changed deployment file to Git. So in this stage this is my username of the GitHub, this is my email ID. And it will push the locally changed deployment dot yaml file to the remote Repository. It will use the credentials defined in the Jenkins, the name is GitHub. This is my remote Repository and this is the branch. So it will push the changed file with this command to the remote Repository to the main branch. I will save this file. Everything has been set up. Now it's time to verify our CI CD pipeline, before I verify.

my cicd pipeline. I will set the trigger in my CI job, so I will go to my Jenkins CI job configure. Under the build trigger, I will click here, poll SCM. I will provide the schedule, which is actually every minute. It will monitor this Repository every minute, and if there is any change on this Repository, it will trigger the build job. Apply, save. I have opened the CI job and CD job on two different tabs, and I am connected to my remote Repository from my local system using Git Bash. In my Repository, I'm inside this folder, so I will open the index.jsp file, and here I will add a new line. So I have added a new line, which says happy learning. I will save this file. I will now push these changes to remote Repository. Okay, so changes have been pushed, and my Jenkins CI job has been triggered automatically. Note one thing here: this is our build number eight. So CI job completed. If I go to CD job, it has also triggered automatically upon the completion of CI job.

so CD job completed successfully, and our build number was 8. If I go to Docker hub and do the refresh here, so the image has been pushed just now. And if I go to the image, the image is having the latest tag with the latest build number, which is 8. If I go to my git ops repository and do the refresh here and open the deployment.yaml file, so in this file, my image is having the latest tag, which is the eight. And if I go to Argo CD and do the refresh here and go to app app detail, so the app is using the latest release, which is the eight. And if I go to pod pod is also using the latest release. And if I go to my application and do the refresh here, so you can see here changes applied to our application. Also, we will test it once again. I will go to the Repository. I will again open the index.jsp file, and this time I will add here see you again. I will save this file. I will push the changes to the remote Repository.

if I go to CI job, it has triggered automatically
upon the push on the GitHub repository. CI job completed successfully. If I go to CD job, it has automatically triggered
upon the completion of CI job. CD Job also completed successfully and note the build number in our CI job
and the build number is 9. If I go to Docker hub and do the refresh here, so image
has been pushed just now. If I go to image, image is having the latest build number, which is the nine. If I go to ArgoCD dashboard
and do the refresh here and go to app app details, so app is using the latest release, which is the nine. And if I go to pod, it is also using the latest release. And if I go to my application
and do the refresh here, so changes have been applied to my application also. By this way, you can set up declarative CI CD pipeline using Jenkins, Docker, ArgoCD, and the EKS any change on the GitHub repository.

will trigger the CI job on the Jenkins, and once CI job is completed, CD job will be triggered automatically, and upon the completion of the CD job, we will have the changes applied onto our application. Hope you find this video helpful. You can fork my Repository, create your own branch, and practice the complete project. During the practice, if you face any kind of difficulty, you can ask me in the comment section. I will definitely reply to your query. Follow me on LinkedIn. I post multiple useful things frequently on LinkedIn. Also, if you find this project helpful, then like the video. A lot of effort went behind this video, so do subscribe to my channel to encourage my work. Share this video with the friends and spread the knowledge. I look forward you to join me in the next video. Thank you.

Real Time DevOps Project | Deploy to Kubernetes Using Jenkins | End to End DevOps Project | CICD

Real Time DevOps Project | Deploy to Kubernetes Using Jenkins | End to End DevOps Project | CICD

스크립트