Step 1: Create one Linux instance. Step 2: In Linux instance install Jenkins and GIT. Step 3: setup maven Step 4: Install plugins: git, maven on jenkins Step 5: install maven: copy maven url from below link https://maven.apache.org/download.cgi #sudo su #cd /opt #wget https://dlcdn.apache.org/maven/maven-3/3.8.4/binaries/apache-maven-3.8.4-bin.tar.gz Un-zip the package.

#ls #mv apache-maven-3.8.4 maven maven #cd maven #cd bin #ll

Step 6: make it available for the root user. update under bash_profile
#cd ~ #pwd #ll -a NEED TO ADD THE JAVA PATH AS WELL AS THE M2 AND M2_HOME PATHS. #bash_profile (we need to edit it)

if [ -f ~/.bashrc ]; then . ~/.bashrc fi

PATH=$PATH:$HOME/bin

export PATH

=================

M2_HOME=/opt/maven M2=/opt/maven/bin JAVA_HOME=/usr/lib/jvm/java-11-openjdk-11.0.13.0.8-1.amzn2.0.3.x86_64

PATH=$PATH:$HOME/bin:$JAVA_HOME:$M2_HOME:$M2

SAVE THE ABOVE FILE USING :WQ

Step 8: https://aws.amazon.com/amazon-linux-2/ [ec2-user@jenkins-server ~]$ sudo su [root@jenkins-server ec2-user]# source .bash_profile [root@jenkins-server ec2-user]# echo $PATH /sbin:/bin:/usr/sbin:/usr/bin:/root/.local/bin:/root/bin [root@jenkins-server ec2-user]# pwd /home/ec2-user [root@jenkins-server ec2-user]# sudo su - Last login: Fri Mar 11 06:48:26 UTC 2022 on pts/0 [root@jenkins-server ~]# pwd /root [root@jenkins-server ~]# source .bash_profile [root@jenkins-server ~]# echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/usr/lib/jvm/java-11-openjdk-11.0.13.0.8-1.amzn2.0.3.x86_64:/opt/maven:/opt/maven/bin:/root/bin:/usr/lib/jvm/ java-11-openjdk-11.0.13.0.8-1.amzn2.0.3.x86_64:/opt/maven:/opt/maven/bin [root@jenkins-server ~]# mvn --version Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537) Maven home: /opt/maven Java version: 11.0.13, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-11-openjdk-11.0.13.0.8-1.amzn2.0.3.x86_64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.10.102-99.473.amzn2.x86_64", arch: "amd64", family: "unix" [root@jenkins-server ~]# pwd /root Go to Jenkins UI > download maven plugin

manage jenkin > jenkins installation > maven installation unchecked the box , install automatically Name - java-11 JAVA_HOME - /usr/share/doc/java-11-openjdk-11.0.13.0.8-1.amzn2.0.3.x86_64

Now add maven on jenkin UI Name - maven MAVEN_HOME - /opt/maven Apply and save

Step 9: Tomact installation

Step 10: Integration of tomcat with jenkins::::: Install plugin "deploy to container" manage jenkins > manage credentials > jenkins > global credentials > add credentials kind - username and pw id & desc - tomcat_deployer uname - deployer pw - deployer save it

Step 11: To deploy war file on tomcat Now, create new job name it - buildanddeploy (maven project) add git repo branch - master clean install post build action - deploy war/ear to a container war file - webapp/ ======================== DOCKER SETUP ========================

STEP 1:

LINUX INSTANCE >>>INSTALL DOCKER >>START DOCKER CONTAINER>>NORMAL DOCKER COMMANDS FOR PRACTICE

STEP 2:

Docker image form the docker hub. Initially using docker hub for the image. To rename your host name:

Edit the name in the file and :wq In-order to make it active we need to re-boot the system : #init6 (instance was not able to start after running this command not recommended to run)

DOCKER PULL:

FIRST WE NEED TO START THE DOCKER SERVICE #service docker start #docker pull tomcat #docker images >>> tomcat image and image id in O/P #docker run -d --name tomcat container -p 8081:8080 tomcat Container runs inside your docker host. Need to map it to external port:8081, internally running on port 8080 #docker ps -a (to list containers) To access this container outside form the container: Take public id: 8081 (need to open this port on the security group: select 8081-9000 to open more posts until 9000) NOW TAKE THE PUBLIC IP :8081

FIXING TOMCAT ACCESS ISSUE ON THE BROWSER THAT WE GOT: "HTTP Status 404 – Not Found" TO CONNECT TO THE CONTAINER: #docker exec -it tomcat-container /bin/bash #ls #cd webapps.dist #ls
(The content which is inside this we need to copy it to our "webapps" folder than only we will be able to access our app)

cp=copy -R=recursive

• in the current directory whatever is there .. 1 folder above in webapps directory

NOW WE WILL BE ABLE TO IT FROM THE BROWSER: http://3.109.203.23:8081/ You'll be able to see the tomcat webpage by refreshing this page which was throwing an error earlier.

The changes will be temporary. if the instance is re-created.

STEPS FROM THE TERMINAL ITSELF:

root@c5d0a32da6b5:~# exit exit [root@docker_host ec2-user]# docker ps -a

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES c5d0a32da6b5 tomcat "catalina.sh run" 10 minutes ago Up 10 minutes 0.0.0.0:8081->8080/tcp, :::8081->8080/tcp tomcat-container

[root@docker_host ec2-user]# docker stop tomcat-container tomcat-container [root@docker_host ec2-user]# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES c5d0a32da6b5 tomcat "catalina.sh run" 11 minutes ago Exited (143) 4 seconds ago tomcat-container [root@docker_host ec2-user]# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

WE HAVE UPDATED THE CHANGES ONLY ON THE DOCKER CONTAINER. WHENEVER WE LAUNCH A NEW CONTAINER WITH THE IMAGE. CHANGES WILL NOT COME UP ON NEW IMAGES. YOU WILL GET THE SAME ERROR : HTTP 404 NOT FOUND. http://3.109.203.23:8082/ FOR THIS WE LAUNCHED A NEW CONTAINER USING PORT 8082 THIS TIME/EARLIER WE RAN IT ON 8081 (TOMCAT-CONTAINER): NEW CONTAINER: TOMCAT-2 docker run -d --name tomcat-2 -p 8082:8080 tomcat:latest

TO RESOLVE THIS : WE ARE GOING TO CREATE A DOCKER FILE >>PULL TOMCAT IMAGE>>CUSTOMIZATION: COPYING THE FILE FROM WEB-APP DIST TO WEB-APPS LIKE WE DID EARLIER. CONTENT WILL BE ACCESIBLE UNDER WEB-APPS DIRECTORY. FROM HERE IF WE LAUNCH NEW CONTAINER WILL NOT SEE THE SAME ERROR.

IMPORTANT DOCKER INSTRUCTIONS: FROM, RUN, CMD , ENTRYPOINT, WORKDIR, COPY, ADD, EXPOSE, ENV SEE SIMPLE DEVOPS PROJECT GIT HUB REPO FOR DETAILED INFORMATION.

INSTALLING TOMCAT ON CENTOS:

1. PULL CENTOS FROM DOCKER HUB >>>>>FROM
2. INSTALL JAVA >>>>>>RUN
3. create this directory: /opt/tomcat DIRECTORY >>>>>>RUN
4. CHANGE WORK DIR TO /opt/tomcat (going inside dir) >>>>WORKDIR
5. Download tomcat packages : tomcat download >>>>ADD OR RUN COMMAND
6. Need to extract: taz.gz file >>>>>RUN
7. re-name the tomcat directory. >>>>>RUN
8. Port no:8080 >>>>>EXPOSE
9. Start the tomcat services. >>>>>CMD

COMMANDS: vi Dockerfile (EVERYTHING IN UPPER CASE)

FROM centos:latest RUN yum install java -y RUN mkdir /opt/tomcat WORKDIR /opt/tomcat ADD https://dlcdn.apache.org/tomcat/tomcat-9/v9.0.59/bin/apache-tomcat-9.0.59.tar.gz . RUNtaz-xvzfapache-tomcat-9.0.59.tar.gz RUNmvapache-tomcat-9.0.59 /* /opt/tomcat EXPOSE8080 CMD ["/opt/tomcat/bin/catalina.sh", "run" ]

NOW TO CREATE IMAGE OUT OF IT: #docker build -t mytomcat . (dot for the current directory) #docker images

---===============DOCKER 2==================

SCRIPT TO LAUNCH AN INSTANCE: #!/bin/bash

STEP 2:

To rename your host name >>

Edit the name in the file and :wq In-order to make it active we need to re-boot the system : #init6 (instance was not able to start after running this command not recommended to run) refresh the page.

STEP 3:

DOCKER PULL >>

FIRST WE NEED TO START THE DOCKER SERVICE: #service docker start #docker pull tomcat #docker images >>> tomcat image and image id in O/P

NEED TO CREATE A DOCKER USER: #useradd dockeradmin #passwd dockeradmin ~~docker

RUN THE BELOW COMMAND TO EDIT THE PERMISSIONS: (Commenting and un-commenting) #vi /etc/ssh/sshd_config #NEED TO RE-START THE SERVICES: #service sshd reload (Redirecting to /bin/systemctl reload sshd.service will show up in O/P)

NOW OPEN THE DUPLICATE SESSION:

IT WILL ASK FOR A PASSWD FOR THE DOCKER ADMIN

NOW NEED TO INTEGRATE THIS DOCKER HOST WITH THE JENKINS, NEED TO INSTALL A PLUGIN FOR THAT:

GO TO JENKINS DASHBOARD
GO TO MANAGE JENKINS
MANAGE PLUGINS: LOOK FOR "Publish Over SSH" INSTALL WITHOUT RESTART

ADDING SSH SERVER: MANAGE JENKINS >>> CONFIGURE SYSTEM -SCROLL DOWN TO MAKE THE CHANGES. -WE NEED TO PUT THE HOST NAME WHICH WE SELECTED EARLIER IN THE STEP 2 >>> SSH SERVER NAME : DOCKER

• NOW PUT THE PRIVATE IP OF YOUR DOCKER INSTANCE IN HOST NAME
• USERNAME: dockeradmin
• NOW SELECT THE ADVANCED OPTION ON RIGHT SIDE.
• Passphrase / Password: docker (this passwd was set in earlier steps)
• SCROLL DOWN AND LOOK FOR "TEST CONNECTION"
• SUCCESS

CREATING A DOCKER DIRECTORY: #sudo su #cd /opt

RUN: #chown -R dockeradmin:dockeradmin docker

NOW, CREATE NEW JOB IN JENKINS "BuildAndDeployJobOnContainer" Source Code Management: GIT URL Branch Specifier: /MASTER Build Triggers: Build whenever a SNAPSHOT dependency is built (SELECT IT) SELECT POLL SCM AND PUT 5 STARS. ***** Build: pom.xml Goals and options: clean install **Post-build Actions: (post steps)

• Name: DOCKER

**** Transfers:

• Source files: webapp/target/*.war
• Remove prefix: webapp/target
• Remote directory: //opt//docker

**Post-build Actions:

Name: DOCKER

****Exec command:

cd /opt/docker; docker build -t regapp:v1 .; (MAKE SURE YOU ARE GIVING SPACE HERE OTHERWISE YOU'LL GET ERRORS WHILE BUILD) docker stop registerapp; docker rm registerapp;
docker run -d --name registerapp -p 8087:8080 regapp:v1

CREATE A DOCKERFILE:

cd /opt/docker/Dockerfile

FROM tomcat:latest RUN cp-R/usr/local/tomcat/webapps.dist//usr/local/tomcat/webapps COPY./.war /usr/local/tomcat/webapps

BUILD THE JOB.

CHECK THE WEBSITE ON YOUR DOCKER SERVER.

---===============ANSIBLE================== UNTIL NOW WE WERE DOING THE DEPLOYMENT USING DOCKER. NOW WE ARE IMPLEMENTING ANSIBLE INTO THIS PIPELINE. ANSIBLE PLAYBOOKS WILL CREATE A CONTAINER OUT OF THE IMAGE.

1. LAUNCH AN EC2 INSTANCE AND INSTALL ANSIBLE ON IT.
2. Sec group: All Traffic
3. Launch Instance

{ ---Same thing without a password

ansibleadmin ALL=(ALL) NOPASSWD: ALL } **We have added the user which we created in the last step.

To disable tunneled clear text passwords, change to no here! #PasswordAuthentication no #PermitEmptyPasswords no PasswordAuthentication yes

:wq

====================== ***** INTEGRATION OF ANSIBLE WITH DOCKER ***** =============================

{ ---Same thing without a password

ansibleadmin ALL=(ALL) NOPASSWD: ALL }

===========GO TO YOUR ANSIBLE SERVER==============

commands for vi: gg >> up clear >> d+G

#exit #ansible all -m ping [WARNING]: Platform linux on host 172.31.38.12 is using the discovered Python interpreter at /usr/bin/python, but future installation of another Python interpreter could change this. See https://docs.ansible.com/ansible/2.9/reference_appendices/interpreter_discovery.html for more information. 172.31.38.12 | SUCCESS => { "ansible_facts": { "discovered_interpreter_python": "/usr/bin/python" }, "changed": false, "ping": "pong"

========================== INTEGRATING ANSIBLE WITH JENKINS =======================

To add an Ansible server into Jenkins:

Name: Ansible server Hostname: PRIVATE IP OF ANSIBLE SERVER Username: ansadmin SCROLL DOWN AND SELECT ADVANCED SETTINGS AND PUT PASSWORD FOR THE ANSIBLE SERVER. Passphrase / Password: ansible

TEST CONFIGURATION >>> APPLY >> SAVE INTEGRATION OF ANSIBLE AND JENKINS IS SUCCESSFULLY DONE.

#NAME: Copy_Artifacts_onto_Ansible

#COPY FORM: BuildAndDeployJobOnContainer

GO TO POST-BUILD ACTIONS IN THE JOB CHANGE NAME OF THE SSH SERVER TO ANSIBLE SERVER

NOW GOT O YOUR ANSIBLE SERVER (CMD)

cd /opt mkdir docker

Change the ownership of the docker directory bu running this command

remove everything from : Exec command apply and save

GO TO ANSIBLE SERVER #cd /opt

#ll

OUTPUT : -rw-rw-r-- 1 ansadmin ansadmin 2868 Mar 22 15:27 webapp.war

================== NOW WE NEED TO INSTALL DOCKER ON THIS ANSIBLE SERVER =======================

NOW ADDING ANSADMIN USER TO THE DOCKER GROUP SO THAT THIS USER WILL BE ABLE TO PERFORM DOCKER OPERATIONS AS WELL.

#cd /opt/docker

================== DOCKERFILE CONTENT =======================

FROM tomcat:latest RUN cp -R /usr/local/tomcat/webapps.dist/* /usr/local/tomcat/webapps COPY ./*.war /usr/local/tomcat/webapps

=============================================================

FROM ANSIBLE INSTRUCT DOCKER GO AND PULL THE IMAGE FROM THE HUB AND CREATE THE CONTAINER. APP IS RUNNING ON THE DOCKER HOST. AND USER CAN ACCESS THE APPLICATION.

#ON ANSIBLE SERVER WE WILL BE CREATING A PLAYBOOK WHICH WILL COPY ARTIFACTS AND RUN THE DOCKERFILE ON TARGET HOST THAT IS ON DOCKER SERVER.

===================================

============================================

• hosts: ansible tasks:
• name: create a docker image command: docker build -t regapp:latest args: chdir: /opt/docker

=============================================

• hosts: ansible

tasks:

• name: create a docker image command: docker build -t regapp:latest . args: chdir: /opt/docker

• name: create tag to push image onto dockerhub command: docker tag regapp:latest vj0555/regapp:latest

• name: puch docker image command: docker push vj0555/regapp:latest

CONFIGURE Copy_Artifacts_onto_Ansible IN JENKINS. GO TO THIS JOB >> CONFIGURE>>>SCROLL DOWN AND LOOK FOR EXEC COMMAND OPTION AND ADD BELOW COMMAND: #ansible-playbook /opt/docker/regapp.yml

SELECT: BUILD TRIGGER >> POLL SCM >>> 5 STARS ***** WILL BUILD EVERY MINUTE BY APPLYING THIS.

NOW GO ON YOUR REPO AND DO SOME CHANGES IN THE CODE. BY DOING THIS IT WILL AUTOMATICALLY TRIGGER JENKINS JOB>>WHICH WILL AUTOMATICALLY CREATE A LATEST DOCKER IMAGE ONTO ANSIBLE SERVER.

GO TO ANSIBLE SERVER: TO CHECK WEATHER LATEST IMAGE IS CREATED OR NOT. #su - ansadmin

=================== NOW WE WILL BE CREATING ANOTHER ANSIBLE PLAYBOOK WHICH WILL PULL AN IMAGE FROM THE HUB AND CREATE A CONTAINER ON THE DOCKER HOST.

GO TO YOUR ANSIBLE SERVER #su - ansadmin

• hosts: dockerhost

tasks:

• name: create container command: docker run -d --name regapp_server -p 8082:8080 vj0555/regapp:latest

==============================================================

NOW GO TO YOUR DOCKER INSTANCE AND REMOVE ALL THE IMAGES AND STOPPED CONTAINERS AS WELL:

NOW GO TO YOUR ANSIBLE SERVER AND TRY TO RUN THE YML FILE. IT WILL THROW AN ERROR IN WHICH WE HAVE TO GET THE PATH: /var/run/docker.sock THEN COPY THAT PATH AND ON DOCKER SERVER GIVE PERMISSION TO THIS LOCATION AS BELOW:

=================

NOW GO TO YOUR ANSIBLE SERVER AND TRY TO RUN THE YML FILE WHICH WE CREATED AGAIN . ++++++++

AGAIN GO TO YOUR DOCKER SERVER AND CHECK FOR THE NEW IMAGES: #docker images #docker ps -a

YOU WILL SEE A IMAGE AND A CONTAINER ON THE DOCKER SERVER.

TAKE THE PUBLIC IP OF THE DOCKER SERVER AND 3.110.161.83:8082/webapp CHECK IT ON THE 8082 PORT YOUR APP WILL BE DEPLOYED SUCCESSFULLY. WE HAVE DONE THIS MANUALLY, NOW WE WILL AUTOMATE THIS TASKS AS WELL WITH THE HELP OF JENKINS.

• hosts: dockerhost

tasks:

• name: create container command: docker run -d --name regapp_server -p 8082:8080 vj0555/regapp:latest ++++++++

• hosts: dockerhost

tasks:

• name:stopexistingcontainer command:dockerstopregapp-server

  • name: removethecontainer command:dockerrmregapp-server

  • name: remove the image command:vj0555/regapp:latest

  • name: create container command: docker run -d --name regapp_server -p 8082:8080 vj0555/regapp:latest

============================================================================

ABOVE COMMAND WILL THROW ERROR, NOW MAKE CHANGES TO YOUR YML FILE AND THEN RUN THESE COMMANDS.

• hosts: dockerhost

tasks:

• name: stop existing container command: docker rm -f regapp_server ignore_errors: yes

• name: remove the container command: docker rm regapp-server ignore_errors: yes

• name: remove the image command: docker rmi vj0555/regapp:latest ignore_errors: yes

• name: create container command: docker run -d --name regapp_server -p 8082:8080 vj0555/regapp:latest

=============

GO TO YOUR DOCKER HOST AND THEN CHECK WEATHER A NEW CONTAINER IS CREATED OR NOT:

NOW WE WILL DO THE ABOVE STEPS USING AUTOMATION USING JENKINS:

GO TO JENKINS SELECT THE JOB AND GO TO >>>CONFIGURE EXEC COMMAND: (EDIT) ansible-playbook /opt/docker/regapp.yml; sleep 10; ansible-playbook /opt/docker/deploy_regapp.yml

===================================KUBERNETES============25/03/2022===================================

NOW OUR APP IS DEPLOYED ON A CONTAINER. BUT WHAT IF THAT CONTAINER FAILS??? kubernetes ceates a new pod in case of any failures. SO, FOR THAT WE ARE USING KUBERNETES FOR THE DEPLOYMENT OF OUR WEBSITE. Elastic Kubernetes Service (Amazon EKS)

PRE-REQUSITE: We will be creating one ec2 instance to setup our kubernetes on amazon eks with the help of AWS CLI

1. AN EC2 INSTANCE.
2. INSTALL AWSCLI LATEST VERSION.

ADD CLUSTER>>CREATE Name:

• Not editable after creation.

Prerequisites

Before starting this tutorial, you must install and configure the following tools and resources that you need to create and manage an Amazon EKS cluster.

AWS CLI – A command line tool for working with AWS services, including Amazon EKS. This guide requires that you use version 2.4.9 or later or 1.22.30 or later. For more information, see Installing, updating, and uninstalling the AWS CLI in the AWS Command Line Interface User Guide. After installing the AWS CLI, we recommend that you also configure it. For more information, see Quick configuration with aws configure in the AWS Command Line Interface User Guide.

kubectl – A command line tool for working with Kubernetes clusters. This guide requires that you use version 1.21 or later. For more information, see Installing kubectl.

Required IAM permissions – The IAM security principal that you're using must have permissions to work with Amazon EKS IAM roles and service linked roles, AWS CloudFormation, and a VPC and related resources. For more information, see Actions, resources, and condition keys for Amazon Elastic Kubernetes Service and Using service-linked roles in the IAM User Guide. You must complete all steps in this guide as the same user.

AWS DOC LINK: https://docs.aws.amazon.com/eks/latest/userguide/install-kubectl.html

LAUNCH A NORMAL EC2 INSTANCE PORT: 22 AND 80 REQ

We have to update our aws cli version to work with kube cluster. Follow the steps to update it:

https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html Installing past releases of the AWS CLI version 2: https://docs.aws.amazon.com/cli/latest/userguide/getting-started-version.html https://aws.amazon.com/premiumsupport/knowledge-center/eks-cluster-creation-errors/

curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip" unzip awscliv2.zip sudo ./aws/install

"You can now run: /usr/local/bin/aws --version "

================= curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64-2.0.30.zip" -o "awscliv2.zip" unzip awscliv2.zip sudo ./aws/install /usr/local/bin/aws --version ls -l /usr/local/bin/aws sudo ./aws/install --bin-dir /usr/local/bin --install-dir /usr/local/aws-cli --update =======INSTALLING KUBECTL========== #curl -o kubectl https://amazon-eks.s3.us-west-2.amazonaws.com/1.21.2/2021-07-05/bin/linux/amd64/kubectl

INSTALLING: eksctl

===================NOW CREATING AN IAM ROLE =========

GO TO IAM CONSOLE. CREATE ROLE IAM FULL ACCESS, EC2 FULL ACCESS, CLOUDFORMATION FULL ACCESS. CREATE ROLE ROLE NAME : EKS_CTL_ROLE GO TO EC2 INSTANCE AND ASSIGN THE ROLE CREATED TO THIS INSTANCE. ----->>GO TO ACTIONS>>SECUTY>>EDIT ROLE>>SELECT THE ROLE FROM THE DROPDOWN MENU

======================================================================================================

NOW GO TO GIT HUB REPO : kubernetes_setup_using_eksctl.md

Create your cluster and nodes. Go to cd tmp and run below commands:

======================================================================================================

#cd /tmp

======================================================================================================

DELETE THE CLUSTER: FOR DELETING IT FIRST WE NEED TO DELETE: VPC / SUBNETS ETC IF DOING IT FROM THE CONSOLE. eksctl delete cluster --name devcluster --region us-east-1 --node-type t2.small

GO TO CLOUDFORMATION TO CHECK IF SOMETHING IS BEING CREATED OR NOT....... THIS PROCESS WILL TAKE ALMOST 20-25 MINUTES TO BE COMPLETED.

AFTER CREATING THE CLUSTER WE NEED TO CHECK IF THE NODES ARE CREATED OR NOT. 2:27 mins lec 46

deployment.apps/demo-nginx created

TO CHECK IF THE DEPLOYMENT IS CREATED OR NOT:

TO CHECK IF REPLICA SET IS CREATED OR NOT

TO DELETE THE PODS:

THIS COMMAND IS USED TO SEE EVERYTHING:

NOW NEED TO EXPOSE THE DEPLOYMENT AS A SERVICE: #kubectl expose deployment demo-nginx --port=80 --type=LoadBalancer

service/demo-nginx exposed

TO GET THE EXTERNAL IP OF LOAD BALANCER SERVICE:

a415e5629ec124dafafc675479515b40-1857107097.us-east-1.elb.amazonaws.com o/p: Welcome to nginx! ALSO CHECK IN THE LOAD BALANCERS TO SEE WETHER IT IS CREATED OR NOT. NOW WE HAVE DONE EVERYTHING MANUALLY. WE WILL RUN IT AUTOMATICALLY BY CREATING A MANIFEST FILE JUST LIKE ANSIBLE PLAYBOOKS.

NOW DELETE THE RESOURCES THAT WE HAVE CREATED MANUALLY. #kubectl delete deployment demo-nginx

TO CHECK

LOAD BALANCER DELETED.

https://kubernetes.io/docs/reference/ select: One-page API Reference for Kubernetes v1.23 select Pod v1 core from the left hand side menu refer the example GOOGLE: "pod manifest file kubernetes" select create link on google page.. look for : Create a static pod

Now create vi pod.yml file and below content in yml file. CREATE FIRST MANIFEST FILE. ==================================== vi pod.yml =============================== kind: Pod metadata: name: demo-pod labels: app:demo-app

spec: containers:

• name: web image: nginx ports:
• name: web containerPort: 80 ================================================================================================ NOW WE WILL BE CREATING SERVICE USING MANIFEST GOOGLE IT: service manifest file kubernetes SELECT: Service | Kubernetes Defining a Service :

apiVersion: v1 kind: Service metadata: name: demo-service

spec: ports:

• name: nginx-port
  port: 80 targetPort: 80

type: LoadBalancer

apiVersion: v1 kind: Pod metadata: name: demo-pod

spec: containers: - name: web image: nginx ports:

• name: web containerPort: 80

TO RUN POD.YML USE BELOW COMMAND IT WILL CREATE YOUR POD

#kubectl get pods #kubectl apply -f service.yml

service/demo-service created

O/P: NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/demo-service LoadBalancer 10.100.163.5 a5630d4fa22d34a88a301409238aecaf-967050777.us-east-1.elb.amazonaws.com 80:32588/TCP 25s service/kubernetes ClusterIP 10.100.0.1 443/TCP 122m

USING LABELS AND SELECTOR: LECTURE 49

IF WE CHECK OUR WEBSITE ON BROWSER WITH THE HELP OF ALB ENDPOINT WE WILL NOT BE ABLE TO SEE OUR APP BECAUSE WE HAVE COMMENTED THE LABELS. IN REAL SCENARIO THERE CAN BE SEVERAL PODS. HOW WILL SERVICE DECIDE WHICH POD IT HAS TO SEND THE TRAFFIC. SO FOR SENDING TRAFFIC TO A PARTICULAR POD WE NEED TO GIVE THEM LABELS.

POD CREATED AND CREATED SERVICE IN LAST STEPS.

NOW WE WILL HAVE TO UPDATE THE POD.YML FILE. UN-COMMENT THE 2 LINES WE HAVE COMMENTED IN THE EARLIER STEPS. (LABELS)

apiVersion: v1 kind: Service metadata: name: demo-service

spec: ports:

• name: nginx-port port: 80 targetPort: 80

selector: {changed part} app: demo-app type: LoadBalancer

=========

To update the POD.YML FILE

pod/demo-pod configured

To update the service.yml file service/demo-service configured

{TO KNOW THE IP OF A POD RUN BELOW COMMAND}:

TO KNOW ALL THE INFO ABOUT THE SERVICE WE HAVE CREATED RUN BELOW COMMAND:

RUN THIS ON THE BROWSER: a5630d4fa22d34a88a301409238aecaf-967050777.us-east-1.elb.amazonaws.com

THE APP SHOULD BE VISIBLE ON THE PAGE NOW:

{ Welcome to nginx!

If you see this page, the nginx web server is successfully installed and working. Further configuration is required.

For online documentation and support please refer to nginx.org. Commercial support is available at nginx.com.

Thank you for using nginx. }

LECTURE 50: WRITE A DEPLOYMENT FILE NOW WE ARE DELETING OUR PODS and services BY RUNNING BELOW COMMAND:

O/P: pod "demo-pod" deleted

VALIDATE YOUR YML FILE: https://onlineyamltools.com/validate-yaml

apiVersion: apps/v1 kind: Service

metadata: name: vj0555-service labels: app: regapp spec: selector: app: regapp

ports: port: 8080 targetPort: 8080 type: LoadBalancer

----------------LECTURE 51-------------------------

------=============================== BELOW YML FILE WAS NOT RUNNING SO CHANGED THE VERSION: https://stackoverflow.com/questions/62108860/kubectl-no-matches-for-kind-service-in-version-apps-v1 --------===============================------- apiVersion: v1
kind: Service

metadata: name: vj0555-service labels: app: regapp spec: selector: app: regapp

ports:

• port: 8080 targetPort: 8080

#YOU WILL SEE 3 PODS ARE RUNNING AS WE MENTIONED IN THE DEPLOYMENT FILE. NOW WE WILL BE DELETING ONE PPOD MANUALLY.

AND NOW IF WE CHECK USING BELOW COMMAND

#WE WILL SEE THt there are still three pods running. because after deleting one pod. another pod is created automatically as we mentioned in the file.

LECT: 52 NOW WE WILL INTEGRATE THIS WITH JENKINS AND ANSIBLE.

HOW TO INEGRATE KUBE CLUSTER WITH ANSIBLE:

CREATE AND ADMINUSER ADD ANSADMIN USER TO SUDOERS FILE ENABLE PASROD BASED LOGIN ON ANSIBLE NODE: ADD TO HOSTS FILE COPY SSH KEYS TEST THE CONNECTION ONCE THIS IS DONE WE WILL BE WRITING THE ANSIBLE PLAYBOOK . NOW, GO TO THE BOOTSTRAP SERVER AND ADD THE ANSADMIN USER

EDIT THIS SECTION IN THAT FILE: AND :WQ

root ALL=(ALL)ALL ansadminALL=(ALL) ALL

#PasswordAuthentication no #PermitEmptyPasswords no PasswordAuthentication yes

NOW GO TO YOUR ANSIBLE SERVER:

You will see the changes here. NOW RENAME ANOTHER FILE.

NOW GOT TO THE ANSIBLE SERVER AND MAKE SURE YOU ARE LOGGED IN AS A ROOT USER NOT ANS ADMIN USER. WE WILL NOW EDIT THE FILE.

NOW ADD THE KUBERNETES GROUP, WITH IT'S PRIVATE IP: [kubenetes] 172.31.34.193 :wq

ANSIBLE SERVER:

NOW TRY TO LOGIN INTO KUBERNETES SERVER VIA ANSIBLE SERVER:

NOW TO CHECK THE CONNECTION WE NEED TO RUN THE BELOW COMMAND:

O/P: (THREE IP'S SHOULD SHOW UP HERE) ONLY 2 IPS WERE SHOWING UP EARLIER BECAUSE OUR DOCKER SERVER WAS STOPPED. ONCE WE STARTED THE SERVER ALL THREE SHOWED UP.

LEC:53 EXECUTE DEP AND SERVICE FILES USING ANSIBLE. LOGIN TO ANSIBLE SERVER. LOGIN VIA ANSADMIN.

• hosts:kubernetes user: root

  tasks:

  • name: deployregapponkubernetes command: kubectlapply -f regapp-deployment.yml ~

• hosts:kubernetes user: root

  tasks:

  • name: deployregapponkubernetes command: kubectlapply -f regapp-service.yml ~
    ===================================================================================== NOW DELETE THE RESOURCES CREATED PREVIOUSLY ON EKS_BOOTSTRAP_SERVER #cd /tmp

On EKS_Server move all the .yml files from /tmp to root with the help of following commands #mv <.yml> ~

Now, Run the playbooks to build resources #ansible-playbook -i /opt/docker/hosts kube_deploy.yml

it will create all the pods and deployment on eks server

it will create service on eks server =====================================================================================

NOW WE ARE CREATING JENKINS DEPLOYMENT JOB FOR KUBERNETES:

DEPLOYING AS APOD. USING JENKINS NOW RATHER THAN USING ANSIBLE FOR RUNNING THE PLAYBOOKS.

JUMP IN TO YOUR JENKINS SERVER.

CREATE NEW NAME: Deploy_On_kubernetes Select free style job. Got to Post build action. select : send files or execute commands over SSH NAME: ANSIBLE SERVER EXEC COMMANDS: cd /opt/docker; ansible-playbook kube_deploy.yml ansible-playbook -i /opt/docker/hosts kube_deploy.yml; ansible-playbook -i /opt/docker/hosts kube_service.yml APPLY AND SAVE

GOT TO KUBE SERVER kubectl delete deployment.apps/vj0555-regapp TO DELETE THE RESOURCES.

NOW DELETE THE SERVICE: kubectl delete service/vj0555-service

=====================================================================================