Introduction about the all tools
What is Git?
Git is a free, open-source version control system (VCS) that helps developers manage their code. It's the most widely used tool VCS(version control system) Git is fast for committing, branching, merging, and comparing past versions Git is very high Performance and Flexibility,Security
Install Git in you local machine
https://git-scm.com/downloads/win
Please download the ---64-bit Git for Windows Setup.
Once download the git .exe file , double click and install the git on your machine
once installed right click on your local machine you can found Open Git batch here option, means git is installed successfully in your machine
GitHub account creation:: for creating github account EmailId is Required
go to link --https://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F&source=header-home
Enter Email & password ,Username click continue ---Account will create successfully image
Github::Github is a one of the SCM(Source code management) tool and store the Project code.
Repository: storage area of your source code. Create a Repository on GitHub
click Repositories
Enter Repository Name::
Public:: Anyone on the internet can see this repository.
Private:: You choose who can see and commit to this repository.
Click Create Repository
Repository Created SUccessfully with Default branch main
GitHub is a web-based platform for version control and collaboration, allowing developers to store and manage their code in repositories.
Version Control: :: GitHub uses Git, a distributed version control system, to track changes in code. This allows multiple people to work on the same project without overwriting each other's contributions.
Repositories::: where you can store your project files and track the history of changes made to those files.Public and private repos can be created depending on accessibility needs.
git commands::
---git clone
git status
git add --all
git commit -m "added some text files to Readmefile"
git push
if we get any Access denied issues during push the changes from local to remote repository,please be authenticate below commands
git config --global user.name "srinfotech7358"
git config --global user.email "srinfotechbatch1@gmail.com"
syntax::ssh-keygen -t ed25519 -C "your_email@example.com"
ssh-keygen -t ed25519 -C "srinfotechbatch1@gmail.com"
Keys avaibale path and save the key (/c/Users/HP/.ssh/id_ed25519):
Please follow below links for more understanding
https://docs.github.com/en/authentication/connecting-to-github-with-ssh
Once genearted the keys (public/private) and copy public key to Github Account
Go to -->settings
Click SSH and GPG Keys
click New SSH Key
Add new SSH Key and click Add SSH Key
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1
$ git clone git@github.com:srinfotech7358/AWSDevOps.git Cloning into 'AWSDevOps'... The authenticity of host 'github.com (20.207.73.82)' can't be established. ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU. This key is not known by any other names. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added 'github.com' (ED25519) to the list of known hosts. remote: Enumerating objects: 3, done. remote: Counting objects: 100% (3/3), done. remote: Total 3 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0) Receiving objects: 100% (3/3), done.
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1
$ cd AWSDevOps/
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1/AWSDevOps (main)
$ git status On branch main Your branch is up to date with 'origin/main'.
Changes not staged for commit: (use "git add ..." to update what will be committed) (use "git restore ..." to discard changes in working directory) modified: README.md
no changes added to commit (use "git add" and/or "git commit -a")
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1/AWSDevOps (main)
$ git add --all
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1/AWSDevOps (main) $ git commit -m "added some text to Readme.md file" [main 95d0d52] added some text to Readme.md file 1 file changed, 3 insertions(+), 1 deletion(-)
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1/AWSDevOps (main)
$ git push Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Writing objects: 100% (3/3), 299 bytes | 149.00 KiB/s, done. Total 3 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0) To github.com:srinfotech7358/AWSDevOps.git e38e1b1..95d0d52 main -> main
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1/AWSDevOps (main)
$ git add --all
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1/AWSDevOps (main)
$ git commit -m "added some text to Readme.md file" [main 8ddd014] added some text to Readme.md file 1 file changed, 3 insertions(+), 1 deletion(-)
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1/AWSDevOps (main)
$ git push Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 4 threads Compressing objects: 100% (2/2), done. Writing objects: 100% (3/3), 311 bytes | 155.00 KiB/s, done. Total 3 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0) To github.com:srinfotech7358/AWSDevOps.git 95d0d52..8ddd014 main -> main
In GitHub, forking is a way to create your own copy of someone else's repository. example please fork below project to your own github account
https://github.com/srinfotech7358/spring-petclinic
Go to Above Project URL
https://github.com/srinfotech7358/spring-petclinic
at top right we can found Fork option in github Account
Click on Fork and click create Fork
Successfully Fork done from someone else's repository
once above steps done ,please clone the Project and Modified files and push to github repository
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1 $ git clone git@github.com:srinfotech7358/spring-petclinic.git Cloning into 'spring-petclinic'... remote: Enumerating objects: 10498, done. remote: Total 10498 (delta 0), reused 0 (delta 0), pack-reused 10498 (from 1) Receiving objects: 100% (10498/10498), 7.68 MiB | 941.00 KiB/s, done. Resolving deltas: 100% (3964/3964), done.
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1 $ cd spring-petclinic/
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1/spring-petclinic (main) $ git status On branch main Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1/spring-petclinic (main) $ git status On branch main Your branch is up to date with 'origin/main'.
Changes not staged for commit: (use "git add ..." to update what will be committed) (use "git restore ..." to discard changes in working directory) modified: pom.xml
no changes added to commit (use "git add" and/or "git commit -a")
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1/spring-petclinic (main) $ git add --all
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1/spring-petclinic (main) $ git status On branch main Your branch is up to date with 'origin/main'.
Changes to be committed: (use "git restore --staged ..." to unstage) modified: pom.xml
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1/spring-petclinic (main) $ git commit -m "modified pom.xml file" [main f2ef175] modified pom.xml file 1 file changed, 2 insertions(+)
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1/spring-petclinic (main) $ git push Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 4 threads Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 325 bytes | 325.00 KiB/s, done. Total 3 (delta 2), reused 0 (delta 0), pack-reused 0 (from 0) remote: Resolving deltas: 100% (2/2), completed with 2 local objects. To github.com:srinfotech7358/spring-petclinic.git 0c88f91..f2ef175 main -> main
HP@DESKTOP-E518Q66 MINGW64 ~/Downloads/SR Infotech Batch1/spring-petclinic (main) $
A GitHub branching strategy is crucial for maintaining an organized workflow in version control. There are different strategies depending on the size of the project, the number of team members, and the desired workflow. Here are some common branching strategies used in GitHub:
main or master branch:: This is default branch and whenever we created the empty Repository by defauly main or master branche is created automatically. main or master branch always stable and live code
feature branch:: It could be a new feature, an improvement of existing features, bug fixes, or any other changes. A feature branch is a type of branch in Git typically used to develop new features for the software.feature branch will created from main or master OR feature branch created from latest release branch always based on the release cycle
formate:: feature/YYYY.MM.DD feature/2025.03.17
release branch:: Based on the release we have created release branch accourdingly and starts the next release cycle. always release branch created from master only and master have stable and live code and post release we shold merged code changes to master branch only
release/2025.03.17
hotfix branch:: always created from main or master branch only for production fixes.once production fix done we should merged directly to main or master branch only.
always created this hotfix branch for production issues fixes
bugfix:: this branch is created from release branch to fix the LLE(lower level environemnt)/Pre-Prod/UAT/Non-Prod issues and once LLE issues fixed ,we should pushed their changes to release branch only.
cloning references::
Generate SSHKeys::
syntax::ssh-keygen -t ed25519 -C "your_email@example.com"
Keys avaibale path and save the key (/c/Users/HP/.ssh/id_ed25519):
Please follow below links for more understanding
https://docs.github.com/en/authentication/connecting-to-github-with-ssh
Once genearted the keys (public/private) and copy public key to Github Account
Go to -->settings
Click SSH and GPG Keys
click New SSH Key
Add new SSH Key and click Add SSH Key
git clone git@github.com:ifocusbatch2/spring-petclinic.git
HP@DESKTOP-E518Q66 MINGW64 ~/Desktop/Ifocus/batch2_17 $ git clone git@github.com:ifocusbatch2/spring-petclinic.git Cloning into 'spring-petclinic'... The authenticity of host 'github.com (20.207.73.82)' can't be established. ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU. This key is not known by any other names. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added 'github.com' (ED25519) to the list of known hosts. remote: Enumerating objects: 10430, done. remote: Total 10430 (delta 0), reused 0 (delta 0), pack-reused 10430 (from 1) Receiving objects: 100% (10430/10430), 7.67 MiB | 1.17 MiB/s, done. Resolving deltas: 100% (3935/3935), done.
HP@DESKTOP-E518Q66 MINGW64 ~/Desktop/Ifocus/batch2_17 $ cd spring-petclinic/
HP@DESKTOP-E518Q66 MINGW64 ~/Desktop/Ifocus/batch2_17/spring-petclinic (main) $ git status On branch main Your branch is up to date with 'origin/main'.
Changes not staged for commit: (use "git add ..." to update what will be committed) (use "git restore ..." to discard changes in working directory) modified: pom.xml
no changes added to commit (use "git add" and/or "git commit -a")
HP@DESKTOP-E518Q66 MINGW64 ~/Desktop/Ifocus/batch2_17/spring-petclinic (main) $ git add --all
HP@DESKTOP-E518Q66 MINGW64 ~/Desktop/Ifocus/batch2_17/spring-petclinic (main) $ git commit -m "updated pom.xml file" [main b2e46bf] updated pom.xml file 1 file changed, 1 insertion(+), 1 deletion(-)
HP@DESKTOP-E518Q66 MINGW64 ~/Desktop/Ifocus/batch2_17/spring-petclinic (main) $ git push Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 4 threads Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 340 bytes | 340.00 KiB/s, done. Total 3 (delta 2), reused 0 (delta 0), pack-reused 0 (from 0) remote: Resolving deltas: 100% (2/2), completed with 2 local objects. To github.com:ifocusbatch2/spring-petclinic.git 2aa53f9..b2e46bf main -> main
HP@DESKTOP-E518Q66 MINGW64 ~/Desktop/Ifocus/batch2_17/spring-petclinic (main) $ git checkout -b feature/2025.03.17 Switched to a new branch 'feature/2025.03.17'
HP@DESKTOP-E518Q66 MINGW64 ~/Desktop/Ifocus/batch2_17/spring-petclinic (feature/2025.03.17) $ git status On branch feature/2025.03.17 Changes not staged for commit: (use "git add ..." to update what will be committed) (use "git restore ..." to discard changes in working directory) modified: pom.xml
no changes added to commit (use "git add" and/or "git commit -a")
HP@DESKTOP-E518Q66 MINGW64 ~/Desktop/Ifocus/batch2_17/spring-petclinic (feature/2025.03.17) $ git add --all
HP@DESKTOP-E518Q66 MINGW64 ~/Desktop/Ifocus/batch2_17/spring-petclinic (feature/2025.03.17) $ git status On branch feature/2025.03.17 Changes to be committed: (use "git restore --staged ..." to unstage) modified: pom.xml
HP@DESKTOP-E518Q66 MINGW64 ~/Desktop/Ifocus/batch2_17/spring-petclinic (feature/2025.03.17) $ git commit -m "added branch" [feature/2025.03.17 f393310] added branch 1 file changed, 1 insertion(+), 1 deletion(-)
HP@DESKTOP-E518Q66 MINGW64 ~/Desktop/Ifocus/batch2_17/spring-petclinic (feature/2025.03.17) $ git push fatal: The current branch feature/2025.03.17 has no upstream branch. To push the current branch and set the remote as upstream, use
git push --set-upstream origin feature/2025.03.17 To have this happen automatically for branches without a tracking upstream, see 'push.autoSetupRemote' in 'git help config'.
HP@DESKTOP-E518Q66 MINGW64 ~/Desktop/Ifocus/batch2_17/spring-petclinic (feature/2025.03.17) $ git push origin feature/2025.03.17 Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 4 threads Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 302 bytes | 302.00 KiB/s, done. Total 3 (delta 2), reused 0 (delta 0), pack-reused 0 (from 0) remote: Resolving deltas: 100% (2/2), completed with 2 local objects. remote: remote: Create a pull request for 'feature/2025.03.17' on GitHub by visiting: remote: https://github.com/ifocusbatch2/spring-petclinic/pull/new/feature/2025.03.17 remote: To github.com:ifocusbatch2/spring-petclinic.git
- [new branch] feature/2025.03.17 -> feature/2025.03.17
Merge the code from one branch to another branch that is called pull request
below are the steps to raise PR::
Go to -->Pull requests and click
Click New Pull Request::
please select base & compare branches so here base branch is release/2025.02.25 and compare branch is feature/2025.02.25
i'm going to merge code changes from feature branch to release branch
click create pull request
parasa7358 wants to merge 1 commit into release/2025.02.25 from feature/2025.02.25
click merge request
confirm merge
Merged
Jenkins is a free and open source automation server/tool. It helps automate the parts of software development related to building, testing, and deploying, facilitating continuous integration and continuous delivery.
Jenkins is a Orchestration tool
Jenkins is a CI/CD tool
Jenkins is a Schedular
Jenkins is a crone job schedular
LLE/Pre-prod/UAT/PROD ---automatically ---contunutineus deployemt
LLE/Pre-prod/UAT /PROD ---Manually ---contunutineus delivery
1)The devops engineer was responsibility to release the product to the market as soon as possible 2)release the product speed to the market 3)Devops engineer was give continues feedback to the developers 4) Devops engineer responsibility start from git and end with production
A) when your activity start from git and end with production environment(production servers)Continues deployment when your activity start from git to LLE(lower level environment,testing environment,pre-prod…et) environment(pre-production servers)Continues delivery non-production environment
Tutorials::
https://www.tutorialspoint.com/jenkins/jenkins_overview.htm https://www.geeksforgeeks.org/jenkins-tutorial/#prerequisites
Download JDK 17 ::
https://www.oracle.com/java/technologies/javase/jdk17-archive-downloads.html
Windows x64 Installer 153.92 MB
https://download.oracle.com/java/17/archive/jdk-17.0.12_windows-x64_bin.exe (sha256 )
OR
Windows x64 Compressed Archive 172.87 MB
https://download.oracle.com/java/17/archive/jdk-17.0.12_windows-x64_bin.zip (sha256 )
Download Maven::
https://maven.apache.org/download.cgi
Source zip archive apache-maven-3.9.9-src.zip
====================
JDK 17 Environment setup::
Go to Search box & type Edit the system environemnt variables and click
It will navigate to System properties
Open Environemnt Variables
User variables::
JAVA_HOME=C:\Users\HP\Downloads\jdk-17.0.12_windows-x64_bin\jdk-17.0.12
System variable::
%JAVA_HOME%\bin
%MAVEN_HOME%\bin
Maven setup::
MAVEN_HOME=C:\Users\HP\Downloads\apache-maven-3.9.9-bin\apache-maven-3.9.9
Download link
https://maven.apache.org/download.cgi
Make sure we should setup the path at system variable
JAVA_HOME & MAVEN_HOME
now verify the java version & maven version:: go to git bash and verify. below are refreenced screenshots
java -version
mvn -v
once above setup is ready then we will proceed to installe jenkins
================
Installed jenkins in Windows::
https://www.jenkins.io/download/
Go to google search -->download jenkins war file for windows
Click --->WAR file link
Please follow the below link steps to installed jenkins in your windows machines
https://www.jenkins.io/doc/book/installing/war-file/
Steps::
https://www.jenkins.io/download/
-
First download the jenkins.war file and right click -->open gitbash here
-
run the command -->java -jar jenkins.war --httpPort=9090
Browse to http://localhost:9090 and wait until the Unlock Jenkins page appears
Installed the default suggested plugins
click on continue
Need to create jenkins user profile
USER Name--->admin (any name you can provide)
PASSWORD -->admin (any password as your wish but make sure you should remembered the these credentials)
Steps::
1.first we need to create New repository in Github
2.please Clone the Empty Repositoy in your local system
3.copy the Spring-petclinic project code to in your repository
4.once done we need to push project code to github repository
- we need to integarte Github to Jenkins
we need to create Sample demo Project in Jenkins
Click New Item
Configuration stages::
1.General
2.Source code management (SCM)
3.Triggres
4.Environment
5.Build Steps
6.Post Build Actions
General Section provide the Project/job description
At SCM stage level select the Git and provide the github details
Branches to build
Build steps::select the Invoke top-level Maven targets Goals section
mvn clean install
Maven goals::
mvn test
mvn install
mvn clean install
mvn clean
mvn package
Job will be created
Click Build Now
Buils is Inprogress
LAB:::
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2 $ git clone git@github.com:srinfotech7358/SR-Infotech-Demo.git Cloning into 'SR-Infotech-Demo'... remote: Enumerating objects: 3, done. remote: Counting objects: 100% (3/3), done. remote: Total 3 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0) Receiving objects: 100% (3/3), done.
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2 $ cd SR-Infotech-Demo/
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2/SR-Infotech-Demo (main) $ git checkout feature/2025.05.15 branch 'feature/2025.05.15' set up to track 'origin/feature/2025.05.15'. Switched to a new branch 'feature/2025.05.15'
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2/SR-Infotech-Demo (feature/2025.05.15) $ git status On branch feature/2025.05.15 Your branch is up to date with 'origin/feature/2025.05.15'.
Untracked files: (use "git add ..." to include in what will be committed) spring-petclinic/
nothing added to commit but untracked files present (use "git add" to track)
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2/SR-Infotech-Demo (feature/2025.05.15) $ git add --all warning: adding embedded git repository: spring-petclinic hint: You've added another git repository inside your current repository. hint: Clones of the outer repository will not contain the contents of hint: the embedded repository and will not know how to obtain it. hint: If you meant to add a submodule, use: hint: hint: git submodule add spring-petclinic hint: hint: If you added this path by mistake, you can remove it from the hint: index with: hint: hint: git rm --cached spring-petclinic hint: hint: See "git help submodule" for more information. hint: Disable this message with "git config set advice.addEmbeddedRepo false"
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2/SR-Infotech-Demo (feature/2025.05.15) $ git status On branch feature/2025.05.15 Your branch is up to date with 'origin/feature/2025.05.15'.
Changes to be committed: (use "git restore --staged ..." to unstage) new file: spring-petclinic
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2/SR-Infotech-Demo (feature/2025.05.15) $ git commit -m "i have added new spring petclinic project" [feature/2025.05.15 30a148c] i have added new spring petclinic project 1 file changed, 1 insertion(+) create mode 160000 spring-petclinic
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2/SR-Infotech-Demo (feature/2025.05.15) $ git push Enumerating objects: 3, done. Counting objects: 100% (3/3), done. Delta compression using up to 4 threads Compressing objects: 100% (2/2), done. Writing objects: 100% (2/2), 299 bytes | 9.00 KiB/s, done. Total 2 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0) To github.com:srinfotech7358/SR-Infotech-Demo.git 1a61c37..30a148c feature/2025.05.15 -> feature/2025.05.15
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2/SR-Infotech-Demo (feature/2025.05.15) $ git status On branch feature/2025.05.15 Your branch is up to date with 'origin/feature/2025.05.15'.
Changes not staged for commit: (use "git add/rm ..." to update what will be committed) (use "git restore ..." to discard changes in working directory) deleted: spring-petclinic
no changes added to commit (use "git add" and/or "git commit -a")
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2/SR-Infotech-Demo (feature/2025.05.15) $ git add --all
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2/SR-Infotech-Demo (feature/2025.05.15) $ git commit -m "i have added new spring petclinic project" [feature/2025.05.15 b7e6d86] i have added new spring petclinic project 1 file changed, 1 deletion(-) delete mode 160000 spring-petclinic
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2/SR-Infotech-Demo (feature/2025.05.15) $ git push Enumerating objects: 3, done. Counting objects: 100% (3/3), done. Delta compression using up to 4 threads Compressing objects: 100% (1/1), done. Writing objects: 100% (2/2), 255 bytes | 51.00 KiB/s, done. Total 2 (delta 0), reused 1 (delta 0), pack-reused 0 (from 0) To github.com:srinfotech7358/SR-Infotech-Demo.git 30a148c..b7e6d86 feature/2025.05.15 -> feature/2025.05.15
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2/SR-Infotech-Demo (feature/2025.05.15) $ git add --all
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2/SR-Infotech-Demo (feature/2025.05.15) $ git commit -m "i have added new spring petclinic project" [feature/2025.05.15 b53fcd4] i have added new spring petclinic project 124 files changed, 26870 insertions(+), 1 deletion(-) create mode 100644 .devcontainer/Dockerfile create mode 100644 .devcontainer/devcontainer.json create mode 100644 .editorconfig create mode 100644 .gitattributes create mode 100644 .github/dco.yml create mode 100644 .github/workflows/deploy-and-test-cluster.yml create mode 100644 .github/workflows/gradle-build.yml create mode 100644 .github/workflows/maven-build.yml create mode 100644 .gitignore create mode 100644 .gitpod.yml create mode 100644 .mvn/wrapper/maven-wrapper.properties create mode 100644 LICENSE.txt create mode 100644 build.gradle create mode 100644 docker-compose.yml create mode 100644 gradle/wrapper/gradle-wrapper.jar create mode 100644 gradle/wrapper/gradle-wrapper.properties create mode 100644 gradlew create mode 100644 gradlew.bat create mode 100644 k8s/db.yml create mode 100644 k8s/petclinic.yml create mode 100644 mvnw create mode 100644 mvnw.cmd create mode 100644 pom.xml create mode 100644 settings.gradle create mode 100644 src/checkstyle/nohttp-checkstyle-suppressions.xml create mode 100644 src/checkstyle/nohttp-checkstyle.xml create mode 100644 src/main/java/org/springframework/samples/petclinic/PetClinicApplication.java create mode 100644 src/main/java/org/springframework/samples/petclinic/PetClinicRuntimeHints.java create mode 100644 src/main/java/org/springframework/samples/petclinic/model/BaseEntity.java create mode 100644 src/main/java/org/springframework/samples/petclinic/model/NamedEntity.java create mode 100644 src/main/java/org/springframework/samples/petclinic/model/Person.java create mode 100644 src/main/java/org/springframework/samples/petclinic/model/package-info.java create mode 100644 src/main/java/org/springframework/samples/petclinic/owner/Owner.java create mode 100644 src/main/java/org/springframework/samples/petclinic/owner/OwnerController.java create mode 100644 src/main/java/org/springframework/samples/petclinic/owner/OwnerRepository.java create mode 100644 src/main/java/org/springframework/samples/petclinic/owner/Pet.java create mode 100644 src/main/java/org/springframework/samples/petclinic/owner/PetController.java create mode 100644 src/main/java/org/springframework/samples/petclinic/owner/PetType.java create mode 100644 src/main/java/org/springframework/samples/petclinic/owner/PetTypeFormatter.java create mode 100644 src/main/java/org/springframework/samples/petclinic/owner/PetValidator.java create mode 100644 src/main/java/org/springframework/samples/petclinic/owner/Visit.java create mode 100644 src/main/java/org/springframework/samples/petclinic/owner/VisitController.java create mode 100644 src/main/java/org/springframework/samples/petclinic/system/CacheConfiguration.java create mode 100644 src/main/java/org/springframework/samples/petclinic/system/CrashController.java create mode 100644 src/main/java/org/springframework/samples/petclinic/system/WebConfiguration.java create mode 100644 src/main/java/org/springframework/samples/petclinic/system/WelcomeController.java create mode 100644 src/main/java/org/springframework/samples/petclinic/vet/Specialty.java create mode 100644 src/main/java/org/springframework/samples/petclinic/vet/Vet.java create mode 100644 src/main/java/org/springframework/samples/petclinic/vet/VetController.java create mode 100644 src/main/java/org/springframework/samples/petclinic/vet/VetRepository.java create mode 100644 src/main/java/org/springframework/samples/petclinic/vet/Vets.java create mode 100644 src/main/resources/application-mysql.properties create mode 100644 src/main/resources/application-postgres.properties create mode 100644 src/main/resources/application.properties create mode 100644 src/main/resources/banner.txt create mode 100644 src/main/resources/db/h2/data.sql create mode 100644 src/main/resources/db/h2/schema.sql create mode 100644 src/main/resources/db/hsqldb/data.sql create mode 100644 src/main/resources/db/hsqldb/schema.sql create mode 100644 src/main/resources/db/mysql/data.sql create mode 100644 src/main/resources/db/mysql/petclinic_db_setup_mysql.txt create mode 100644 src/main/resources/db/mysql/schema.sql create mode 100644 src/main/resources/db/mysql/user.sql create mode 100644 src/main/resources/db/postgres/data.sql create mode 100644 src/main/resources/db/postgres/petclinic_db_setup_postgres.txt create mode 100644 src/main/resources/db/postgres/schema.sql create mode 100644 src/main/resources/messages/messages.properties create mode 100644 src/main/resources/messages/messages_de.properties create mode 100644 src/main/resources/messages/messages_en.properties create mode 100644 src/main/resources/messages/messages_es.properties create mode 100644 src/main/resources/messages/messages_fa.properties create mode 100644 src/main/resources/messages/messages_ko.properties create mode 100644 src/main/resources/messages/messages_pt.properties create mode 100644 src/main/resources/messages/messages_ru.properties create mode 100644 src/main/resources/messages/messages_tr.properties create mode 100644 src/main/resources/static/resources/css/petclinic.css create mode 100644 src/main/resources/static/resources/fonts/montserrat-webfont.eot create mode 100644 src/main/resources/static/resources/fonts/montserrat-webfont.svg create mode 100644 src/main/resources/static/resources/fonts/montserrat-webfont.ttf create mode 100644 src/main/resources/static/resources/fonts/montserrat-webfont.woff create mode 100644 src/main/resources/static/resources/fonts/varela_round-webfont.eot create mode 100644 src/main/resources/static/resources/fonts/varela_round-webfont.svg create mode 100644 src/main/resources/static/resources/fonts/varela_round-webfont.ttf create mode 100644 src/main/resources/static/resources/fonts/varela_round-webfont.woff create mode 100644 src/main/resources/static/resources/images/favicon.png create mode 100644 src/main/resources/static/resources/images/pets.png create mode 100644 src/main/resources/static/resources/images/spring-logo-dataflow-mobile.png create mode 100644 src/main/resources/static/resources/images/spring-logo-dataflow.png create mode 100644 src/main/resources/static/resources/images/spring-logo.svg create mode 100644 src/main/resources/templates/error.html create mode 100644 src/main/resources/templates/fragments/inputField.html create mode 100644 src/main/resources/templates/fragments/layout.html create mode 100644 src/main/resources/templates/fragments/selectField.html create mode 100644 src/main/resources/templates/owners/createOrUpdateOwnerForm.html create mode 100644 src/main/resources/templates/owners/findOwners.html create mode 100644 src/main/resources/templates/owners/ownerDetails.html create mode 100644 src/main/resources/templates/owners/ownersList.html create mode 100644 src/main/resources/templates/pets/createOrUpdatePetForm.html create mode 100644 src/main/resources/templates/pets/createOrUpdateVisitForm.html create mode 100644 src/main/resources/templates/vets/vetList.html create mode 100644 src/main/resources/templates/welcome.html create mode 100644 src/main/scss/header.scss create mode 100644 src/main/scss/petclinic.scss create mode 100644 src/main/scss/responsive.scss create mode 100644 src/main/scss/typography.scss create mode 100644 src/test/java/org/springframework/samples/petclinic/MySqlIntegrationTests.java create mode 100644 src/test/java/org/springframework/samples/petclinic/MysqlTestApplication.java create mode 100644 src/test/java/org/springframework/samples/petclinic/PetClinicIntegrationTests.java create mode 100644 src/test/java/org/springframework/samples/petclinic/PostgresIntegrationTests.java create mode 100644 src/test/java/org/springframework/samples/petclinic/model/ValidatorTests.java create mode 100644 src/test/java/org/springframework/samples/petclinic/owner/OwnerControllerTests.java create mode 100644 src/test/java/org/springframework/samples/petclinic/owner/PetControllerTests.java create mode 100644 src/test/java/org/springframework/samples/petclinic/owner/PetTypeFormatterTests.java create mode 100644 src/test/java/org/springframework/samples/petclinic/owner/PetValidatorTests.java create mode 100644 src/test/java/org/springframework/samples/petclinic/owner/VisitControllerTests.java create mode 100644 src/test/java/org/springframework/samples/petclinic/service/ClinicServiceTests.java create mode 100644 src/test/java/org/springframework/samples/petclinic/service/EntityUtils.java create mode 100644 src/test/java/org/springframework/samples/petclinic/system/CrashControllerIntegrationTests.java create mode 100644 src/test/java/org/springframework/samples/petclinic/system/CrashControllerTests.java create mode 100644 src/test/java/org/springframework/samples/petclinic/system/I18nPropertiesSyncTest.java create mode 100644 src/test/java/org/springframework/samples/petclinic/vet/VetControllerTests.java create mode 100644 src/test/java/org/springframework/samples/petclinic/vet/VetTests.java create mode 100644 src/test/jmeter/petclinic_test_plan.jmx
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2/SR-Infotech-Demo (feature/2025.05.15) $ git push Enumerating objects: 178, done. Counting objects: 100% (178/178), done. Delta compression using up to 4 threads Compressing objects: 100% (160/160), done. Writing objects: 100% (176/176), 455.71 KiB | 1.29 MiB/s, done. Total 176 (delta 30), reused 0 (delta 0), pack-reused 0 (from 0) remote: Resolving deltas: 100% (30/30), done. To github.com:srinfotech7358/SR-Infotech-Demo.git b7e6d86..b53fcd4 feature/2025.05.15 -> feature/2025.05.15
HP@DESKTOP-E518Q66 MINGW64 ~/OneDrive/Documents/SR inoftech Batch2/SR-Infotech-Demo (feature/2025.05.15) $
Poll SCM ::Jenkins server ask git if there is any changes in git server or not, if changes there Jenkins server build/package the changes , every change build happened like 5 mints ,means every 5 minutes verify the Jenkins server to git if there is any changes
POLL SCM ----* * * * * --every minute when every commit
Go to jenkins Dashboard click New Item
Description
Provide the Git URL
Branch buiild
POLL SCM:: * * * * *
every minute build was trigger when new commits happend in github repository
Build Steps::
1.By Default execute the Jenkins build jobs are sequence way,one by one
2.Don’t do 2 projects build parallel this is real time scenario but we can do parallel builds as well one job
Jenkins build parallel setup
Go job ---> configure ----> Generall ---> Execute concurrent builds if necessary
When this option is checked, multiple builds of this project may be executed in parallel. By default, only a single build of a project is executed at a time — any other requests to start building that project will remain in the build queue until the first build is complete.
Here 5 builds execute parallel ,I kept executor is 5 this is same machine
Build Periodically::: H/15 * * * * ----this build happened every 5 minutes without commits ,if changes are commit or not but every 5 mints
build happened in Jenkins
Jenkins offers two options for determining when builds should be discarded:
Build age: discard builds when they reach a certain age; for example, seven days old. Build count: discard the oldest build when a certain number of builds already exist. These two options can be active at the same time, so you can keep builds for 14 days, but only up to a limit of 50 builds, for example. If either limit is exceeded, then any builds beyond that limit will be discarded.
Description
Git url::
Build the branch
every 5 mints build will trigger
Build Periodically::: H/15 * * * * ----this build happened every 5 minutes without commits ,if changes are commit or not but every 5 mints
build happened in Jenkins
click save
SCM::
Where is your project
Build environment::
---all about your workspace folders
Build Triggers::
--whenever code changes --periodic ---script calls
Build steps::
Dev team will tell ,
Post build::
That aim is giving continue feedback to dev team
--send mails --build pass/fail --CI
1.configure system
--number of executors --E-mail notifications --internall org SMTP
We don’t change anything in system level configurations
Post build Action i want to published artifacts & test results
I'm going to created one free style job and configured Post-build Actions
In post build Action select the option Archive the artifacts
target/*.war
In post build Action select the option Publish JUnit test result report for to published the test results
target/surefire-reports/*.xml
ls target
Post build action stage
Select archive the artifact --target/*.jar
Junit test results:: --target/surefire-reports/*.xml
3.For every company will do sequence build on one project this is recommended approach
crone job formate link
https://crontab.guru/examples.html
Run the same job with different inputs without modifying the configuration manually, we can go for Parameterized projects
Go To New Item
Enter Job Name, Free style project and click ok
Enter the description
Select the option This project is parameterised
Click Add Parameter
Select optiions String parameter or choise parameter or boolean parameter you can select the ny options based on your requirement
select string parameter
Select Choise Parameter
choise parameter
Click Save
You Can observed this project is parameterized
Click Build with parameter
select deployment environment
select which versioj you want to deployment like tis you can configured real time parameterized project in jenkins
Click Build
Project-A, Projec -B, Projec - C
Once Project-A build is done, then it will start Project-B build and once Project-B build SUccess then it will start Project-C build ---for this we need to select Add post-build action and select "Build other projects" in drop down and provide Project-B details.
Projec A is (Downstream project is ---Projec B)
Projec B is (UP Stream project is ----Projec A)
Projec C is (downstream project of --Projec B)
i created 3 free style project in jenkins
Github URL::: https://github.com/parasa7358/spring-petclinic.git
Post Build Action , select the option Build Other Project Project-B
Github URL:::https://github.com/parasa7358/onlinebookstore.git
Post Build Action , select the option Build Other Project Project-C
Github URL:::https://github.com/srinfotech7358/shopping-cart
Pipelines Introduction:::
A Jenkins pipeline is a series of automated steps or stages that define the process of continuous integration/continuous delivery (CI/CD) for your code. Jenkins, being a popular open-source automation server, uses pipelines to automate tasks like building, testing, and deploying code.
There are two types of Jenkins pipelines:
-
Declarative Pipeline
-
Scripted Pipeline
-
Declarative Pipeline:: The declarative pipeline syntax is simpler and more structured. It's the recommended style for most users because it's easy to read and maintain
Steps
Click +New Item
Enter the Project Name And Click OK
At General Section Provide the Description
At Definition, We need to select the Pipeline Script
Here's an example of a simple declarative pipeline: Syntax
pipeline{
agent any
stages{
Stage ('Clone'){
steps{
// write code } }
Stage ('Build'){ steps{
// write code } // write code
}
Stage ('Test'){
steps{
// write code } // write code
} Stage ('Execute test casea and get the results'){
steps{
// write code } // write code
}
Stage ('Generated Artifact'){
steps{
// write code } // write code
}
Stage ('Deploy'){
steps{
// write code } // write code
}
// write code
}
}
Please try to create one pipeline job in jenkinsfile and execute the below Declarative pipeline example:;
pipeline {
agent any
stages { stage('Clone') { steps { git branch: 'main', url: 'https://github.com/srinfotech7358/spring-petclinic.git' } } stage('Build') { steps { bat 'mvn clean install' } } stage('Test') { steps { bat 'mvn test' } } stage('Generate Junit Test Results') { steps { junit 'target/surefire-reports/*.xml' } } stage('Generate Artifacts') { steps { archiveArtifacts artifacts: 'target/*.war', followSymlinks: false } } } }
Plugins in Jenkins are essential components that extend its core functionality, allowing you to customize Jenkins to meet specific CI/CD needs. Jenkins has a vast plugin ecosystem that supports building, deploying, and automating software projects across various platforms and tools
Step-by-Step: Log in to Jenkins as an administrator.
Navigate to Manage Jenkins (usually on the left sidebar).
Click on Manage Plugins.
(Image reference from Jenkins documentation)
Go to the Available tab.
Use the search box to find the plugin you want.
Check the box next to the plugin name.
Click:
Pipeline: Stage View Plugin in Jenkins The Pipeline: Stage View plugin is a visualization tool in Jenkins that allows users to see a graphical view of each stage in a pipeline. It provides a real-time and historical overview of pipeline execution per stage, making it easier to debug, monitor, and analyze performance.
Click the Build Now and we can triggered the pipeline
Success all the stages & Steps
pipeline: This is the top-level structure.
agent: Specifies where the pipeline will run, such as on any available agent, a specific node, or a Docker container.
stages: Defines the different steps or stages in the pipeline (e.g., Build, Test, Deploy).
steps: Commands to be executed in each stage.
The scripted pipeline offers more flexibility, but it is less structured and can be harder to maintain. It uses Groovy syntax to define the pipeline.
Here's an example of a scripted pipeline:
node { try { stage('Build') { echo 'Building the application...' // Your build commands here }
stage('Test') { echo 'Running tests...' // Your test commands here } stage('Deploy') { echo 'Deploying the application...' // Your deploy commands here } Please try to create one new jenkins pipeline job and execute below script for Scripted pipeline examples node { stage('Clone') { git branch: 'master', url: 'https://github.com/parasa7358/onlinebookstore.git' } stage('Build') { bat 'mvn package' } stage('Test') { bat 'mvn test' } } node: Represents a Jenkins agent where the pipeline will run.
Both declarative and scripted pipelines are stored as Jenkinsfiles, which you place in your source code repository. This allows you to version control your pipeline and keep it aligned with your application code.
pipeline { agent any
stages { stage('Clone') { steps { git branch: 'main', url: 'git@github.com:parasa7358/spring-petclinic.git' } } stage('Build') { steps { bat 'mvn package' } } stage('Test') { steps { bat 'mvn test' } } stage('Test Results Reports') { steps { junit 'target/surefire-reports/*.xml' } } stage('Artifacts') { steps { archiveArtifacts artifacts: 'target/*.war', followSymlinks: false } } stage('Deploy') { steps { echo 'Hello World' } } } }
This pipeline:::
1 Checks out the source code from your Git repository. 2. Builds the project using Maven. 3.Runs unit tests. 4.Deploys the application using a custom script.
JOb creation::
Branches to build
Script Path::: This path is Jenkinsfiles where we maintained in github source code level
node {
stage('Clone') { git branch: 'main', url: 'git@github.com:parasa7358/spring-petclinic.git' } stage('Build') { bat 'mvn package' } stage('Test') { bat 'mvn test' } stage('Test Results Reports') { junit 'target/surefire-reports/*.xml' } stage('Artifacts') { archiveArtifacts artifacts: 'target/*.war', followSymlinks: false } stage('Deploy') { echo 'Hello World' } } github sourcecode jenkinsfile
Apache Tomcat is an open-source web server and servlet container developed by the Apache Software Foundation. It is primarily used to serve Java applications and is one of the most popular servlet containers in the world.
Tomcat is an essential tool for anyone working with Java web applications. It provides a simple, reliable platform for deploying and managing Java Servlets and JSPs and is widely used in both development and production environments. Its ease of use, combined with powerful features and flexibility, makes it an ideal choice for many developers working on Java-based web applications.
Apache Tomcat is an open-source web server and servlet container that is primarily used to serve Java-based web applications. It implements several Java EE (Enterprise Edition) specifications, such as Java Servlet, JavaServer Pages (JSP), and WebSocket, among others. Tomcat is often used to run Java applications on the web because it's lightweight, easy to configure, and widely supported.
Here are some key points about Tomcat:
-
Servlet Container: Tomcat is a servlet container, meaning it manages the lifecycle of Java Servlets, which are small Java programs that run on a web server.
-
JSP Support: Tomcat also supports JavaServer Pages (JSP), a technology that allows for embedding Java code within HTML pages.
-
Configuration: It’s highly configurable through XML files, like
server.xmlfor server settings,web.xmlfor application settings, and others. -
Lightweight: Unlike full-fledged application servers like WildFly (formerly JBoss) or GlassFish, Tomcat is primarily a servlet and JSP container, which makes it lighter and easier to deploy for simpler Java web applications.
-
Performance: It’s known for good performance in handling static content, making it a popular choice for Java web developers.
https://tomcat.apache.org/download-90.cgi
64-bit Windows zip
after downloaded the tomcat ,we need extrack the all the files
go to bin folder
C:\Users\HP\Downloads\apache-tomcat-9.0.105-windows-x64\apache-tomcat-9.0.105\bin
navigate to CMD--command prompt
run the command
startup.bat
we can find tomcat server started
we can navigate to browser
Integrating Tomcat with Jenkins is a common use case for automating the deployment of Java-based web applications. Jenkins can be set up to deploy a web application to a Tomcat server whenever a new build is triggered.
Prerequisites:
Apache Tomcat should be installed and running on your server. Jenkins should be installed and running.
Steps to integrate Jenkins with Tomcat:
- Install the "Deploy to Container" Plugin in Jenkins: The easiest way to deploy to Tomcat from Jenkins is by using the Deploy to Container plugin. This plugin allows Jenkins to deploy WAR files to a Tomcat server.
Go to your Jenkins dashboard. Click on Manage Jenkins > Manage Plugins. In the Available tab, search for Deploy to Container Plugin and install it. Once installed, restart Jenkins to apply the plugin.
- Configure Tomcat Server in Jenkins: Now you need to tell Jenkins where your Tomcat server is running.
In Jenkins, go to Manage Jenkins > Configure System. Scroll down to the Deploy to container section. Click Add Tomcat Server.
Provide the necessary information: Name: Give the Tomcat server a name (Tomcat9). URL: The URL of your Tomcat server (e.g., http://localhost:8080). Username: The username for Tomcat's manager app (usually admin). Password: The password for that username (set in Tomcat's tomcat-users.xml). Save the configuration.
- Configure Tomcat’s tomcat-users.xml: Make sure Tomcat is set up to allow Jenkins to deploy the application by editing the tomcat-users.xml file.
Restart Tomcat to apply the changes.
- Create a Jenkins Job to Build and Deploy the Application: Next, you need to create a Jenkins job that will build your web application (e.g., a WAR file) and deploy it to Tomcat.
From the Jenkins dashboard, click New Item.
Select Freestyle Project, give it a name, and click OK.
TomcatServer Integrate With Jenkins
In the job configuration, go to the Build section and configure your build step, such as building a Maven project For Maven, you can use:
mvn clean install
In the Post-build Actions section, add Deploy war/ear to a container.
In the WAR/EAR files field, provide the path to your WAR file (e.g., target/*.war). In the Container field, choose the Tomcat server you configured earlier. Set the Context Path (e.g., TomcatIntegartedWithJenkins), which is the URL path where the application will be accessible on Tomcat. If you want Jenkins to deploy automatically after every successful build, check the option Deploy after every successful build.
please use below project to configured Tomcat integration
https://github.com/ifocusbatch2/Petclinic.git
build steps
Post-build Actions
please select Deploy war/ear to a container in drop down
WAR/EAR files::: target/*.war
Context path:::TomcatIntegartedWithJenkins
containers::Tomcat 9.x Remote
please add tomcat credentials username and password
Tomcat URL ::http://localhost:8080/
Save the job.
- Trigger the Build and Deployment: Go to the Jenkins job you just created and click Build Now to trigger a build. After the build completes, Jenkins should deploy the WAR file to your Tomcat server.
build success
[INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 06:16 min [INFO] Finished at: 2025-05-26T11:12:07+05:30 [INFO] ------------------------------------------------------------------------ [DeployPublisher][INFO] Attempting to deploy 1 war file(s) [DeployPublisher][INFO] Deploying C:\Users\HP.jenkins\workspace\TomcatServer Integrate With Jenkins\target\petclinic.war to container Tomcat 9.x Remote with context TomcatIntegartedWithJenkins Redeploying [C:\Users\HP.jenkins\workspace\TomcatServer Integrate With Jenkins\target\petclinic.war] Undeploying [C:\Users\HP.jenkins\workspace\TomcatServer Integrate With Jenkins\target\petclinic.war] Deploying [C:\Users\HP.jenkins\workspace\TomcatServer Integrate With Jenkins\target\petclinic.war] Finished: SUCCESS
Once Build & Deployemnt completed go to Tomcat Server
Click Manager App
You should found /TomcatIntegartedWithJenkins
click /TomcatIntegartedWithJenkins
Spring-petclinic web application up & running
Polling SCM (Source Code Management) and webhooks are two common methods used for integrating continuous integration (CI) systems or automating tasks based on changes in repositories.
- Polling SCM Polling SCM is a method where a system (like Jenkins, GitLab CI, etc.) periodically checks the source code repository for changes. If it detects changes, it triggers the build process or some other automated task.
How it works:
A job is set up to check the SCM (like GitHub, GitLab, Bitbucket, etc.) at regular intervals (e.g., every minute or hour).
The CI server pulls the repository to see if there are any new commits since the last poll.
If changes are detected, it triggers the CI/CD pipeline to build, test, or deploy the application.
- Webhooks Webhooks provide a more efficient method for triggering actions based on changes in the repository. Rather than the CI system polling for changes, the source control platform sends an HTTP POST request (webhook) to the CI system when an event (like a commit or pull request) occurs.
please create one new pipeline job
Provide the Description
Enabled POLL SCM
In Pipeline Section write groovy script using Declarative style
pipeline { agent any
tools{ maven 'maven' } stages{ stage('Git checkout'){
steps{ git branch: 'main' url: 'https://github.com/parasa7358/Petclinic.git' } }
stage('clean and install'){
steps{ sh 'mvn clean install' } }
stage('Package'){
steps{ sh 'mvn package' } }
stage('Archive the Artifacts'){
steps{ sh 'mvn clean install' } post{ success{ archiveArtifacts artifacts: '**target/*.war' } } } stage('Test Cases'){
steps{ sh 'mvn test' } }
stage('Deploy to tomcat server'){
steps{ deploy adapters: [tomcat9(credentialsId: 'tomcat9credentials', path: '', url: 'http://localhost:8080/')], contextPath: 'SRINFOTECH', war: '**/*.war' } }
} }
Run the job
To integrate Jenkins with Tomcat using the Declarative Pipeline approach, you'll be using Jenkins Pipeline syntax to automate the deployment process to a Tomcat server. This process typically involves building the application, packaging it, and then deploying it to Tomcat.
- Jenkinsfile Configuration (Declarative Pipeline)
In your Jenkins project, you'll create a Jenkinsfile, which contains the Declarative Pipeline syntax. This file defines the steps involved in the CI/CD pipeline.
Please execute below script in jenkins pipeline job using Declarative style
pipeline { agent any
tools{ maven 'maven' } stages{ stage('Git checkout'){
steps{ git branch: 'feature/2025.03.12', url: 'https://github.com/parasa7358/Petclinic.git' } }
stage('clean and install'){
steps{ sh 'mvn clean install' } }
stage('Package'){
steps{ sh 'mvn package' } }
stage('Archive the Artifacts'){
steps{ sh 'mvn clean install' } post{ success{ archiveArtifacts artifacts: '**target/*.war' } } } stage('Test Cases'){
steps{ sh 'mvn test' } }
stage('Deploy to tomcat server'){
steps{ deploy adapters: [tomcat9(credentialsId: 'tomcat9credentials', path: '', url: 'http://localhost:8080/')], contextPath: 'SRINFOTECH', war: '**/*.war' } }
} }
Onlinebookstore::
pipeline { agent any
stages { stage('Clone') { steps { git branch: 'master', url: 'https://github.com/srinfotech7358/onlinebookstore.git' } } stage('Build') { steps { bat 'mvn clean install' } } stage('Generate Artifacts') { steps { archiveArtifacts artifacts: 'target/*.war', followSymlinks: false } } stage('Deploy to Tomcat Server') { steps { deploy adapters: [tomcat9(alternativeDeploymentContext: '', credentialsId: 'Tomcat', path: '', url: 'http://localhost:8080')], contextPath: 'SR INFOTECH SOLUTIONS PVT LIMITED', war: 'target/*.war' } } } }
Sonarqube installed link::
https://gist.github.com/dmancloud/0abf6ad0cb16e1bce2e907f457c8fce9
default U/P ---admin/admin
To integrate SonarQube with Jenkins, you need to ensure that Jenkins can communicate with your SonarQube server to perform static code analysis during your CI/CD pipeline. This will allow you to analyze your code quality and get reports from SonarQube as part of your build process.
Here's how you can integrate SonarQube with Jenkins:please follow below steps
- Install the SonarQube Plugin in Jenkins Before you start, ensure that you have the SonarQube Scanner Plugin installed in Jenkins:
Go to Jenkins Dashboard. Click on Manage Jenkins → Plugins. Go to the Available tab, and search for SonarQube Scanner. Install it and restart Jenkins.
- Configure SonarQube in Jenkins Next, you need to configure SonarQube on Jenkins so it can communicate with your SonarQube server.
Go to Jenkins Dashboard. Click on Manage Jenkins → Configure System. Scroll down to the SonarQube servers section and click Add SonarQube.
Name::: Give your SonarQube instance a name (SonarQubeServer). Server URL: URL to your SonarQube instance (e.g., http://localhost:9000). and default port is 9000 Server Authentication Token: You can generate a token in SonarQube by navigating to My Account → Security → Generate Tokens. Paste this token into Jenkins. Click Save.
- Configure the SonarQube Scanner in JenkinsSteps: =============================================== In the Configure System page, scroll to the SonarQube Scanner section. Click Add SonarQube Scanner and select SonarQube Scanner for Jenkins.
If you want to use a custom installation, specify the path to the SonarQube Scanner binary. Click Save.
Go to your SonarQube server (e.g., http://localhost:9000). Create a project or use an existing one. Obtain the Project Key from the SonarQube project and update the pipeline script as shown in the sonar.projectKey parameter.
Go to Projects and click Local project
Click Next
Selected Use the global setting
Click Create Project
Now Spring-petclinic Project created in Sonarqube
Click Locally
Click Generate for Token
Analyze "spring-petclinic12": sqp_0eb364758c5186bea4077eff841ddb99ba89a3ab
Click Continue
Selected Maven and copy below script from sonarqube and it will help to integrate Sonarqube with jenkins pipeline
mvn clean verify sonar:sonar
-Dsonar.projectKey=spring-petclinic12
-Dsonar.projectName='spring-petclinic12'
-Dsonar.host.url=http://localhost:9000
-Dsonar.token=sqp_0eb364758c5186bea4077eff841ddb99ba89a3ab
Go To jenkins and create new job IntegrateSonarqubeWithJenkins
Please use below script to run the pipeline job
pipeline { agent any
tools{ maven 'maven' } stages{ stage('Git checkout'){
steps{ git branch: 'main', url: 'https://github.com/parasa7358/Petclinic.git' } }
stage('clean and install'){
steps{ bat 'mvn clean install' } }
stage('Package'){
steps{ bat 'mvn package' } }
stage('Archive the Artifacts'){
steps{ bat 'mvn clean install' } post{ success{ archiveArtifacts artifacts: '**target/*.war' } } } stage('Test Cases'){
steps{ bat 'mvn test' } }
stage('Sonarqube Analysis'){
steps{ bat 'mvn clean package' bat '''mvn sonar:sonar \ -Dsonar.projectKey=spring-petclinic
-Dsonar.projectName='spring-petclinic'
-Dsonar.host.url=http://localhost:9000
-Dsonar.token=sqp_8d74d659dbf3d3bf2924a0d24104f5ddba914fac'''
} }
stage('Deploy to tomcat server'){
steps{ deploy adapters: [tomcat9(credentialsId: 'tomcat9credentials', path: '', url: 'http://localhost:8080/')], contextPath: 'Ifocus Solutions Pvt Ltd', war: '**/*.war' } }
} }
- please start Jenkins on your machine & make sure Jenkins server is UP & Running state
- please start Tomcat on your machine & make sure Tomcat server is UP & Running state
- please start Sonarqube on your machine & make sure Sonarqube server is UP & Running state
once above steps done then we can execute below script
pipeline{
tools{ maven 'Maven' } agent any
stages{
stage('Clone'){ steps{ git branch: 'main', url: 'https://github.com/srinfotech7358/Petclinic.git' } } stage('Build') { steps { bat 'mvn clean install' } } stage('Test Cases') { steps { bat 'mvn test' } } stage('Archive the Artifacts') { steps { archiveArtifacts artifacts: 'target/*.war', followSymlinks: false } } stage('Sonarqube Analysis') { steps {
bat 'mvn package' bat '''mvn sonar:sonar \ -Dsonar.projectKey=spring-petclinic \ -Dsonar.projectName='spring-petclinic' \ -Dsonar.host.url=http://localhost:9000 \ -Dsonar.token=sqp_96cf5222ab632b69c14baa5590210a7125185d5a''' } } stage('Deploy Application into Tomcat Server') { steps { deploy adapters: [tomcat9(alternativeDeploymentContext: '', credentialsId: 'NewTomcat', path: '', url: 'http://localhost:8080/')], contextPath: 'Test', war: 'target/*.war' } }
}
}
Once sonarqube scanner done, please verify the sonarqube dashboard for reports & results
Go to Administration
Click Projects & Select Background Tasks
You can able to see all scanned projects status
Click on any Project, see the PASSED the quality gates
Click on Overall Code option
see the results
here Code coverage is
Coverage 82.7%
NOTE:: Coverage is greater than or equal to 80.0%, this should be maintained minimum % every project
NOTE:::Duplicated Lines (%) is less than or equal to 3.0%
Go to Dashboard click on Quality Gates
at left side we can see create & just click on it
Provide the Name & Click Create
Your own quality gates are created
this is your own quality gates
nditions on New Code Metric Operator Value Issues is greater than 0 Security Hotspots Reviewed is less than 100% Coverage is less than 80.0%
Duplicated Lines (%) is greater than
select your project
apply the Grant permissions to a user or a group
Apply all the permissions & click Add
go to Quality Profiles
select Language
total java Rules 527
at right saide top click create
provide the Language & Name and click Create
your own profile
click Active More rules
Bulk Change
Activate In Spring-pipeline project
Sure Apply
Succcessfully Applied my own quality profile rules
Activate In Quality Profile (683 rules)
Now we are successfully onboarded spring-petclininc project to Sonarqube server
Running the Pipeline Once the pipeline is configured, Jenkins will execute the SonarQube analysis during the build process. After the build completes, you can view the analysis results in your SonarQube dashboard.
Code coverage Code smells Bugs Vulnerabilities Duplications These reports will be available in the SonarQube dashboard for your project.
JFrog Artifactory is a universal artifact repository manager that serves as a central hub for storing, managing, and distributing software artifacts, binaries, packages, and other assets throughout the software development lifecycle, improving automation, and ensuring release integrity.
Artifact Repository Management:
Allows for storing binaries and artifacts (e.g., libraries, packages, Docker images) in a centralized location. Supports all major package types (e.g., Maven, Gradle, npm, NuGet, RubyGems, etc.). Version Control:
Helps in managing versions of your artifacts and ensures the correct version is used during builds and deployments. Integration with CI/CD:
Integrates seamlessly with CI/CD tools like Jenkins, Bamboo, GitLab CI, and others. Enables automated publishing of artifacts as part of your continuous integration pipeline. Access Control & Security:
Provides fine-grained access control and permissions for users and groups. Supports user authentication, security, and audit trails to ensure compliance and secure artifact management. Replication:
Allows you to replicate artifacts across multiple Artifactory instances, ensuring high availability and disaster recovery capabilities. Remote Repositories:
Artifactory can proxy remote repositories, allowing you to cache and fetch external dependencies without re-downloading them each time. Promotion & Release Management:
You can "promote" artifacts from one repository to another (e.g., from a development repository to a production repository), allowing for better control over releases. Multi-Platform Support:
Artifactory supports multiple programming languages and platforms, making it a universal solution for managing software dependencies and releases.
First Step::
https://jfrog.com/download-jfrog-platform/ ---download url
previous versions link
https://jfrog.com/download-legacy/?product=artifactory&version=7.104.12
All zip version and search 6.12.1 OSS version
https://releases.jfrog.io/artifactory/bintray-artifactory/
Go to download folder and extract all files
go to bin folder
you can found artifactory and go to cmd and run the artifactory.bat from command line
run the artifactory.bat
once artifactory jfrog up & running navigate to below url default port number is 8081
http://localhost:8081/artifactory
default username & password for jfrog is
username::: admin
password::: password
stage ('Artifactory Server'){
steps { rtServer ( id: "Artifactory", url: 'http://localhost:8081/artifactory', username: 'admin', password: 'password', bypassProxy: true, timeout: 300 ) } }
stage('Upload'){
steps{ rtUpload ( serverId:"Artifactory" , spec: '''{ "files": [ { "pattern": "*.war", "target": "srinfotech-solutions-private-limited" } ] }''', ) } }
stage ('Publish build info') {
steps { rtPublishBuildInfo ( serverId: "Artifactory" ) } }
After installed Artifactory plugin
Go to Manage Jenkins--System configuration find JFROG
Click JFrog Platform Instances
For user name and password Go to Jfrogadmin-Securityusers Default Jfrog U/P----admin/password
I need to setup target repository in Jfrog
srinfotech-solutions-private-limited
click Local repository
Select maven
Repository key :::: srinfotech-solutions-private-limited
Click save and finish
Go to artifacts and check repository is created with name -srinfotech-solutions-private-limited
pipeline{
tools{ maven 'Maven' } agent any
stages{
stage('Clone'){ steps{ git branch: 'feature/2025.05.27', url: 'https://github.com/srinfotech7358/Petclinic.git' } } stage('Build') { steps { bat 'mvn clean install' } } stage('Test Cases') { steps { bat 'mvn test' } } stage('package') { steps { bat 'mvn package' } }
stage('Archive the Artifacts') { steps { archiveArtifacts artifacts: 'target/*.war', followSymlinks: false } } stage('Sonarqube Analysis') { steps {
bat 'mvn package' bat '''mvn sonar:sonar \ -Dsonar.projectKey=spring-petclinic \ -Dsonar.projectName='spring-petclinic' \ -Dsonar.host.url=http://localhost:9000 \ -Dsonar.token=sqp_96cf5222ab632b69c14baa5590210a7125185d5a''' } } stage ('Artifactory Server'){ steps { rtServer ( id: "Artifactory", url: 'http://localhost:8081/artifactory', username: 'admin', password: 'password', bypassProxy: true, timeout: 300 ) } }
stage('Upload'){ steps{ rtUpload ( serverId:"Artifactory" , spec: '''{ "files": [ { "pattern": "*.war", "target": "srinfotech-solutions-private-limited" } ] }''', ) } }
stage ('Publish build info') { steps { rtPublishBuildInfo ( serverId: "Artifactory" ) } } stage('Deploy Application into Tomcat Server') { steps { deploy adapters: [tomcat9(alternativeDeploymentContext: '', credentialsId: 'NewTomcat', path: '', url: 'http://localhost:8080/')], contextPath: 'SRIN solutions PVT LTD', war: '**/*.war' } }
}
}
Continuous Integration(CI)::the practice of automating the integration of code changes from multiple Developers into a single software project. It's a primary DevOps best practice, allowing developers to frequently merge code changes into a central repository,after which automated builds and tests are run automatically.
developers frequently commit to a shared repository using a version control system such as Git,A continuous integration automatically builds and runs unit tests on the new code changes to immediately using jenkins Orchestration.
Continuous Deployment(CD) :: Continuous Deployment is an extension of continuous delivery. With continuous deployment, every change that passes through the automated tests and builds is automatically deployed to production without any human intervention. The deployment process is fully automated.
Continuous Delivery (CD)::Continuous Delivery is a software development practice in which code changes are automatically built, tested, and prepared for release to production in a consistent and reliable manner. The key distinction of continuous delivery is that the process of deploying the code to production is done manually by a human decision-maker.
please try to deploy all 3 projects in Tomcat Server
Project1::
https://github.com/srinfotech7358/devOpsWeb.git
Project2::
https://github.com/srinfotech7358/Petclinic.git
Project3::
https://github.com/srinfotech7358/onlinebookstore.git
Post Deployment
Spring-petclinic::
onlinebookstore::
SRInfotech DevOps Project::
Amazon Web Services (AWS) is a comprehensive and widely adopted cloud platform offered by Amazon. It provides a broad set of services to help organizations and individuals build and scale applications, manage data, and process workloads in the cloud. AWS is designed to provide flexible, scalable, and cost-effective solutions for computing, storage, networking, machine learning, and much more.
AWS ---Amazon web services
compute services:: Amazon EC2 (Elastic Compute Cloud): Provides scalable virtual servers to run applications. AWS Lambda: Lets you run code without provisioning or managing servers. It automatically scales based on usage.
Storage services:: Amazon S3 (Simple Storage Service): Object storage for storing and retrieving large amounts of data. Amazon EBS (Elastic Block Store): Persistent block-level storage for EC2 instances.
Database:: Amazon RDS (Relational Database Service): Managed relational database service supporting multiple database engines (e.g., MySQL, PostgreSQL, MariaDB, etc.). Amazon DynamoDB: A managed NoSQL database service. Amazon Aurora: A high-performance relational database engine compatible with MySQL and PostgreSQL.
Network services:: Amazon VPC (Virtual Private Cloud): Lets you create isolated networks within AWS for secure connections.
Security ::
AWS IAM (Identity and Access Management): Controls user access and permissions for AWS resources. AWS KMS (Key Management Service): Managed service for creating and controlling encryption keys. Security groups ---inbound, outbould roles
Containers & kuberneties:: ECS ---elastic containers servcies EKS ----estastic kuberneties services AKS ---Azure kuberneties services
Cloud watch --Metrics Monitoring
CloudWatch Metrics allows you to track the performance and utilization of AWS resources such as EC2 instances, RDS databases, Lambda functions, S3 buckets, and much more. These metrics include CPU utilization, disk activity, network traffic, and others. You can create custom metrics for your applications or services as well.
cloud trail ---Security Monitoring:
Use CloudTrail logs to detect unauthorized access or activity in your AWS environment. You can track changes in security settings, unauthorized API calls, or unexpected configuration changes.
Developer Tools:: AWS CodeCommit: Source control service for managing your code repositories. AWS CodeDeploy: Automates code deployments to EC2 instances and Lambda. AWS CodePipeline: Continuous integration and continuous delivery (CI/CD) service for automating the release pipeline.
Amazon Elastic Compute Cloud (Amazon EC2) is one of the core services provided by Amazon Web Services (AWS)
Wide Variety of Instance Types:
EC2 instances are grouped into families based on the type of workload they are optimized for. Some common instance families include: General Purpose: e.g., t3, m5 instances (balanced CPU, memory, and networking). Compute Optimized: e.g., c5 instances (great for high-performance computing tasks). Memory Optimized: e.g., r5, x1e instances (designed for high-memory workloads like databases).
Go to AWS ans Search EC2
Click EC2
Go to instances at left side bar
Click Launch Instances, EC2 ---> Instances -----> Launch an instance
Select Ubuntu
Select Amazon Machine Image (AMI)
select Instance type,t2 medium
Create Create new key pair and provide key pair name
click create pair
click launch instance
instance will be created
i have to create 2 EC2 ubuntu machines in AWS
- Jenkinsmaster
- Node
we have already .pem file dowloaded in you local machin
right click from .pem and click Open git bash here option Now Go to AWS Ubuntu machine which is already created in AWS insatnces and select master machine
Click Connect
Click SSH Client
Copy URL
ssh -i "Newkeysmasternode.pem" ubuntu@ec2-18-237-178-192.us-west-2.compute.amazonaws.com
Now past that url in Gitbash
switch to root user below command run
Sudo -i
update the all packages ,please run below command
sudo apt-get update
JDK link
https://bluevps.com/blog/how-to-install-java-on-ubuntu
MAven link
https://phoenixnap.com/kb/install-maven-on-ubuntu
sudo apt-get install maven java -version mvn -v
Set java home environment
sudo vi /etc/environment JAVA_HOME=”/usr/lib/jvm/java-8-openjdk-amd64/jre” MAVEN_HOME=”/usr/share/maven”
Reload your system environment
source /etc/environment
Veriy the variables was set correctly
echo $JAVA_HOME echo $MAVEN_HOME
https://phoenixnap.com/kb/install-jenkins-ubuntu
Once installed Jenkins successfully
we need to enabled the Inbounds and outbounds rules in AWS security groups
Inbounds rules
Copy public IP address and go to browser Access Jenkins using Public IP address http://35.86.160.156:8080/
bydefault Jenkins runs on port 8080 Jenkins home path/var/lib/Jenkins
AWS any machines default password authentication is disabled , we need to enabled in any linux machines
sudo vi /etc/ssh/sshd_config sudo service sshd restart In EC2 – by default password based authentication is disabled so we need to enabled vi /etc/ssh/sshd_config passwordauthentication :yes
In ubuntu machine default user is not sudo user,
visudo
Jenkins ALL=(ALL:ALL) NOPASSWD:ALL
su Jenkins
Switching to new user
Once installed Jenkins successfully
we need to enabled the Inbounds and outbounds rules in AWS security groups
Inbounds rules
Copy public IP address and go to browser Access Jenkins using Public IP address http://35.86.160.156:8080/
bydefault Jenkins runs on port 8080 Jenkins home path/var/lib/Jenkins
Please insatll JDK & Maven in node machine and setup environemnt varibles
sudo apt-get install maven java -version mvn -v Set java home environment
sudo vi /etc/environment JAVA_HOME=”/usr/lib/jvm/java-8-openjdk-amd64/jre” MAVEN_HOME=”/usr/share/maven”
Reload your system environment
source /etc/environment
Veriy the variables was set correctly
echo $JAVA_HOME echo $MAVEN_HOME
comminicate master & node via SSH keys
ssh-keygen -t ed25519 after generated the keys, we need to copy public key to node machine
option-1 to copy keys from master to node
ssh-copy-id user@ipaddressofnodemachine ssh-copy-id node@172.31.44.169
2nd option --copy keys manually from master to node
3rd options --i have created authorized_keys file in node machine and copy public key from master to node
keys copied correcctly try below command to run,
ssh username@ipaddressofNodeMachine
- we need to create .ssh directory
mkdir .ssh/ cd .ssh/ touch authorized_keys ls
here i want copy public key from master to node machine into the authorized_keys file
please restsrt all the machines
i want call node1 machine fomr jenkins master
ssh usernameofnode@ipaddressofnodemachine
jenkins@ip-172-31-36-36:~/.ssh$ ssh node1@ip-172-31-41-243
Master Node Configuration::
got to manage Jenkins manage Nodes
click new node Remote root directory
Launch methods via ssh
Add credentials
Host Key Verification Strategy
Master Node Configuration::
got to manage Jenkins manage Nodes click new node Remote root directory
Launch methods via ssh
Add credentials ::
this time please use credentials option SSH key with private key from node machine
please use credentials with Username & password and let's try if you copy properly ,agent machine will conenct Successfully
Host Key Verification Strategy
Agent successfully connected
Execute Jenkins job using slave Create one test slave job in Jenkins
select Restrict where this project can be run
select Label Expression
please create 2 job in jenkins master and setup 1 job in Node machine and 2nd job master machine, just trigger Build Now
Please observe below screenshot 2 job running different machines
advantage of master & Node Integartion
Ansible playbooks are the heart of automation with Ansible. They are simple YAML (Yet Another Markup Language) files that define automation tasks in a structured, human-readable format. Playbooks allow you to automate configurations, deployments, and orchestration tasks in a clear and organized way.
Playbook: A playbook is a file that contains one or more "plays." Each play defines a set of tasks to be executed on a group of hosts. The playbook can be used for things like installing packages, managing users, configuring services, etc.
Task: A task is an individual unit of work. Tasks define specific actions, such as installing a package, starting a service, or copying a file. Tasks are executed sequentially, in the order in which they are written in the playbook.
Inventory: An inventory is a list of hosts that Ansible will manage. The inventory file defines which machines to target. An inventory can group hosts together (e.g., web servers, db servers) for easy management.
Modules: Ansible provides numerous modules that are responsible for performing specific tasks like managing packages, services, files, etc. Common modules include apt, yum, service, copy, and file.
- ACS --ansible control server 2.node1 3.node2
- passwordauthentication enabled
sudo vi /etc/ssh/sshd_config
- Create New user-->ansible and user should be provide the sudo permissions
visudo
ansible ALL=(ALL:ALL) NOPASSWD:ALL
su ansible Switching to new user
3.install ansible in Ansible control server
ansible --version
-
keybased authentication via SSH keys
ssh-keygen -t ed25519
Generated private and public keys
- copy publickey from ansible control server to node machines
if above steps are configured properly ,it will communications happend via sshkeys
- passwordauthentication enabled
sudo vi /etc/ssh/sshd_config
- Create New user-->node1 and user should be provide the sudo permissions
visudo
node1 ALL=(ALL:ALL) NOPASSWD:ALL
su node1 Switching to new user node1
3.install python in node1 machine
https://docs.vultr.com/how-to-install-python-and-pip-on-ubuntu-24-04
python3 --version
- keybased authentication via SSH keys
- passwordauthentication enabled
sudo vi /etc/ssh/sshd_config
- Create New user-->node2 and user should be provide the sudo permissions
visudo
node2 ALL=(ALL:ALL) NOPASSWD:ALL
su node1 Switching to new user node2
3.install python in node1 machine
https://docs.vultr.com/how-to-install-python-and-pip-on-ubuntu-24-04
python3 --version
- keybased authentication via SSH keys
if above steps are configured properly ,it will communications happend via sshkeys
all these 3 machine ping to each other and see beow screenshots all 3 machines pings each other
NOTE:: 1.please create authorized_keys file in ansible master and copy public key to authorized kesy fiile 2.ssh-copy-id ansible@localhost Restart machine
cd /etc/ansible ansible -m ping all It working sudo nano hosts Add all host names or ipaddress or private DNS names
ubuntu@ip-172-31-28-207:~$ sudo -i
root@ip-172-31-28-207:~# su ansible
ansible@ip-172-31-28-207:/root$ cd ~
ansible@ip-172-31-28-207:~$ cd /etc/ansible/
ansible@ip-172-31-28-207:/etc/ansible$ ansible -m ping all
node2@ip-172-31-42-167.us-west-2.compute.internal | SUCCESS => { "ansible_facts": { "discovered_interpreter_python": "/usr/bin/python3.12" }, "changed": false, "ping": "pong" } [WARNING]: Platform linux on host node1@ip-172-31-39-93.us-west-2.compute.internal is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible- core/2.18/reference_appendices/interpreter_discovery.html for more information. node1@ip-172-31-39-93.us-west-2.compute.internal | SUCCESS => { "ansible_facts": { "discovered_interpreter_python": "/usr/bin/python3.12" }, "changed": false, "ping": "pong" } [WARNING]: Platform linux on host ansible@localhost is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible- core/2.18/reference_appendices/interpreter_discovery.html for more information. ansible@localhost | SUCCESS => { "ansible_facts": { "discovered_interpreter_python": "/usr/bin/python3.12" }, "changed": false, "ping": "pong" } [WARNING]: Platform linux on host ansible@ip-172-31-42-190.us-west-2.compute.internal is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible- core/2.18/reference_appendices/interpreter_discovery.html for more information. ansible@ip-172-31-42-190.us-west-2.compute.internal | SUCCESS => { "ansible_facts": { "discovered_interpreter_python": "/usr/bin/python3.12" }, "changed": false, "ping": "pong" }
all these 3 machine ping to each other and see beow screenshots all 3 machines pings each other
Ansible playbooks are the heart of automation with Ansible. They are simple YAML (Yet Another Markup Language) files that define automation tasks in a structured, human-readable format. Playbooks allow you to automate configurations, deployments, and orchestration tasks in a clear and organized way.
Playbook: A playbook is a file that contains one or more "plays." Each play defines a set of tasks to be executed on a group of hosts. The playbook can be used for things like installing packages, managing users, configuring services, etc.
Task: A task is an individual unit of work. Tasks define specific actions, such as installing a package, starting a service, or copying a file. Tasks are executed sequentially, in the order in which they are written in the playbook.
Inventory: An inventory is a list of hosts that Ansible will manage. The inventory file defines which machines to target. An inventory can group hosts together (e.g., web servers, db servers) for easy management.
Modules: Ansible provides numerous modules that are responsible for performing specific tasks like managing packages, services, files, etc. Common modules include apt, yum, service, copy, and file.
A basic playbook has the following components:
YAML Header: The file begins with a --- to indicate it’s a YAML file.
the hosts (target machines) become: yes ----->Sudo user
Tasks: Tasks define the actions to be executed on the target systems.
I want to see where the Ansible is installed on ACS
cd /etc/ansible
Playbook is written in YAML format Inside the playbook tasks Each task is a module Playbook is a one of yaml file Yaml file is a collection of key-value pairsset of all tasks Playbook is tell to the ansible what are the tasks can be performed Each task one module Module is a smallest item of ansible Module can be used to individual or smallest task can be performed Any configuration management tool should maintain ‘state’
hosts: all (apply all we can be mentioned in inventory ) become: yes (become user as a sudo user) tasks:
we can search in google ansible playbook https://docs.ansible.com/ansible/latest/user_guide/playbooks.html https://docs.ansible.com/ansible/latest/user_guide/playbooks_intro.html#basics
-
hosts: all
become: yes
tasks:
-
name: install git
apt:
name: git
state: present
update_cache: yes
-
note:::default state is present update_cache: yes tells Ansible to run the apt-get update command on the remote machine before performing any further package operations (like installing or upgrading packages). become: yes # Elevate privileges to execute tasks as root
ansible@ip-172-31-19-120:/etc/ansible$ ansible-playbook installgit.yml
PLAY [all] **********************************************************************************************
TASK [Gathering Facts] ********************************************************************************** [WARNING]: Platform linux on host localhost is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible- core/2.18/reference_appendices/interpreter_discovery.html for more information. ok: [localhost] [WARNING]: Platform linux on host node2@172.31.30.90 is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible- core/2.18/reference_appendices/interpreter_discovery.html for more information. ok: [node2@172.31.30.90] [WARNING]: Platform linux on host node1@172.31.30.121 is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible- core/2.18/reference_appendices/interpreter_discovery.html for more information. ok: [node1@172.31.30.121]
TASK [install git] ************************************************************************************** ok: [node2@172.31.30.90] ok: [node1@172.31.30.121] ok: [localhost]
PLAY RECAP ********************************************************************************************** localhost : ok=2 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 node1@172.31.30.121 : ok=2 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 node2@172.31.30.90 : ok=2 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
ansible@ip-172-31-19-120:/etc/ansible$ git --version git version 2.43.0 ansible@ip-172-31-19-120:/etc/ansible$ Read from remote host ec2-34-226-192-28.compute-1.amazonaws.com: Connection reset by peer Connection to ec2-34-226-192-28.compute-1.amazonaws.com closed. client_loop: send disconnect: Connection reset by peer
sudo vi installgit.yml
copy git & JDK playbook code to installgit.yml
-
hosts: all
become: yes
tasks:
-
name: install git
apt:
name: git
state: present
update_cache: yes
-
name: Install Java
apt:
name: openjdk-17-jdk
state: present
-
ansible-planbook ansible-playbook installgit.yml
ansible@ip-172-31-42-190:/etc/ansible$ ansible-playbook installgit.yml
PLAY [all] ***********************************************************************************************************
TASK [Gathering Facts] *********************************************************************************************** [WARNING]: Platform linux on host ansible@localhost is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible-core/2.18/reference_appendices/interpreter_discovery.html for more information. ok: [ansible@localhost] [WARNING]: Platform linux on host node2@ip-172-31-42-167.us-west-2.compute.internal is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible-core/2.18/reference_appendices/interpreter_discovery.html for more information. ok: [node2@ip-172-31-42-167.us-west-2.compute.internal] [WARNING]: Platform linux on host node1@ip-172-31-39-93.us-west-2.compute.internal is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible-core/2.18/reference_appendices/interpreter_discovery.html for more information. ok: [node1@ip-172-31-39-93.us-west-2.compute.internal]
TASK [install git in ubuntu machines] ******************************************************************************** ok: [node1@ip-172-31-39-93.us-west-2.compute.internal] ok: [node2@ip-172-31-42-167.us-west-2.compute.internal] ok: [ansible@localhost]
TASK [install JDK17 in ubuntu machines] ****************************************************************************** changed: [node2@ip-172-31-42-167.us-west-2.compute.internal] changed: [ansible@localhost] changed: [node1@ip-172-31-39-93.us-west-2.compute.internal]
PLAY RECAP *********************************************************************************************************** ansible@localhost : ok=3 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 node1@ip-172-31-39-93.us-west-2.compute.internal : ok=3 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 node2@ip-172-31-42-167.us-west-2.compute.internal : ok=3 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
ansible@ip-172-31-42-190:/etc/ansible$ java --version openjdk 17.0.15 2025-04-15 OpenJDK Runtime Environment (build 17.0.15+6-Ubuntu-0ubuntu124.04) OpenJDK 64-Bit Server VM (build 17.0.15+6-Ubuntu-0ubuntu124.04, mixed mode, sharing)
https://docs.ansible.com/ansible/2.9/modules/list_of_all_modules.html https://docs.ansible.com/ansible/2.9/modules/apt_module.html#parameters https://www.geeksforgeeks.org/how-to-install-java-using-ansible-playbook/ https://www.yamllint.com/ https://www.geeksforgeeks.org/how-to-install-tomcat-using-ansible-playbook/
https://docs.ansible.com/ansible/latest/modules/list_of_all_modules.html https://docs.ansible.com/ansible/2.9/modules/list_of_all_modules.html
i want to insatll 4 spfwares(git,jdk17,tree & apache2) :: below playbook name -----> softwaresinstallition.yml
created playbook for this requirement
-
hosts: all
become: yes
tasks:
-
name: install git in ubuntu machines
apt:
name: git
state: present
update_cache: yes
-
name: install JDK17 in ubuntu machines
apt:
name: openjdk-17-jdk state: absent-
name: install tree in ubuntu machines
apt:
name: tree
state: present
-
name: install apache2 in ubuntu machines
apt:
name: apache2
state: absent
-
ansible-playbook softwaresinstallition.yml
ansible@ip-172-31-42-190:/etc/ansible$ sudo vi softwaresinstallition.yml ansible@ip-172-31-42-190:/etc/ansible$ ansible-playbook softwaresinstallition.yml
PLAY [all] ***********************************************************************************************************
TASK [Gathering Facts] *********************************************************************************************** [WARNING]: Platform linux on host ansible@localhost is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible-core/2.18/reference_appendices/interpreter_discovery.html for more information. ok: [ansible@localhost] [WARNING]: Platform linux on host node1@ip-172-31-39-93.us-west-2.compute.internal is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible-core/2.18/reference_appendices/interpreter_discovery.html for more information. ok: [node1@ip-172-31-39-93.us-west-2.compute.internal] [WARNING]: Platform linux on host node2@ip-172-31-42-167.us-west-2.compute.internal is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible-core/2.18/reference_appendices/interpreter_discovery.html for more information. ok: [node2@ip-172-31-42-167.us-west-2.compute.internal]
TASK [install git in ubuntu machines] ******************************************************************************** ok: [node1@ip-172-31-39-93.us-west-2.compute.internal] ok: [node2@ip-172-31-42-167.us-west-2.compute.internal] ok: [ansible@localhost]
TASK [install JDK17 in ubuntu machines] ****************************************************************************** ok: [ansible@localhost] changed: [node2@ip-172-31-42-167.us-west-2.compute.internal] changed: [node1@ip-172-31-39-93.us-west-2.compute.internal]
TASK [install tree in ubuntu machines] ******************************************************************************* ok: [ansible@localhost] changed: [node2@ip-172-31-42-167.us-west-2.compute.internal] changed: [node1@ip-172-31-39-93.us-west-2.compute.internal]
TASK [install apache2 in ubuntu machines] **************************************************************************** changed: [node1@ip-172-31-39-93.us-west-2.compute.internal] changed: [node2@ip-172-31-42-167.us-west-2.compute.internal] changed: [ansible@localhost]
PLAY RECAP *********************************************************************************************************** ansible@localhost : ok=5 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 node1@ip-172-31-39-93.us-west-2.compute.internal : ok=5 changed=3 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 node2@ip-172-31-42-167.us-west-2.compute.internal : ok=5 changed=3 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
Inbound and outbound rules refer to the types of network traffic that are allowed or denied to and from a system, such as a server, virtual machine, or network device. These rules are typically defined in firewalls or security groups (such as in cloud environments like AWS, Azure, or Google Cloud). The primary goal is to control which data can enter or leave a network, ensuring security and proper access control.
Here’s a detailed explanation of inbound and outbound rules:
Inbound Rules:: Inbound rules control traffic entering a system or network. These rules define which types of external traffic are allowed to reach a server, instance, or device.
Common Uses: Allowing specific users or services to access the system.
Restricting access to the system from unauthorized users.
Opening ports for services like web servers (HTTP, HTTPS), SSH, database connections, etc
Allowing incoming traffic on port 80 (HTTP) so that users can access a web server.
Outbound Rules:: Outbound rules control traffic leaving a system or network. These rules define which traffic is allowed to exit a server or device and reach external destinations.
Common Uses: Allowing a server to access external services like APIs, databases, or external servers.
Restricting unwanted traffic from the system to external destinations.
Controlling the flow of outgoing traffic to ensure compliance with security policies.
Allow HTTP/HTTPS: Allow outbound traffic on ports 80 (HTTP) and 443 (HTTPS) to any IP:
After execute the playbook see the Apache2 in browser
ACS----Ansible control server
NODE1::
NODE2::
Executing ansible in 2 ways
- Adhoc command ---> yearly base
- Playbook (YAML/YML) format --> use for repetitive work
where hosts/ipaddress are stored
I want to create my own inventory
Cd /etc/ansible
cat /etc/ansible/hosts
Sudo vi hosts
Copy all hosts
In Ansible, inventory groups are used to organize and categorize hosts (machines or servers) into logical groups. This allows you to apply tasks to specific sets of servers, simplifying playbook management and execution. An inventory is a list of managed hosts and their associated metadata, and groups are one of the key components of that structure.
Here’s a detailed explanation of Ansible inventory groups
- What Are Inventory Groups? An inventory group in Ansible is a way to group hosts based on a shared characteristic. For example, you might have groups for different environments (e.g., dev, prod), different types of servers (e.g., web_servers, db_servers), or other logical categories that fit your needs.
static inventory groups defined in the standard INI or YAML format.
[web_servers]
ansiblenode1@172.31.20.135
ansiblenode2@172.31.30.200
localhost
[db_servers]
ansiblenode1@172.31.20.135
ansiblenode2@172.31.30.200
[app_servers]
localhost
-
hosts: web_server
become: yes
tasks:
-
name: install git
apt:
name: git
state: present
update_cache: yes
-
name: install tree
apt:
name: tree
state: present
-
name: install apache
apt:
name: apache2
state: present
-
once above two files created run the below command
ansible-playbook -i hosts installsoftware.yml
ansible -i hosts -m ping Webserver
Best practice is you need to create our own inventories
sudo vi hosts
after ran the above yaml, please try to access all machines with IPaddresss
Inbound and outbound rules refer to the types of network traffic that are allowed or denied to and from a system, such as a server, virtual machine, or network device. These rules are typically defined in firewalls or security groups (such as in cloud environments like AWS, Azure, or Google Cloud). The primary goal is to control which data can enter or leave a network, ensuring security and proper access control.
Here’s a detailed explanation of inbound and outbound rules:
Inbound Rules:: Inbound rules control traffic entering a system or network. These rules define which types of external traffic are allowed to reach a server, instance, or device.
Common Uses: Allowing specific users or services to access the system.
Restricting access to the system from unauthorized users.
Opening ports for services like web servers (HTTP, HTTPS), SSH, database connections, etc
Allowing incoming traffic on port 80 (HTTP) so that users can access a web server.
Outbound Rules:: Outbound rules control traffic leaving a system or network. These rules define which traffic is allowed to exit a server or device and reach external destinations.
Common Uses: Allowing a server to access external services like APIs, databases, or external servers.
Restricting unwanted traffic from the system to external destinations.
Controlling the flow of outgoing traffic to ensure compliance with security policies.
Allow HTTP/HTTPS: Allow outbound traffic on ports 80 (HTTP) and 443 (HTTPS) to any IP:
A LAMP stack stands for Linux, Apache, MySQL, and PHP, which is a popular open-source software stack used for web development. It provides everything you need to set up a dynamic website or web application.
Here’s a quick overview of each component:
Linux: The operating system (in this case, Ubuntu).
Apache: The web server that serves your website’s files.
MySQL: The database management system for storing and retrieving data.
PHP: The programming language used for dynamic web page generation.
https://www.digitalocean.com/community/tutorials/how-to-install-lamp-stack-on-ubuntu
sudo apt update
sudo apt install apache2
sudo apt install mysql-server
sudo apt install php
sudo apt install libapache2-mod-php
sudo apt install php-mysql
sudo systemctl restart apache2
sudo apt install php-cli
sudo nano /var/www/html/info.php
above steps are manually installed all required softwares in LAMP project but my requirement is to write a Playbook for those manuall steps
-
hosts: all
become: yes
tasks:
-
name: install apache2
apt:
name: apache2
state: present
update_cache: yes
-
name: install php
apt:
name: php
state: present
-
name: install mysql-server
apt:
name: mysql-server
state: present
-
name: install libapache2-mod-php
apt:
name: libapache2-mod-php
state: present
-
name: install php-mysql
apt:
name: php-mysql
state: present
-
name: restart apache
service:
name: apache2
enabled: true
state: restarted
-
name: install php-cli
apt:
name: php-cli
state: present
-
name: copy module info.php
copy:
src: info.php
dest: /var/www/html/info.php
-
https://docs.ansible.com/ansible/latest/collections/ansible/builtin/copy_module.html
https://docs.ansible.com/ansible/latest/collections/ansible/builtin/service_module.html
https://www.digitalocean.com/community/tutorials/how-to-install-lamp-stack-on-ubuntu
[Webservers] ansiblenode1@172.31.20.135 ansiblenode2@172.31.30.200 localhost
[Appservers] ansiblenode1@172.31.20.135
[DBservers]
localhost
ansible@ip-172-31-28-207:/etc/ansible/playbook$ ls hosts info.php installsoftwares.yml phppackage.yml ansible@ip-172-31-28-207:/etc/ansible/playbook$ sudo vi phppackage.yml ansible@ip-172-31-28-207:/etc/ansible/playbook$ sudo vi hosts ansible@ip-172-31-28-207:/etc/ansible/playbook$ sudo vi phppackage.yml ansible@ip-172-31-28-207:/etc/ansible/playbook$ ansible-playbook -i hosts phppackage.yml ansible@ip-172-31-28-207:/etc/ansible/playbook$ sudo vi info.php ansible@ip-172-31-28-207:/etc/ansible/playbook$ ansible-playbook -i hosts phppackage.yml
PLAY [Webservers] *********************************************************************************************
TASK [Gathering Facts] **************************************************************************************** [WARNING]: Platform linux on host localhost is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible-core/2.17/reference_appendices/interpreter_discovery.html for more information. ok: [localhost] [WARNING]: Platform linux on host ansiblenode2@172.31.30.200 is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible-core/2.17/reference_appendices/interpreter_discovery.html for more information. ok: [ansiblenode2@172.31.30.200] [WARNING]: Platform linux on host ansiblenode1@172.31.20.135 is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible-core/2.17/reference_appendices/interpreter_discovery.html for more information. ok: [ansiblenode1@172.31.20.135]
TASK [install apache2] **************************************************************************************** ok: [ansiblenode2@172.31.30.200] ok: [ansiblenode1@172.31.20.135] ok: [localhost]
TASK [install php] ******************************************************************************************** ok: [ansiblenode1@172.31.20.135] ok: [ansiblenode2@172.31.30.200] ok: [localhost]
TASK [install mysql-server] *********************************************************************************** ok: [ansiblenode1@172.31.20.135] ok: [ansiblenode2@172.31.30.200] ok: [localhost]
TASK [install libapache2-mod-php] ***************************************************************************** ok: [ansiblenode1@172.31.20.135] ok: [ansiblenode2@172.31.30.200] ok: [localhost]
TASK [install php-mysql] ************************************************************************************* ok: [ansiblenode1@172.31.20.135] ok: [ansiblenode2@172.31.30.200] ok: [localhost]
TASK [restart apache] ***************************************************************************************** changed: [ansiblenode2@172.31.30.200] changed: [localhost] changed: [ansiblenode1@172.31.20.135]
TASK [install php-cli] **************************************************************************************** ok: [ansiblenode1@172.31.20.135] ok: [localhost] ok: [ansiblenode2@172.31.30.200]
TASK [copy module info.php] *********************************************************************************** changed: [localhost] changed: [ansiblenode2@172.31.30.200] changed: [ansiblenode1@172.31.20.135]
PLAY RECAP **************************************************************************************************** ansiblenode1@172.31.20.135 : ok=9 changed=2 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 ansiblenode2@172.31.30.200 : ok=9 changed=2 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 localhost : ok=9 changed=2 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
Please execute above steps we will see the php insatlled on all 3 machines
- hosts: Webservers become: yes tasks:
- name: install Apache2 in ubuntu machines apt: name: apache2 state: present
- name: apache2 started in ubuntu machines service: name: apache2 enabled: yes state: started
- name: apache2 enabled in ubuntu machines service: name: apache2 enabled: yes state: enabled
- name: install php php-fpm in ubuntu machines apt: name: php php-fpm state: present
- name: install php-mysql in ubuntu machines apt: name: php-mysql state: present
- name: install php-opcache in ubuntu machines apt: name: php-opcache state: present
- name: install php-cli in ubuntu machines apt: name: php-cli state: present
- name: install libapache2-mod-php in ubuntu machines apt: name: libapache2-mod-php state: present
- name: Copy info.php file to Destination folder copy: src: info.php dest: /var/www/html/info.php
https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_loops.html
Repeated tasks can be written as standard loops over a simple list of strings. You can define the list directly in the task.
Using loops Examples::
- name: Add several users ansible.builtin.user: name: "{{ item }}" state: present groups: "wheel" loop:
- testuser1
- testuser2
Working Script and Please try to execute below scripts using Ansible Loops::
-
hosts: Websevers become: yes tasks:
-
name: install all php packages in ubuntu machines apt: name: "{{ item }}" state: present loop:
- php-fpm
- php-mysql
- php-opcache
- php-cli
- libapache2-mod-php
- apache2
-
name: apache2 started in ubuntu machines service: name: apache2 enabled: yes state: started
-
name: apache2 enabled in ubuntu machines service: name: apache2 enabled: yes state: reloaded
-
name: apache2 restarted in ubuntu machines service: name: apache2 enabled: yes state: restarted
-
name: Copy info.php file to Destination folder copy: src: info.php dest: /var/www/html/info.php
-
Setup module is used to collect the facts
Facts-----> information gather from nodes called facts
ansible -I hosts -m setup Webserver
If you're asking about the "filter" parameter in Ansible's command-line modules like below
ansible -i hosts -m setup -a "filter=os" Webserver
ansible_os_family": "Debian"
Ansible when statements
https://docs.ansible.com/ansible/latest/user_guide/playbooks_conditionals.html#the-when-statement
ansible_os_family": "Debian"
When condition is always used bottom of the script and using scrips we can able to run a playbook on a different platforms
-
hosts: Webserver
become: yes
tasks:
-
name: install apache
apt: name: apache2
state: present
update_cache: yes
when: ansible_os_family == "Debian"
-
name: install apache
yum:
name: httpd
state: present
when: ansible_os_family == "Redhat"
-
In Ansible, variables are used to store values that can be referenced and used throughout your playbooks, roles, and tasks. This allows for dynamic, reusable, and flexible automation. Here’s a basic breakdown of how Ansible variables work and the different ways you can define and use them:
define variables in 3 places
- Inventory level lowest priority
- Playbook level
- Command line level –highest level priority
defined variable in Ansible::
1.commandline level ---highest priorty 2.playbook level ----2nd highest priority 3.inventory level -- low priorty a.host level variabel b. group level
Inventory variables: These are defined in the inventory file (or dynamic inventory) for specific hosts or groups.
[webservers] ansiblenode1@172.31.20.135 package_name=git ansiblenode2@172.31.30.200 package_name=apache2 localhost
[webservers:vars] ansiblenode2@172.31.30.200 localhost
package_name=httpd
Playbook variables: You can define variables directly within your playbooks using the vars section.
-
hosts: Webservers
become: yes
vars:
pacakge_name: git
tasks:
-
name: Install all packages
apt:
name: "{{ pacakge_name }}"
state: present
Command-line variables: You can pass variables to your playbooks at runtime using the -e or --extra-vars option.
ansible-playbook -i hosts -e "package_name=apache2" variables2.yml
-
Ansible resolves variable values based on a specific precedence order. The order from highest to lowest precedence is:
Extra-vars (-e on the command line): Command-line variables take the highest precedence.
Playbook variables: Variables defined within the playbook.
Inventory variables: Variables set in the inventory.
-
hosts: Websevers
-
become: yes
vars:
package_name: apache2
package_httpd: httpd
git_variable: git
tasks:
-
name: installed apache
-
apt: name: "{{ package_name }}"
state: present
update_cache: yes
when: ansible_os_family=="Debian"
-
name: installed git
apt: name: "{{ git_variable }}"
state: present
when: ansible_os_family=="Debian"
-
name: installed httpd yum: name: "{{ package_httpd }}"
state: present
when: ansible_os_family=="Redhat"
-
https://docs.ansible.com/ansible/latest/collections/ansible/builtin/debug_module.html
-
name: Echo message on localhost
hosts: localhost
connection: local
gather_facts: no
vars:
message: "Hello from Ansible playbook on localhost!"
tasks:
-
name: Echo message and connection type
ansible.builtin.shell: "echo '{{ message }}' ; echo 'Connection type: {{ ansible_connection }}'"
register: echo_output
-
name: Display output
debug:
msg: "{{ echo_output.stdout_lines }}"
-
ansible-playbook -i hosts -vvv variable.yaml --------> verbose logs purpose ,please run this command
Registry is a module used to results can be stored in a variable Stored ouptput of a task or script I want execute a command and results can be stored in a variable is called registry
Sometimes you want a task to run only when a change is made on a machine. For example, you may want to restart a service if a task updates the configuration of that service, but not if the configuration is unchanged. Ansible uses handlers to address this use case. Handlers are tasks that only run when notified
hosts: webservers become: yes tasks: - name: Ensure apache is at the latest version ansible.builtin.yum: name: httpd state: latest handlers: - name: Restart apache ansible.builtin.service: name: httpd state: restarted
- hosts: DBservers become: yes tasks:
-
name: install apache2 apt: name: apache2 state: present update_cache: yes
-
debug: msg: "install apache2 successfully in ubuntu machines"
-
name: install my sql software apt: name: mysql-server state: present
-
debug: msg: "install mysql-server successfully in ubuntu machines"
-
name: install php apt: name: php state: present
-
debug: msg: "install php successfully in ubuntu machines"
-
name: install libapache2-mod-php apt: name: libapache2-mod-php state: present
-
debug: msg: "install mod php successfully in ubuntu machines"
-
name: install php-mcrypt apt: name: php-mcrypt state: present
-
debug: msg: "install mcrypt successfully in ubuntu machines"
-
name: install php-mysql apt: name: php-mysql state: present
-
debug: msg: "install mysql successfully in ubuntu machines" handlers:
-
name: restart apache2 service: name: apache2 enabled : yes state: stopped handlers:
-
name: start apache2 service: name: apache2 enabled : yes state: started
-
name: install php-cli apt: name: php-cli state: present
-
debug: msg: "install php-cli successfully in ubuntu machines"
-
name: restart apache2 service: name: apache2 enabled : yes state: restarted
-
name: Copy file with src and destination copy: src: info.php dest: /var/www/html/info.php
-
=========================
Working Script::
- hosts: Websevers become: yes tasks:
- name: install all php packages in ubuntu machines apt: name: "{{ item }}" state: present
loop:- php-fpm
- php-mysql
- php-opcache
- php-cli
- libapache2-mod-php
- debug: msg: "installed all the PHP packages"
handlers: - name: install Apache2 in ubuntu machines apt: name: apache2 state: present
- debug: msg: "installed apache2 successfully"
- name: apache2 started in ubuntu machines service: name: apache2 enabled: yes state: started
- debug: msg: "aapche2 started successfully"
- name: apache2 enabled in ubuntu machines service: name: apache2 enabled: yes state: reloaded
- debug: msg: "apache2 reloaded successfully"
- name: apache2 restarted in ubuntu machines service: name: apache2 enabled: yes state: restarted
- debug: msg: "apache2 restaretd successfully"
- name: Copy info.php file to Destination folder copy: src: info.php dest: /var/www/html/info.php
- debug: msg: "copied php file successfully"
- name: install all php packages in ubuntu machines apt: name: "{{ item }}" state: present
Ansible roles are a way of organizing playbooks and tasks in a modular, reusable, and maintainable structure. They allow you to break down complex playbooks into smaller, focused units of functionality that can be easily shared and reused across different projects. Here's a more detailed look at Ansible roles:
https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_reuse_roles.html
1.Written ansible in a reusable fashion 2.How do I use someone else’s work 3.Ansible galaxy is a place where we can find reusable roles
4.Which we can use in your script
install roles
Ansible-galaxy install
ansible-galaxy install my_role
create my own role::
ansible-galaxy init
ansible-galaxy init my_role
my_role/ ├── defaults/ │ └── main.yml # Default variables ├── files/ │ └── somefile # Files to be copied to the target ├── handlers/ │ └── main.yml # Handlers (usually for service restarts) ├── meta/ │ └── main.yml # Metadata about the role ├── tasks/ │ └── main.yml # The main tasks (this file includes other task files if needed) ├── templates/ │ └── config.j2 # Jinja2 templates for dynamic file creation ├── tests/ │ └── test.yml # Test playbooks to verify the role works ├── vars/ │ └── main.yml # Custom variables
Using Roles in Playbooks Once you've defined a role, you can use it in your playbook like this:
- name: Example Playbook using roles hosts: all become: yes roles:
- my_role
Benefits of Using Roles Reusability: Roles can be reused across different playbooks and projects.
Modularity: Roles allow you to organize your playbook into smaller, manageable parts.
Clarity: Each role focuses on a specific task or function, making your playbooks more understandable.
Example Role: Installing Tomcat
https://galaxy.ansible.com/ui/standalone/roles/robertdebock/tomcat/install/
Create my own role
Ansible-galaxy init rolename
Install tomcat
If you're looking to install or use an Ansible role for Tomcat from Ansible Galaxy, you can search for available roles and collections related to Tomcat. Here's how you can find and use a role related to Tomcat from Galaxy.
- Search for a Tomcat Role
To search for a role related to Tomcat on Ansible Galaxy, you can use the following command: bash Copy ansible-galaxy search tomcat This will return a list of roles related to Tomcat that you can install and use. 2. Install a Tomcat Role Once you’ve found a suitable role for Tomcat, you can install it using the ansible-galaxy install command. For example, if you find a role called geerlingguy.tomcat, you can install it by running: bash Copy
ansible-galaxy install geerlingguy.tomcat This will download and install the role into your ~/.ansible/roles/ directory (or the path defined in your ansible.cfg file).
- Use the Installed Tomcat Role in Your Playbook After installing the role, you can use it in your playbook. Here’s an example of a simple playbook that installs and configures Tomcat: yaml Copy
-
hosts: localhost become: yes roles:
- robertdebock.java
- robertdebock.tomcat
ansible-playbook -i hosts Deploywar.yml
This will use the geerlingguy.tomcat role to set up Tomcat on your webservers hosts.
https://galaxy.ansible.com/robertdebock/tomcat
Deploywar.yml
By default tomcat run port 8080 http://18.236.181.244:8080/ http://34.216.173.44:8080/manager/html
Most of the work is done Where is my war file
If war file is available in local machine use copy module if war file is available other machine(internet) use get_url module Tomcat by default install
/opt/tomcat
- hosts: Webservers become: yes roles:
- robertdebock.java
- robertdebock.tomcat tasks:
- name: copy war get_url: url: https://srinfotech.s3.us-west-2.amazonaws.com/jobs/AnsibleIntegartedWith+Jenkins/5/onlinebookstore.war dest: /opt/tomcat/webapps/onlinebookstore.war
Go to AWS account and search S3 bucket
S3=SSS=simple storage services
Select S3
Click Create bucket
Bucket name provide
Object Ownership ---- ACLs enabled selected
Unchecked Block all public access
Ackened
Click crete bucket
S3 bucket is created in AWS
S3 bucket Created successfully
Click Bucket
Click Upload
Click Add Files
Select Onlinebookstore.war file
Select check box to upload the onlinebookstore.war file
Click Upload
Upload Succeeded
Copy URL
- hosts: localhost become: yes roles:
- robertdebock.java
- robertdebock.tomcat tasks:
- name: copy war get_url: url: https://srinfotech.s3.us-west-2.amazonaws.com/jobs/AnsibleIntegartedWith+Jenkins/5/onlinebookstore.war dest: /opt/tomcat/webapps/onlinebookstore.war
run the playbook
ansible-playbook -i hosts onlinebookstore.yml
Success
Verify deployment in Tomcat server
http://54.218.133.244:8080/onlinebookstore/
Go to AWS account and search S3 bucket
S3=SSS=simple storage services
Select S3
Click Create bucket
AWS region --virgenia
Bucket name provide
Object Ownership ---- ACLs enabled selected
Unchecked Block all public access
Ackened
Click crete bucket
S3 bucket is created in AWS
First installed Jenkins in AWS ubuntu machine
Installed S3 publisher plugin
Found S3 profile at system configuration
Second step:: Create IAM role in AWS account
IAM----> Indentity Access Management
Click Users
Click create user
Provide the user name
Click next
select S3 policies
User created successfully
User name::
SRInfotech
Console password::
wv9PC8%3
Create access & secret keys:;
Open new user test
Click create access key
Select Application running on an AWS compute service
Click next
Access keys created
Integaretd S3 with Jenkins
Provided access and secret key
Click test connection
Check passed
Bucket region us-east-1
Destination bucket:: should be give AWS bucket name
Should be enabled Manage artifacts options
Docker is an opensource & Applicatuions level virtualization technology and it's called containirazition.
Docker is an open-source platform that automates the deployment, scaling, and management of applications in lightweight, portable containers. Containers are isolated environments that package an application and all its dependencies (such as libraries, binaries, and configurations) to ensure it runs uniformly across different computing environments.
Docker is a platform and that make it easier to create, deploy, and run applications using containers. Containers are lightweight, standalone, and executable units that include everything needed to run a piece of software, including the code, runtime, libraries, and system tools.
1.container is an insolation area of executuions of your applications OR instance of images are called containers 2.Containers are created from “images” 3. Containers are the core of Docker. They are lightweight, portable, and isolated environments where applications run. Docker is run your software packages /Applications in containers called containarizations.
- if you build a docker container for your application called containerization
- containers have it’s own boundaries
who will create containers? Ans --docker images are created the containers
docker image is a package with all dependencies and the necessary information to create the container and docker image derived from multiple base images.
An image is a snapshot of a container, a blueprint that defines what the container will contain and how it will behave when run. It consists of an application and its dependencies. Docker images are built using a Dockerfile
A Docker Registry is a system for storing and distributing Docker images. It is a centralized location where Docker images can be uploaded (pushed), stored, and downloaded (pulled) by users and applications. Docker images are the building blocks of containers, and registries provide a way to manage, version, and share these images across different environments.
Default registry :: https://hub.docker.com/
1.tomcat & nodejs containers have it’s own process tree,own files systems,own network interfaces own storage,ram…etc 2.when you want to give application to your team/testers docker is the best choice and when you want give system to your team/ testers VMwares are best choice. 3.application level virtulization docker is the best choice and OS level virtulization VMwares are best choice 4.individually scale the your application very easy in docker
Example:: For festival season In your organization leave management application multiple employees are applied leaves at the same time in that scenario docker is very easy to scale the one more application but physically it’s very difficult so docker is the best choice
Please follow below link steps to install the docker in ubuntu and please read all the content in that link
https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-22-04
once installed docker please verify below commands::
docker --version
root@ip-172-31-20-86:~# docker --version Docker version 28.0.4, build b8034c0
root@ip-172-31-20-86:~# docker info Client: Docker Engine - Community Version: 28.0.4 Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.22.0 Path: /usr/libexec/docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.34.0 Path: /usr/libexec/docker/cli-plugins/docker-compose
Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 28.0.4 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Using metacopy: false Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: systemd Cgroup Version: 2 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: 05044ec0a9a75232cad458027ca83437aae3f4da runc version: v1.2.5-0-g59923ef init version: de40ad0 Security Options: apparmor seccomp Profile: builtin cgroupns Kernel Version: 6.8.0-1024-aws Operating System: Ubuntu 24.04.2 LTS OSType: linux Architecture: x86_64 CPUs: 2 Total Memory: 3.82GiB Name: ip-172-31-20-86 ID: 201c6f4b-75d3-4326-adf5-00b9a82a8d4d Docker Root Dir: /var/lib/docker Debug Mode: false Experimental: false Insecure Registries: ::1/128 127.0.0.0/8 Live Restore Enabled: false
if above page is came without any erros, it means docker is installed in your machine
Docker's high-level architecture revolves around several components that work together to provide containerization and isolation for applications
The Docker Client is the primary interface for interacting with Docker. It can be a command-line interface (CLI), like the docker command, or a graphical interface (GUI) in some tools.
It allows users to interact with Docker's features, such as building containers, running containers, and managing containers and images.
It sends requests to the Docker Daemon to execute commands.
The Docker Daemon (also known as dockerd) is the core component of Docker. It runs in the background on the host system.
The daemon is responsible for managing Docker containers, images, networks, and volumes. It listens for Docker API requests and handles container lifecycle operations such as starting, stopping, and building containers.
The Docker Daemon can communicate with multiple Docker clients, allowing for distributed management of containers.
1.The Docker Client sends a command to the Docker Daemon.
2.The Docker Daemon interacts with containers, images, and storage volumes.
3.The Docker Daemon can pull images from a Docker Registry.
4.The Docker Daemon runs containers based on the images and handles networking and storage.
docker pull
docker pull hello-world
docker images ----used to display the all images
docker image ls ----used to display the all images
docker run ---used to build the images and create the container
docker run -d -p 8080:8080 -p 5000:5000 jenkins/jenkins:jdk21
docker ps
above command is used to verify the how many containers are running
docker run -d -p 80:80 nginx:latest
docker ps
above command is used to verify the how many containers are running, you can seee nginx container is running state
Docker detached mode refers to running a container in the background
docker run -d <image_name>
example::
docker run -d nginx
Where:
-d is the flag for detached mode.
<image_name> is the name of the Docker image you want to run.
docker run -d nginx
This command will:
Run the nginx container in detached mode.
Start the container in the background.
docker ps
docker stop
docker start
docker exec -it <container_id_or_name> docker exec -it 5336d949f33b /bin/bash
root@5336d949f33b:/# hostname 5336d949f33b root@5336d949f33b:/# hostname -i 172.17.0.3
docker exec -it 5178eb58223a /bin/bash Use this command inside the container
ctrl pq Outside the containers
take one nginx web server
docker pull nginx
root@ip-172-31-20-86:~# docker pull nginx Using default tag: latest latest: Pulling from library/nginx 6e909acdb790: Pull complete 5eaa34f5b9c2: Pull complete 417c4bccf534: Pull complete e7e0ca015e55: Pull complete 373fe654e984: Pull complete 97f5c0f51d43: Pull complete c22eb46e871a: Pull complete Digest: sha256:124b44bfc9ccd1f3cedf4b592d4d1e8bddb78b51ec2ed5056c52d3692baebc19 Status: Downloaded newer image for nginx:latest docker.io/library/nginx:latest
docker images
root@ip-172-31-20-86:~# docker images REPOSITORY TAG IMAGE ID CREATED SIZE jenkins/jenkins latest be95e0848c42 7 days ago 466MB nginx latest 53a18edff809 7 weeks ago 192MB
docker run -d -p 80:80 nginx
root@ip-172-31-20-86:~# docker run -d -p 80:80 nginx 3d1a52d091b05878e079b89002aa57b460c5263a585a8add0ecc671608d1f999
docker ps
root@ip-172-31-20-86:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 3d1a52d091b0 nginx "/docker-entrypoint.…" 3 seconds ago Up 3 seconds 0.0.0.0:80->80/tcp, [::]:80->80/tcp thirsty_shaw
docker exec -it 3d1a52d091b0
root@ip-172-31-20-86:~# docker exec -it 3d1a52d091b0 /bin/bash docker: 'docker exec' requires at least 2 arguments
root@ip-172-31-20-86:~# docker exec -it 3d1a52d091b0 /bin/bash root@3d1a52d091b0:/# hostname 3d1a52d091b0 root@3d1a52d091b0:/# hostname -i 172.17.0.3
root@5336d949f33b:/# ls bin boot dev docker-entrypoint.d docker-entrypoint.sh etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var root@5336d949f33b:/# cd opt/ root@5336d949f33b:/opt# ls root@5336d949f33b:/opt# cd .. root@5336d949f33b:/# ls bin boot dev docker-entrypoint.d docker-entrypoint.sh etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var root@5336d949f33b:/# cd usr/ root@5336d949f33b:/usr# ls bin games include lib lib64 libexec local sbin share src root@5336d949f33b:/usr# cd lib root@5336d949f33b:/usr/lib# ls apt dpkg init locale lsb mime nginx os-release sasl2 ssl systemd terminfo tmpfiles.d udev x86_64-linux-gnu root@5336d949f33b:/usr/lib# root@5336d949f33b:/usr/lib# docker images bash: docker: command not found root@5336d949f33b:/usr/lib# docker imagesexit bash: docker: command not found root@5336d949f33b:/usr/lib# read escape sequence root@ip-172-31-20-86:# docker images REPOSITORY TAG IMAGE ID CREATED SIZE jenkins/jenkins latest be95e0848c42 7 days ago 466MB nginx latest 53a18edff809 7 weeks ago 192MB ubuntu latest a04dc4851cbc 2 months ago 78.1MB hello-world latest 74cc54e27dc4 2 months ago 10.1kB root@ip-172-31-20-86:# docekr runRead from remote host ec2-34-204-17-141.compute-1.amazonaws.com: Connection reset by peer Connection to ec2-34-204-17-141.compute-1.amazonaws.com closed. client_loop: send disconnect: Connection reset by peer
we can see below nginx web page and nginx is running on containers
root@ip-172-31-39-182:# docker images REPOSITORY TAG IMAGE ID CREATED SIZE jenkins/jenkins jdk21 52e1941f479f 21 hours ago 471MB root@ip-172-31-39-182:# docker run -d -p 8080:8080 -p 5000:5000 jenkins/jenkins:jdk21 aca7ec14bfc5f057f73dc4cf294e920a63712bbd5f838b5205e5e00faa542318 root@ip-172-31-39-182:# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 7 seconds ago Up 6 seconds 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 43 seconds ago Up 43 seconds 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:# java --version Command 'java' not found, but can be installed with: apt install default-jre # version 2:1.17-75, or apt install openjdk-17-jre-headless # version 17.0.14+7-124.04 apt install openjdk-21-jre-headless # version 21.0.6+7-124.04.1 apt install openjdk-19-jre-headless # version 19.0.2+7-4 apt install openjdk-20-jre-headless # version 20.0.2+9-1 apt install openjdk-22-jre-headless # version 2222ea-1 apt install openjdk-11-jre-headless # version 11.0.26+4-1ubuntu124.04 apt install openjdk-8-jre-headless # version 8u442-b06us1-0ubuntu124.04 root@ip-172-31-39-182:# docker exec -it aca7ec14bfc5 /bin/bash jenkins@aca7ec14bfc5:/$ java --version openjdk 21.0.7 2025-04-15 LTS OpenJDK Runtime Environment Temurin-21.0.7+6 (build 21.0.7+6-LTS) OpenJDK 64-Bit Server VM Temurin-21.0.7+6 (build 21.0.7+6-LTS, mixed mode) jenkins@aca7ec14bfc5:/$ sudo apt update bash: sudo: command not found jenkins@aca7ec14bfc5:/$ hostname aca7ec14bfc5 jenkins@aca7ec14bfc5:/$ java --version openjdk 21.0.7 2025-04-15 LTS OpenJDK Runtime Environment Temurin-21.0.7+6 (build 21.0.7+6-LTS) OpenJDK 64-Bit Server VM Temurin-21.0.7+6 (build 21.0.7+6-LTS, mixed mode) jenkins@aca7ec14bfc5:/$ cd /var/lib/ jenkins@aca7ec14bfc5:/var/lib$ ls apt dpkg git misc pam shells.state systemd jenkins@aca7ec14bfc5:/var/lib$ exit exit root@ip-172-31-39-182:# cd /var/lib/ root@ip-172-31-39-182:/var/lib# ls PackageKit command-not-found grub os-prober shim-signed ucf amazon containerd hibinit-agent pam snapd udisks2 app-info dbus ieee-data plymouth sudo unattended-upgrades apport dhcpcd landscape polkit-1 swcatalog update-manager apt docker libuuid private systemd update-notifier boltd dpkg logrotate python tpm usb_modeswitch chrony fwupd man-db sgml-base ubuntu-advantage vim cloud git misc shells.state ubuntu-release-upgrader xml-core root@ip-172-31-39-182:/var/lib# cd .. root@ip-172-31-39-182:/var# cd .. root@ip-172-31-39-182:/# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 7 minutes ago Up 7 minutes 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:/# docker exec -it aca7ec14bfc5 /bin/bash jenkins@aca7ec14bfc5:/$ cd /var/jenkins_home/secret bash: cd: /var/jenkins_home/secret: No such file or directory jenkins@aca7ec14bfc5:/$ ls bin boot dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var jenkins@aca7ec14bfc5:/$ cd secrets bash: cd: secrets: No such file or directory jenkins@aca7ec14bfc5:/$ cd .. jenkins@aca7ec14bfc5:/$ ls bin boot dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var jenkins@aca7ec14bfc5:/$ pwd / jenkins@aca7ec14bfc5:/$ cd /var/jenkins_home/ jenkins@aca7ec14bfc5:$ ls config.xml jenkins.telemetry.Correlator.xml plugins secrets users copy_reference_file.log jobs secret.key updates war hudson.model.UpdateCenter.xml nodeMonitors.xml secret.key.not-so-secret userContent jenkins@aca7ec14bfc5:$ cd secrets jenkins@aca7ec14bfc5:/secrets$ ls initialAdminPassword jenkins.model.Jenkins.crumbSalt master.key jenkins@aca7ec14bfc5:/secrets$ cat initialAdminPassword 3268b754fc93442e9ea3cf22c40fcc8e jenkins@aca7ec14bfc5:/secrets$ read escape sequence root@ip-172-31-39-182:/# docker run -d -p 8080:8080 -p 5000:5000 jenkins/jenkins:jdk21 1b6159a409c358d5a2db6ecc34b13cf29e8f1d94ca249722a47424d02a8d6bc1 docker: Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint unruffled_pare (f76e7f84de1872354f3caf9f2c4d2ee9bf83c468178a614d407f1c5d35df00f3): Bind for 0.0.0.0:5000 failed: port is already allocated
Run 'docker run --help' for more information root@ip-172-31-39-182:/# docker run -d -p 8081:8081 -p 5001:5001 jenkins/jenkins:jdk21 601ef30a9a97b2ef1ab13a6956d603edbc23cd2d2717cb4d2db41f4b88e148ae root@ip-172-31-39-182:/# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 601ef30a9a97 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 8 seconds ago Up 8 seconds 0.0.0.0:5001->5001/tcp, [::]:5001->5001/tcp, 8080/tcp, 0.0.0.0:8081->8081/tcp, [::]:8081->8081/tcp, 50000/tcp frosty_pare aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 12 minutes ago Up 12 minutes 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:/# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 601ef30a9a97 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 2 minutes ago Up About a minute 0.0.0.0:5001->5001/tcp, [::]:5001->5001/tcp, 8080/tcp, 0.0.0.0:8081->8081/tcp, [::]:8081->8081/tcp, 50000/tcp frosty_pare aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 14 minutes ago Up 14 minutes 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:/# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 601ef30a9a97 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 3 minutes ago Up 3 minutes 0.0.0.0:5001->5001/tcp, [::]:5001->5001/tcp, 8080/tcp, 0.0.0.0:8081->8081/tcp, [::]:8081->8081/tcp, 50000/tcp frosty_pare aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 16 minutes ago Up 16 minutes 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:/# docker exec -it 601ef30a9a97 /bin/bash jenkins@601ef30a9a97:/$ java --version openjdk 21.0.7 2025-04-15 LTS OpenJDK Runtime Environment Temurin-21.0.7+6 (build 21.0.7+6-LTS) OpenJDK 64-Bit Server VM Temurin-21.0.7+6 (build 21.0.7+6-LTS, mixed mode) jenkins@601ef30a9a97:/$ cd /var/jenkins_home/ jenkins@601ef30a9a97:$ ls config.xml jenkins.telemetry.Correlator.xml plugins secrets users copy_reference_file.log jobs secret.key updates war hudson.model.UpdateCenter.xml nodeMonitors.xml secret.key.not-so-secret userContent jenkins@601ef30a9a97:$ jenkins@601ef30a9a97:~$ exit exit root@ip-172-31-39-182:/# docker run -d -p 8585:8585 jenkins/jenkins:jdk21 bc684af40e16b2c7eb91de87e952ec7a1ae0bab608bc9d0e17bad723ce853d69 root@ip-172-31-39-182:/# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES bc684af40e16 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 7 seconds ago Up 7 seconds 8080/tcp, 50000/tcp, 0.0.0.0:8585->8585/tcp, [::]:8585->8585/tcp romantic_buck 601ef30a9a97 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 7 minutes ago Up 7 minutes 0.0.0.0:5001->5001/tcp, [::]:5001->5001/tcp, 8080/tcp, 0.0.0.0:8081->8081/tcp, [::]:8081->8081/tcp, 50000/tcp frosty_pare aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 19 minutes ago Up 19 minutes 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:/# docker run -d -p 80:80 jenkins/jenkins:jdk21 a800fb0e6d7cd81cefdb33b1ded7019c478fbd8ebd232498c99316a092b92660 root@ip-172-31-39-182:/# docker psdock docker: unknown command: docker psdock
Run 'docker --help' for more information root@ip-172-31-39-182:/# root@ip-172-31-39-182:/# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES a800fb0e6d7c jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" About a minute ago Up About a minute 8080/tcp, 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 50000/tcp romantic_lewin bc684af40e16 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 2 minutes ago Up 2 minutes 8080/tcp, 50000/tcp, 0.0.0.0:8585->8585/tcp, [::]:8585->8585/tcp romantic_buck 601ef30a9a97 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 9 minutes ago Up 9 minutes 0.0.0.0:5001->5001/tcp, [::]:5001->5001/tcp, 8080/tcp, 0.0.0.0:8081->8081/tcp, [::]:8081->8081/tcp, 50000/tcp frosty_pare aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 22 minutes ago Up 22 minutes 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:/# docker pull srinfotech Using default tag: latest Error response from daemon: pull access denied for srinfotech, repository does not exist or may require 'docker login': denied: requested access to the resource is denied root@ip-172-31-39-182:/# docker pull nginx Using default tag: latest latest: Pulling from library/nginx dad67da3f26b: Pull complete 4eb3a9835b30: Pull complete 021db26e13de: Pull complete 397cc88dcd41: Pull complete 5f4a88bd8474: Pull complete 66467f827546: Pull complete f05e87039331: Pull complete Digest: sha256:dc53c8f25a10f9109190ed5b59bda2d707a3bde0e45857ce9e1efaa32ff9cbc1 Status: Downloaded newer image for nginx:latest docker.io/library/nginx:latest root@ip-172-31-39-182:/# docker images REPOSITORY TAG IMAGE ID CREATED SIZE jenkins/jenkins jdk21 52e1941f479f 21 hours ago 471MB nginx latest 9a9a9fd723f1 2 days ago 192MB root@ip-172-31-39-182:/# docker run -d -p 80:80 nginx:latest 78f28d3d450fa094d496e22de149de21141ffd1e884772251922121a7b40422d docker: Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint interesting_mclaren (f76b2b0d8ace4755840ce6f55c5da9f57bfed6e0f29dd8a41991b31217fc3f6a): Bind for 0.0.0.0:80 failed: port is already allocated
Run 'docker run --help' for more information root@ip-172-31-39-182:/# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES a800fb0e6d7c jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 10 minutes ago Up 10 minutes 8080/tcp, 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 50000/tcp romantic_lewin bc684af40e16 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 11 minutes ago Up 11 minutes 8080/tcp, 50000/tcp, 0.0.0.0:8585->8585/tcp, [::]:8585->8585/tcp romantic_buck 601ef30a9a97 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 18 minutes ago Up 18 minutes 0.0.0.0:5001->5001/tcp, [::]:5001->5001/tcp, 8080/tcp, 0.0.0.0:8081->8081/tcp, [::]:8081->8081/tcp, 50000/tcp frosty_pare aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 31 minutes ago Up 31 minutes 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:/# docker stop a800fb0e6d7c a800fb0e6d7c root@ip-172-31-39-182:/# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES bc684af40e16 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 12 minutes ago Up 12 minutes 8080/tcp, 50000/tcp, 0.0.0.0:8585->8585/tcp, [::]:8585->8585/tcp romantic_buck 601ef30a9a97 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 19 minutes ago Up 19 minutes 0.0.0.0:5001->5001/tcp, [::]:5001->5001/tcp, 8080/tcp, 0.0.0.0:8081->8081/tcp, [::]:8081->8081/tcp, 50000/tcp frosty_pare aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 31 minutes ago Up 31 minutes 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:/# docker run -d -p 80:80 nginx:latest 585b90814ed4871098000ddaf38376502a490bc2f38bfe625d47a3ddd7f0c85f root@ip-172-31-39-182:/# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 585b90814ed4 nginx:latest "/docker-entrypoint.…" 9 seconds ago Up 9 seconds 0.0.0.0:80->80/tcp, [::]:80->80/tcp festive_euler bc684af40e16 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 12 minutes ago Up 12 minutes 8080/tcp, 50000/tcp, 0.0.0.0:8585->8585/tcp, [::]:8585->8585/tcp romantic_buck 601ef30a9a97 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 19 minutes ago Up 19 minutes 0.0.0.0:5001->5001/tcp, [::]:5001->5001/tcp, 8080/tcp, 0.0.0.0:8081->8081/tcp, [::]:8081->8081/tcp, 50000/tcp frosty_pare aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 32 minutes ago Up 32 minutes 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:/# docker images REPOSITORY TAG IMAGE ID CREATED SIZE jenkins/jenkins jdk21 52e1941f479f 21 hours ago 471MB nginx latest 9a9a9fd723f1 2 days ago 192MB root@ip-172-31-39-182:/# docker image tag nginx srinfotech7358/SrInfotechnginx:latest Error parsing reference: "srinfotech7358/SrInfotechnginx:latest" is not a valid repository/tag: invalid reference format: repository name (srinfotech7358/SrInfotechnginx) must be lowercase root@ip-172-31-39-182:/# docker image tag nginx srinfotech7358/srinfotechnginx:latest root@ip-172-31-39-182:/# docker images REPOSITORY TAG IMAGE ID CREATED SIZE jenkins/jenkins jdk21 52e1941f479f 21 hours ago 471MB nginx latest 9a9a9fd723f1 2 days ago 192MB srinfotech7358/srinfotechnginx latest 9a9a9fd723f1 2 days ago 192MB root@ip-172-31-39-182:/# docker login -u srinfotech7358
i Info → A Personal Access Token (PAT) can be used instead. To create a PAT, visit https://app.docker.com/settings
Password:
WARNING! Your credentials are stored unencrypted in '/root/.docker/config.json'. Configure a credential helper to remove this warning. See https://docs.docker.com/go/credential-store/
Login Succeeded root@ip-172-31-39-182:/# docker push srinfotech7358/srinfotechnginx Using default tag: latest The push refers to repository [docker.io/srinfotech7358/srinfotechnginx] cd38dca3d982: Mounted from library/nginx d35594dd7e6d: Mounted from library/nginx 126eaee18409: Mounted from library/nginx 6380429cac56: Mounted from library/nginx 13fcb2d303e8: Mounted from library/nginx 151f9feea563: Mounted from library/nginx 7fb72a7d1a8e: Mounted from library/nginx latest: digest: sha256:3004321c732af3becb9dc247f5e8926faba9186aa67960e15767996abcec588b size: 1778 root@ip-172-31-39-182:/# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 585b90814ed4 nginx:latest "/docker-entrypoint.…" 10 minutes ago Up 10 minutes 0.0.0.0:80->80/tcp, [::]:80->80/tcp festive_euler bc684af40e16 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 22 minutes ago Up 22 minutes 8080/tcp, 50000/tcp, 0.0.0.0:8585->8585/tcp, [::]:8585->8585/tcp romantic_buck 601ef30a9a97 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 29 minutes ago Up 29 minutes 0.0.0.0:5001->5001/tcp, [::]:5001->5001/tcp, 8080/tcp, 0.0.0.0:8081->8081/tcp, [::]:8081->8081/tcp, 50000/tcp frosty_pare aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 42 minutes ago Up 42 minutes 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:/# docker stop 585b90814ed4 585b90814ed4 root@ip-172-31-39-182:/# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES bc684af40e16 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 23 minutes ago Up 23 minutes 8080/tcp, 50000/tcp, 0.0.0.0:8585->8585/tcp, [::]:8585->8585/tcp romantic_buck 601ef30a9a97 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 30 minutes ago Up 30 minutes 0.0.0.0:5001->5001/tcp, [::]:5001->5001/tcp, 8080/tcp, 0.0.0.0:8081->8081/tcp, [::]:8081->8081/tcp, 50000/tcp frosty_pare aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 42 minutes ago Up 42 minutes 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:/# docker run -d -p 80:80 srinfotech7358/srinfotechnginx:latest 9f5173c50d14631bd31c8270f79a45db441e8c66db5b730dbb7197de65594c20 root@ip-172-31-39-182:/# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9f5173c50d14 srinfotech7358/srinfotechnginx:latest "/docker-entrypoint.…" 9 seconds ago Up 8 seconds 0.0.0.0:80->80/tcp, [::]:80->80/tcp vibrant_dewdney bc684af40e16 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 24 minutes ago Up 24 minutes 8080/tcp, 50000/tcp, 0.0.0.0:8585->8585/tcp, [::]:8585->8585/tcp romantic_buck 601ef30a9a97 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 31 minutes ago Up 31 minutes 0.0.0.0:5001->5001/tcp, [::]:5001->5001/tcp, 8080/tcp, 0.0.0.0:8081->8081/tcp, [::]:8081->8081/tcp, 50000/tcp frosty_pare aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 43 minutes ago Up 43 minutes 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:/# docker stop 9f5173c50d14 9f5173c50d14 root@ip-172-31-39-182:/# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES bc684af40e16 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 25 minutes ago Up 25 minutes 8080/tcp, 50000/tcp, 0.0.0.0:8585->8585/tcp, [::]:8585->8585/tcp romantic_buck 601ef30a9a97 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 32 minutes ago Up 32 minutes 0.0.0.0:5001->5001/tcp, [::]:5001->5001/tcp, 8080/tcp, 0.0.0.0:8081->8081/tcp, [::]:8081->8081/tcp, 50000/tcp frosty_pare aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 44 minutes ago Up 44 minutes 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:/# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9f5173c50d14 srinfotech7358/srinfotechnginx:latest "/docker-entrypoint.…" About a minute ago Exited (137) 27 seconds ago vibrant_dewdney 585b90814ed4 nginx:latest "/docker-entrypoint.…" 12 minutes ago Exited (0) 2 minutes ago festive_euler 78f28d3d450f nginx:latest "/docker-entrypoint.…" 13 minutes ago Created interesting_mclaren a800fb0e6d7c jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 23 minutes ago Exited (143) 13 minutes ago romantic_lewin bc684af40e16 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 25 minutes ago Up 25 minutes 8080/tcp, 50000/tcp, 0.0.0.0:8585->8585/tcp, [::]:8585->8585/tcp romantic_buck 601ef30a9a97 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 32 minutes ago Up 32 minutes 0.0.0.0:5001->5001/tcp, [::]:5001->5001/tcp, 8080/tcp, 0.0.0.0:8081->8081/tcp, [::]:8081->8081/tcp, 50000/tcp frosty_pare 1b6159a409c3 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 33 minutes ago Created unruffled_pare aca7ec14bfc5 jenkins/jenkins:jdk21 "/usr/bin/tini -- /u…" 44 minutes ago Up 44 minutes 0.0.0.0:5000->5000/tcp, [::]:5000->5000/tcp, 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp, 50000/tcp festive_tharp root@ip-172-31-39-182:/# docker start 9f5173c50d14 9f5173c50d14 root@ip-172-31-39-182:/# Read from remote host ec2-35-155-150-89.us-west-2.compute.amazonaws.com: Connection reset by peer Connection to ec2-35-155-150-89.us-west-2.compute.amazonaws.com closed. client_loop: send disconnect: Connection reset by peer
docker --version
docker info
docker pull
docker pull ubuntu =docker pull ubuntu:latest
docker images
docker run -d ubuntu
docker ps -aq
docker rmi
docker run -d -p 8080:8080 -p 5000:5000 jenkins/jenkins:jdk21
docker exec -it aca7ec14bfc5 /bin/bash --->inside the container comamnd
docker run -d -p 8080:8080 -p 5000:5000 jenkins/jenkins:jdk21
ctrl+pq or exit
docker image tag nginx srinfotech7358/srinfotechnginx:latest
A Dockerfile is a script containing a series of instructions on how to build a Docker image. It defines the environment and application setup, including dependencies, configurations, and the necessary steps to get your application running in a container.
dockerfile is a text file, and it have set up of all instructiuons
https://docs.docker.com/get-started/docker-concepts/building-images/writing-a-dockerfile/
Dockerfile::dockerfile is text file, and it have set up of all instructiuons
FROM nginx or ubuntu or
LABEL "AUthor =nagaraju@gamil.com"
RUN apt update && apt-get install jenkins -y
COPY . . ----src destnations
ADD . . -----src destinatuion
CMD ["echo",".jar"]
ENTRYPOINT ["echo", "war"]
EXPOSE 8080,8085
ENV APP_HOME ="Ifocus SOlutions pvt ltd"
WORKDIR $APP_HOME /app
VOLUME
FROM: Specifies the base image for the Docker image you're creating.
FROM ubuntu:20.04
RUN: Executes commands inside the container, often used to install dependencies.
RUN apt-get update && apt-get install -y python3
COPY or ADD: Copies files from your local machine into the container.
COPY . /app
WORKDIR: Sets the working directory for any subsequent commands in the Dockerfile.
WORKDIR /app
CMD: Specifies the command to run when a container is started from the image.
CMD ["python3", "app.py"]
EXPOSE: Defines the network ports the container will listen on at runtime.
EXPOSE 8080
ENV: Sets environment variables inside the container. ENV APP_ENV=production CMD & ENTRPOINT can be executed starting of the container
--use CMD you can change the value but ENTRYPOINT not possible to change the value at the starting of the container --CMD you can change the argument value --ENTRYPOINT can’t change the argument value
CMD ["echo",".jar"] ENTRYPOINT ["echo", "war"]
CMD/ENTRYPOINT ====should have something which runs till your app is alive
life time of your container -->time which your cmd/entrypont is alive
Here’s a simple Dockerfile example that builds a Python web app:
FROM python:3.9-slim
WORKDIR /app
COPY . /app
RUN pip install --no-cache-dir -r requirements.txt
EXPOSE 5000
CMD ["python", "app.py"]
Building and Running a Docker Image: Once you’ve written your Dockerfile, you can build and run it using Docker commands:
Build the Docker image:
docker build -t my-python-app .
Run the container:
docker run -d -p 8080:8080 my-python-app
A Dockerfile is a script containing a series of instructions on how to build a Docker image. It defines the environment and application setup, including dependencies, configurations, and the necessary steps to get your application running in a container. Essentially, it's the blueprint for creating Docker images.
-
FROM: Specifies the base image for the Docker image you're creating.
FROM ubuntu:20.04 -
RUN: Executes commands inside the container, often used to install dependencies.
RUN apt-get update && apt-get install -y python3 -
COPY or ADD: Copies files from your local machine into the container.
COPY . /app -
WORKDIR: Sets the working directory for any subsequent commands in the Dockerfile.
WORKDIR /app -
CMD: Specifies the command to run when a container is started from the image.
CMD ["python3", "app.py"]
-
EXPOSE: Defines the network ports the container will listen on at runtime.
EXPOSE 8080 -
ENV: Sets environment variables inside the container.
ENV APP_ENV=production
Here’s a simple Dockerfile example that builds a Python web app:
# Use an official Python runtime as the base image FROM python:3.9-slim # Set the working directory in the container WORKDIR /app # Copy the current directory contents into the container COPY . /app # Install the required dependencies RUN pip install --no-cache-dir -r requirements.txt # Expose the port the app runs on EXPOSE 5000 # Define the command to run the application CMD ["python", "app.py"]Once you’ve written your Dockerfile, you can build and run it using Docker commands:
-
Build the Docker image:
docker build -t my-python-app . -
Run the container:
docker run -p 5000:5000 my-python-app
The Dockerfile streamlines the process of creating consistent and reproducible environments, making it easier to deploy applications across different systems.
https://docs.docker.com/get-started/workshop/02_our_app/
• bridge: Default network for containers on the same host. • host: The container shares the host’s networking stack. • overlay: Used for multi-host networking (requires Docker Swarm). • none: No network connectivity is assigned to the container. • >bridge network is used for single node communication • >overlay network is used for multi node communication • ---Kubernetes/swarm are used to communicate 2 containers in docker that’s like orchestration macvlan network:: may be used to give containers across different hosts unique, routable IP addresses in a larger network IPVLAN:Containers share the host’s MAC address but have individual IP addresses.
docker network create my_custom_network
Created my own network - my_custom_network
docker run -d --name container1 --network my_custom_network nginx
docker run -d --name container2 --network my_custom_network redis
In this example: • container1 will run an Nginx container. • container2 will run a Redis container.
Both containers are connected to the my_custom_network.
To view detailed information about a network (like connected containers and settings), use the docker network inspect command:
docker ps docker network ls docker network inspect my_custom_network
docker network connect my_custom_network container_name Disconnect a Container from a Network: docker network disconnect my_custom_network container_name Remove a Docker Network:: docker network rm my_custom_network Note that the network must be unused by any containers before it can be removed.
A common use case for Docker networks is to isolate different applications or microservices, ensuring that containers in one application cannot easily communicate with containers in another. This helps you maintain security and control over how containers interact with each other.
--default network bridge can only ping throw ip address not container name --our own network bridge(mybridge) able to ping both ip address and container name that’s advantage of network create.
---Kubernetes/swarm are used to communicate 2 containers in docker that’s like orchestration --if you create your own bridge network the advantage is you can able to resolved the any issues using container name not only ipaddress but by default using you can able to resolved the issues by ipaddress.
bridge network is used for single node communication overlay network is used for multi node communication
Docker and Docker Swarm are both tools used to manage containers, but they serve different purposes and have different features.
Docker is a platform that allows you to create, deploy, and run applications inside containers. Containers are lightweight, portable, and ensure that the application works the same regardless of where it's deployed, making Docker a powerful tool for developing, testing, and deploying applications.
• Containerization: Docker encapsulates applications and their dependencies into containers, ensuring consistency across environments (e.g., development, staging, production). • Images and Containers: Docker uses images to define the environment for an application. Containers are instances of those images. • Docker Hub: Docker Hub is a cloud-based registry where you can find pre-built images or upload your own. • Portability: Docker containers can run on any system with Docker installed, from your laptop to a cloud server. • Isolation: Containers are isolated from the host system, so they don’t interfere with other processes or systems.
• Build an Image: docker build -t my-image . • Run a Container: docker run -d --name my-container my-image • List Containers: docker ps • Stop a Container: docker stop my-container • Remove a Container: docker rm my-container • List Images: docker images
Docker Swarm is a clustering and orchestration tool for Docker containers. It allows you to deploy and manage multiple containers across multiple Docker hosts (machines), forming a swarm. This means that you can treat a collection of Docker hosts as a single virtual host and manage them as one. Docker Swarm makes it easier to scale, deploy, and maintain containerized applications in production environments. It provides high availability, fault tolerance, and easy scaling of applications across multiple machines.
- this is Docker Inc's Container Orchestration Platform
- it only supports managing Docker containerized application workloads
- it is pretty easy to install and learn
- can be installed on a laptop with pretty basic configuation as well as it is very light weight
- good for POC or learning purpose
- not production grade
• Node: A machine (physical or virtual) running Docker that is part of the Swarm cluster. There are two types of nodes: o Manager Node: Manages the cluster and orchestrates services. o Worker Node: Runs the actual containers based on instructions from manager nodes. • Service: A service is a description of the tasks (containers) you want to run. When you define a service, Docker Swarm ensures that the desired number of replicas of that service are running at all times. • Task: A task is a running container in the context of a service. Each task runs a container that is part of a service.
• Docker is used to build and run containers on a single machine, whereas Docker Swarm extends Docker to manage containers across a cluster of machines. • Docker Swarm provides orchestration features such as load balancing, scaling, and high availability, which are not available in basic Docker. • Docker Swarm is built into Docker, making it easier to set up and use compared to other container orchestration systems like Kubernetes.
1.Manager Node 2.Worker Node1 3. Worker Node2
docker swarm init runs on master docker swarm join runs on node
docker swarm join --token SWMTKN-1-33cj3h7mhtq98iy5aifyy9s1cdqnzh4jgl3rdgdez0vbfx8fnc-bu27q63wt2i7qfgkh0r07o85o 172.31.24.64:2377
once initialize the swarm it will automatically created overlay network
docker network create –d overlay qt-overlay
docker network create -d overlay qt-overlay docker node ls
docker service create --name my-web-service --replicas 3 -p 80:80 nginx docker service ls docker node ls
--docker always maintain --replicas 3 means 3 containers by default if for example 1 container die docker automatically create container automatically this is main use of services with docker
docker swarm:: multi containarization for your applications
Docker Swarm is a built-in container orchestration tool that allows you to manage a cluster of Docker hosts as a single entity
in any cloud we have docker /container services lke
1.AWS --->ECS ----elastic conatienr services 2.Azure---->ACS ----Azure contaienr services 3.Kuberneties---->EKS ---Elsatic kuberneties services
Docker Flow
Docker Compose is a tool for defining and running multi-container Docker applications. With a docker-compose.yml file, you can configure your application’s services, networks, and volumes, and then start them all with a single command. Below, I'll explain how to create a docker-compose.yml file and walk you through an example that demonstrates its use. version: "3" # Specify the version of Docker Compose
services: <service_name>: # Define your services (containers) image: <image_name> # The Docker image to use (can be local or from Docker Hub) build: <path_to_dockerfile> # Path to the Dockerfile if you need to build the image container_name: <container_name> # Optionally define a container name ports: # Map container ports to host ports - "<host_port>:<container_port>" volumes: # Mount volumes (directories or files) - <host_directory>:<container_directory> environment: # Set environment variables - = depends_on: # Define dependencies between services - <another_service> networks: # Specify networks to connect to - <network_name>
networks: <network_name>: # Define custom networks driver: bridge # Optional: can be "bridge", "host", or "none"
volumes: <volume_name>: # Define named volumes for persistent data
Explanation of the docker-compose.yml Example:
- Version: Specifies the version of the Docker Compose file format to use. In this case, 3.8.
- Services: o web: This is the service for your Node.js application. image: Specifies the base image to use (node:18-alpine). working_dir: Sets the working directory inside the container. volumes: Mounts the current directory (.) to /app inside the container so your application code is accessible to the container. ports: Maps port 3000 on the host to port 3000 inside the container. environment: Sets environment variables like NODE_ENV and the database connection information (DB_HOST=db). depends_on: Ensures the db service is started before the web service. o db: This is the service for your MySQL database. image: Specifies the MySQL version to use (mysql:8.0). environment: Sets environment variables such as the MySQL root password, database name, and user credentials. volumes: Mounts a named volume (db-data) to persist MySQL data between container restarts. ports: Exposes port 3306 for MySQL to allow communication between containers or with the host.
- Volumes: Defines a named volume (db-data) to persist the database data outside of the container.
version: '3.8'
services: web: image: node:18-alpine # Use the official Node.js image container_name: node-app working_dir: /app volumes: - .:/app # Mount the current directory to /app in the container ports: - "3000:3000" # Expose port 3000 on the host and map it to port 3000 in the container environment: - NODE_ENV=development - DB_HOST=db # Reference the db service as the hostname depends_on: - db # Ensure the db service starts first
db: image: mysql:8.0 # Use the official MySQL image container_name: mysql-db environment: MYSQL_ROOT_PASSWORD: rootpassword MYSQL_DATABASE: mydb MYSQL_USER: user MYSQL_PASSWORD: password volumes: - db-data:/var/lib/mysql # Mount a volume for persistent data ports: - "3306:3306" # Expose port 3306 for MySQL
volumes: db-data: # Define a volume for MySQL data persistence
docker compose up -d
docker exec -it bbeebd8d5ca2 /bin/bash
mysql -u root -p
SHOW DATABASES;
CREATE DATABASE SRINFOTECH; USE SRINFOTECH;
CREATE TABLE SRINFOTECHTABLE ( id INT NOT NULL, name VARCHAR(250) NOT NULL, cource VARCHAR(100) NOT NULL, city VARCHAR(200) NOT NULL, PRIMARY KEY(id) );
INSERT INTO SRINFOTECHTABLE VALUES ( 1, "veeresh", "AWSDEVOPS","Hyderabad" );
INSERT INTO SRINFOTECHTABLE VALUES ( 2, "laxmikanth", "AWSDEVOPSTraining","Bangalour" );
INSERT INTO SRINFOTECHTABLE VALUES ( 1, "Rawali", "AWSDEVOPSFullStack","Chennai" );
SELECT * FROM SRINFOTECHTABLE;
Use Cases for Docker Compose: • Multi-container applications: Perfect for web applications that rely on more than one service (e.g., database, caching, backend). • Development environments: Provides a consistent environment that can be easily replicated across different machines. • Testing and CI/CD: Can be used to quickly spin up environments for testing or continuous integration/deployment pipelines
please try to practice below example for docker compose
https://docs.docker.com/compose/gettingstarted/
https://github.com/srinfotech7358/spring-ms.git
Please clone this project in ubuntu machines
root@ip-172-31-20-86:~# git clone https://github.com/srinfotech7358/spring-ms.git
root@ip-172-31-20-86:# cd spring-ms/ root@ip-172-31-20-86:/spring-ms# ls Dockerfile azure-pipeline.yml azure-pipelines.yml deploy.yaml pom.xml src root@ip-172-31-20-86:~/spring-ms#
root@ip-172-31-20-86:~/spring-ms# docker image build -t springmyapp . [+] Building 0.4s (12/12) FINISHED docker:default => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 256B 0.0s => WARN: FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 1) 0.0s => [internal] load metadata for registry.access.redhat.com/ubi8/openjdk-11:latest 0.3s => [internal] load metadata for docker.io/library/maven:3.6.3-jdk-11 0.1s => [auth] library/maven:pull token for registry-1.docker.io 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [internal] load build context 0.0s => => transferring context: 2.76kB 0.0s => [stage-1 1/2] FROM registry.access.redhat.com/ubi8/openjdk-11:latest@sha256:28b35eea470174a39befd8eb9250a3276b79a4f6e7dac787 0.0s => [stage1 1/3] FROM docker.io/library/maven:3.6.3-jdk-11@sha256:1d29ccf46ef2a5e64f7de3d79a63f9bcffb4dc56be0ae3daed5ca5542b38aa 0.0s => CACHED [stage1 2/3] COPY . . 0.0s => CACHED [stage1 3/3] RUN mvn clean package 0.0s => CACHED [stage-1 2/2] COPY --from=stage1 target/*.jar app.jar 0.0s => exporting to image 0.0s => => exporting layers 0.0s => => writing image sha256:bdbbb4bbe700af425032e6a27d6909e2906677fbffce9b833d596e3f37082479 0.0s => => naming to docker.io/library/springmyapp 0.0s
1 warning found (use docker --debug to expand):
- FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 1) root@ip-172-31-20-86:~/spring-ms#
root@ip-172-31-20-86:/spring-ms# docker images REPOSITORY TAG IMAGE ID CREATED SIZE spring latest bdbbb4bbe700 9 hours ago 410MB springmyapp latest bdbbb4bbe700 9 hours ago 410MB srinu7358/spring-03042025 latest bdbbb4bbe700 9 hours ago 410MB allinstructions latest c2993e54968d 9 hours ago 1.17GB 805cbec82269 9 hours ago 1.17GB testmyownimage latest 621f509fde33 10 hours ago 1.1GB ifocus latest 381bfb89fb02 10 hours ago 1.1GB srinu7358/ifocus-myapp latest 381bfb89fb02 10 hours ago 1.1GB root@ip-172-31-20-86:/spring-ms# docker run -d -p 8081:8081 springmyapp:latest 17ac78f05de4abdca3d46972e63f29c897a011d732ca3e76e7c1ef2158af10b1 root@ip-172-31-20-86:~/spring-ms#
/repositoryname: Docker.io username/reponame ::latest
[docker.io/srinu7358/ifocus-myapp] :latest ---->image formate
docker.io -----registry name ----docekr hub
srinu7358 ----repository username
ifocus-myapp ---image name
docker container run –d –p 8080:8080 springmyapp:1.0 -d --> detached mode -p -->mappimg a port 8080: host port 8080: container port springmyapp:: image name 1.0:: tag name
Expected http://54.162.108.91:8080/
docker compose up
sudo apt-get install docker-compose-plugin
docker image tag srinfotechmyapp srinfotech7358/myapp:latest
docker.io/library/hello-world:latest
docker.io--->registry name library -->username-->docker hub username--
Image formate is
registry name/repositoryusername/imagename:tagname
docker -io/srinfotech7358/myapp:latest
1.this is Docker Inc's Container Orchestration Platform 2.it only supports managing Docker containerized application workloads 3.it is pretty easy to install and learn 4.can be installed on a laptop with pretty basic configuation as well as it is very light weight 5.good for POC or learning purpose 6.not production grade
Kubernetes (often abbreviated as K8s) is an open-source container orchestration platform designed to automate the deployment, scaling, and management of containerized applications. Originally developed by Google.
free and opensource container orchestration platform developed by Google along with many open source contributors
it is production grade
free for personal and commercial use
as it is opensource, we won't get support from Google
only supports command line interface (CLI)
doesn't support web console
Kubernetes does provide some basic Dashboard but it is considered a security vulnerability, hence no one uses the Kubernetes Dashboard
Rancher is opensource webconsole for Google Kubernetes
supports inbuilt monitoring features
it can check the health of our application, when it finds your application is not responding, it can repair it or replace it with another good healthy instance of your application it supports inbuilt load-balancing Master ---Management --(Orchestration) Node machine (minion) --workers (containers)
POD ---the smallest unit, mainatained one or more containers
YAML --key-value paires
1.Container Orchestration: Kubernetes helps you manage multiple containers, ensuring that they run efficiently and reliably across many servers.
2.Scaling: Kubernetes can automatically scale your applications up or down based on demand, making it easier to handle varying workloads.
3.Load Balancing: It can distribute network traffic to different containers, ensuring that applications remain responsive even under heavy loads.
4.Self-Healing: If a container crashes or stops working, Kubernetes can automatically restart or replace it, ensuring the application stays available.
5.Automated Deployment and Rollback: Kubernetes can automate the process of deploying new versions of an application, and if something goes wrong, it can roll back to a previous version.
6.Storage Management: Kubernetes can automatically mount the storage resources you need for your applications, making it easier to manage persistent data.
In short, Kubernetes is designed to make it easier to manage applications at scale in a way that is highly automated, reliable, and efficient. It’s widely used in DevOps platform
Cluster:: collection of nodes with a single responsibility
All the nodes in that cluster do same process, same type of work can will do collection of nodes in cluster
Cluster:: a cluster might refer to a set of virtual machines or containers working together for a specific application or service.
Kubernetes Cluster Components: 1.Master Node (Control Plane): The Master Node is the brain of the Kubernetes cluster. It manages the cluster and makes decisions about scheduling, scaling, and maintaining the health of the application. The control plane consists of several key components:
1.API Server:: The API server exposes the Kubernetes API, which is used to interact with the cluster.
2.Scheduler:: The scheduler assigns work (pods) to available worker nodes.
3.Controller Manager: : Ensures that the desired state of the system is maintained, such as ensuring that the correct number of pods are running.
4.etcd: A distributed key-value store used to store all cluster data, including the state of the system (like deployed pods, config maps, and secrets).
Worker Nodes (Minions): o The Worker Nodes are responsible for running the actual application workloads. These nodes host the pods, which are the smallest deployable units in Kubernetes. A worker node typically runs:
1.Kubelet: An agent that ensures the containers in the pods are running and healthy.
2.Kube Proxy: A network proxy that maintains network rules for pod communication.
3.Container Runtime: The software responsible for running containers (e.g., Docker, containerd).
4.Pods::
A pod is the smallest unit of execution in Kubernetes and can contain one or more containers that share resources such as networking and storage. Pods are always deployed in a Kubernetes cluster and are managed by the control plane.
A service in Kubernetes is a way to expose an application running in a pod to other pods or external users. It ensures that network communication between pods is reliable, even as pods are dynamically created or destroyed.
1.Pod is a smallest component in kubernetes
2.In docker smallest component -- > container
3.in kuberneties we will create pods and inside the pods containers are running.
4.one pod speak with other pod using id address(kube-proxy)
5.every pod has ip address
Above picture directly using pods without using services and if ipaddress no longer available our application is not worked. pods communication throw ip address right so it has a problem to resolved the this problem services is come to the picture.
Services –logical entity and maintain ip address
Basically kubernetes is used for maintain containers
bootstraps a cluster. It’s designed to be a simple way for new users to build clusters (more detail on this is in a later chapter).
is a tool for interacting with your existing cluster.
An agent that ensures the containers in the pods are running and check healthy.
Please follow the below link steps to configured the Kubernetes Master and Workers
https://www.linuxtechi.com/install-kubernetes-on-ubuntu-22-04/
kubectl get nodes
root@k8smaster:~# kubectl get nodes NAME STATUS ROLES AGE VERSION k8smaster Ready control-plane 11h v1.28.15 k8sworker1 Ready 11h v1.28.15 k8sworker2 Ready 11h v1.28.15
Make sure we should install the Docker in all the machines
root@k8smaster:~# docker --version
Docker version 28.3.2, build 578ccf6
root@k8smaster:~#
git clone https://github.com/ifocus7358/docker-Java-kubernetes-project.git
root@ip-172-31-36-154:~# git clone https://github.com/ifocus7358/docker-Java-kubernetes-project.git Cloning into 'docker-Java-kubernetes-project'... remote: Enumerating objects: 156, done. remote: Counting objects: 100% (42/42), done. remote: Compressing objects: 100% (32/32), done. remote: Total 156 (delta 27), reused 10 (delta 10), pack-reused 114 (from 1) Receiving objects: 100% (156/156), 27.40 KiB | 9.13 MiB/s, done. Resolving deltas: 100% (35/35), done.
root@ip-172-31-36-154:~# ls
docker-Java-kubernetes-project
root@ip-172-31-36-154:~# cd docker-Java-kubernetes-project/
root@ip-172-31-36-154:~/docker-Java-kubernetes-project# ls
README.md kubernetes productcatalogue shopfront stockmanager root@ip-172-31-36-154:~/docker-Java-kubernetes-project# cd kubernetes/
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# ls
productcatalogue-service.yaml shopfront-service.yaml stockmanager-service.yaml root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# cd ..
root@ip-172-31-36-154:~/docker-Java-kubernetes-project# ls
README.md kubernetes productcatalogue shopfront stockmanager
root@ip-172-31-36-154:~/docker-Java-kubernetes-project# cd shopfront/
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# ls
Dockerfile pom.xml src root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront#
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# docker image build -t shopfront .
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# mvn -v
Apache Maven 3.8.7
So need to build the source code first it will generate target folder
mvn clean install
[INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5.598 s [INFO] Finished at: 2025-04-08T05:52:09Z [INFO] ------------------------------------------------------------------------
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# ls
Dockerfile pom.xml src target root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# cd target/
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront/target# ls
classes generated-sources maven-archiver maven-status shopfront-0.0.1-SNAPSHOT.jar shopfront-0.0.1-SNAPSHOT.jar.original root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront/target# ls
classes generated-sources maven-archiver maven-status shopfront-0.0.1-SNAPSHOT.jar shopfront-0.0.1-SNAPSHOT.jar.original root@ip-172-31-36-154:/docker-Java-kubernetes-project/shopfront/target# cd .. root@ip-172-31-36-154:/docker-Java-kubernetes-project/shopfront# docker build -t shopfront .
[+] Building 8.8s (7/7) FINISHED docker:default => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 198B 0.0s => [internal] load metadata for docker.io/library/openjdk:8-jre 0.1s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [internal] load build context 0.5s => => transferring context: 46.10MB 0.5s => [1/2] FROM docker.io/library/openjdk:8-jre@sha256:667a15e7bc533a90fb39ddb7e5bed63162ac3c13a97e6c698bf4f139f51b7d33 6.1s => => resolve docker.io/library/openjdk:8-jre@sha256:667a15e7bc533a90fb39ddb7e5bed63162ac3c13a97e6c698bf4f139f51b7d33 0.0s => => sha256:2068746827ec1b043b571e4788693eab7e9b2a95301176512791f8c317a2816a 10.88MB / 10.88MB 0.3s => => sha256:a6a74c7b774e00fd2ec5664e257d344f1b7e69e2a618b1c0678f69719863c5ad 1.58kB / 1.58kB 0.0s => => sha256:0c14a0e20aa3a19448f6227265c6642571112e9cd9a69b5e7a323df46d1aa835 7.43kB / 7.43kB 0.0s => => sha256:d9d4b9b6e964657da49910b495173d6c4f0d9bc47b3b44273cf82fd32723d165 5.16MB / 5.16MB 0.2s => => sha256:667a15e7bc533a90fb39ddb7e5bed63162ac3c13a97e6c698bf4f139f51b7d33 1.04kB / 1.04kB 0.0s => => sha256:001c52e26ad57e3b25b439ee0052f6692e5c0f2d5d982a00a8819ace5e521452 55.00MB / 55.00MB 1.3s => => sha256:8510da692cda60e4746c14dd90905695eade5888e2ad640706a2be9dc42a0224 5.66MB / 5.66MB 0.5s => => sha256:c34215579d03c1311f4e8cd3525bc03dbbb53d79d8b58e63cce8cdd355356347 211B / 211B 0.4s => => sha256:73d77b4774a96dfa09076212d5170e977d153ceab60c1ec4312a8f436b91371c 41.42MB / 41.42MB 1.2s => => extracting sha256:001c52e26ad57e3b25b439ee0052f6692e5c0f2d5d982a00a8819ace5e521452 2.7s => => extracting sha256:d9d4b9b6e964657da49910b495173d6c4f0d9bc47b3b44273cf82fd32723d165 0.2s => => extracting sha256:2068746827ec1b043b571e4788693eab7e9b2a95301176512791f8c317a2816a 0.3s => => extracting sha256:8510da692cda60e4746c14dd90905695eade5888e2ad640706a2be9dc42a0224 0.2s => => extracting sha256:c34215579d03c1311f4e8cd3525bc03dbbb53d79d8b58e63cce8cdd355356347 0.0s => => extracting sha256:73d77b4774a96dfa09076212d5170e977d153ceab60c1ec4312a8f436b91371c 1.0s => [2/2] ADD target/shopfront-0.0.1-SNAPSHOT.jar app.jar 2.1s => exporting to image 0.3s => => exporting layers 0.3s => => writing image sha256:3ccf19de392942c193c580caabe914257071f0c0b1cb8c8b371d369d5e0630fd 0.0s => => naming to docker.io/library/shopfront 0.0s root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE shopfront latest 3ccf19de3929 14 seconds ago 320MB gcr.io/k8s-minikube/kicbase v0.0.46 e72c4cbe9b29 2 months ago 1.31GB root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# docker run -d -p 80:80 shopfront
836d8e23016935ac3cd74067bbdb4998dba147ce425d17edafced967b1884233 root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 836d8e230169 shopfront "java -Djava.securit…" 6 seconds ago Up 5 seconds 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 8010/tcp epic_leavitt ad8f297fbeca gcr.io/k8s-minikube/kicbase:v0.0.46 "/usr/local/bin/entr…" 27 minutes ago Up 27 minutes 127.0.0.1:32768->22/tcp, 127.0.0.1:32769->2376/tcp, 127.0.0.1:32770->5000/tcp, 127.0.0.1:32771->8443/tcp, 127.0.0.1:32772->32443/tcp minikube root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront#
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE shopfront latest 3ccf19de3929 3 minutes ago 320MB gcr.io/k8s-minikube/kicbase v0.0.46 e72c4cbe9b29 2 months ago 1.31GB root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 836d8e230169 shopfront "java -Djava.securit…" About a minute ago Up About a minute 0.0.0.0:80->80/tcp, [::]:80->80/tcp, 8010/tcp epic_leavitt ad8f297fbeca gcr.io/k8s-minikube/kicbase:v0.0.46 "/usr/local/bin/entr…" 28 minutes ago Up 28 minutes 127.0.0.1:32768->22/tcp, 127.0.0.1:32769->2376/tcp, 127.0.0.1:32770->5000/tcp, 127.0.0.1:32771->8443/tcp, 127.0.0.1:32772->32443/tcp minikube root@ip-172-31-36-154:/docker-Java-kubernetes-project/shopfront# docker rm 836d8e230169 Error response from daemon: cannot remove container "/epic_leavitt": container is running: stop the container before removing or force remove root@ip-172-31-36-154:/docker-Java-kubernetes-project/shopfront# docker rm -f 836d8e230169
836d8e230169 root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ad8f297fbeca gcr.io/k8s-minikube/kicbase:v0.0.46 "/usr/local/bin/entr…" 29 minutes ago Up 29 minutes 127.0.0.1:32768->22/tcp, 127.0.0.1:32769->2376/tcp, 127.0.0.1:32770->5000/tcp, 127.0.0.1:32771->8443/tcp, 127.0.0.1:32772->32443/tcp minikube root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE shopfront latest 3ccf19de3929 4 minutes ago 320MB gcr.io/k8s-minikube/kicbase v0.0.46 e72c4cbe9b29 2 months ago 1.31GB root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# docker image tag shopfront srinu7358/shopfront-myapp
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE shopfront latest 3ccf19de3929 6 minutes ago 320MB srinu7358/shopfront-myapp latest 3ccf19de3929 6 minutes ago 320MB gcr.io/k8s-minikube/kicbase v0.0.46 e72c4cbe9b29 2 months ago 1.31GB root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# docker login -u srinu7358
i Info → A Personal Access Token (PAT) can be used instead. To create a PAT, visit https://app.docker.com/settings
Password:
WARNING! Your credentials are stored unencrypted in '/root/.docker/config.json'. Configure a credential helper to remove this warning. See https://docs.docker.com/go/credential-store/
Login Succeeded root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# docker push srinnfotech7358/shopfrontnewapp
Using default tag: latest The push refers to repository [docker.io/srinu7358/shopfront-myapp] c54136e18c64: Pushed 1aaddf64804f: Mounted from library/openjdk 990c5138f5d1: Mounted from library/openjdk 5c384ea5f752: Mounted from library/openjdk 293d5db30c9f: Mounted from library/openjdk 03127cdb479b: Mounted from library/openjdk 9c742cd6c7a5: Mounted from library/openjdk latest: digest: sha256:e027803e479a98c9d1fdcc6d983a6b778b62c2a91dee9bcccfffcb921848b42e size: 1794 root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# docker pull srinu7358/shopfront-myapp:latest
latest: Pulling from srinu7358/shopfront-myapp Digest: sha256:e027803e479a98c9d1fdcc6d983a6b778b62c2a91dee9bcccfffcb921848b42e Status: Image is up to date for srinu7358/shopfront-myapp:latest docker.io/srinu7358/shopfront-myapp:latest root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE shopfront latest 3ccf19de3929 12 minutes ago 320MB srinnfotech7358/shopfrontnewapp latest 3ccf19de3929 12 minutes ago 320MB gcr.io/k8s-minikube/kicbase v0.0.46 e72c4cbe9b29 2 months ago 1.31GB root@ip-172-31-36-154:~/docker-Java-kubernetes-project/shopfront# cd ..
root@ip-172-31-36-154:~/docker-Java-kubernetes-project# ls
README.md kubernetes productcatalogue shopfront stockmanager root@ip-172-31-36-154:~/docker-Java-kubernetes-project# Read from remote host ec2-54-174-108-84.compute-1.amazonaws.com: Connection reset by peer Connection to ec2-54-174-108-84.compute-1.amazonaws.com closed. client_loop: send disconnect: Connection reset by peer
Please build the stockmanager project and it will generated target/ after build success
[INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 5.152 s [INFO] Finished at: 2025-04-10T04:54:00Z [INFO] ------------------------------------------------------------------------ root@ip-172-31-36-154:/docker-Java-kubernetes-project/stockmanager# ls Dockerfile build pom.xml src target root@ip-172-31-36-154:/docker-Java-kubernetes-project/stockmanager# cd target/ root@ip-172-31-36-154:~/docker-Java-kubernetes-project/stockmanager/target# ls classes generated-sources maven-archiver maven-status stockmanager-0.0.1-SNAPSHOT.jar stockmanager-0.0.1-SNAPSHOT.jar.original
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/stockmanager# docker image build -t stockmanager .
[+] Building 1.1s (8/8) FINISHED docker:default => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 201B 0.0s => [internal] load metadata for docker.io/library/openjdk:8-jre 0.1s => [auth] library/openjdk:pull token for registry-1.docker.io 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [internal] load build context 0.4s => => transferring context: 43.32MB 0.4s => CACHED [1/2] FROM docker.io/library/openjdk:8-jre@sha256:667a15e7bc533a90fb39ddb7e5bed63162ac3c13a97e6c698bf4f139f51b7d33 0.0s => [2/2] ADD target/stockmanager-0.0.1-SNAPSHOT.jar app.jar 0.2s => exporting to image 0.3s => => exporting layers 0.3s => => writing image sha256:3de0cce0b9d4173e0ab799d4a59b986a841c5e08244b25d0887f1d0a9d496662 0.0s => => naming to docker.io/library/stockmanager
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/stockmanager# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE stockmanager latest 3de0cce0b9d4 10 seconds ago 317MB shopfront latest 3ccf19de3929 47 hours ago 320MB srinu7358/shopfront-myapp latest 3ccf19de3929 47 hours ago 320MB gcr.io/k8s-minikube/kicbase v0.0.46 e72c4cbe9b29 2 months ago 1.31GB
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/stockmanager# docker image tag stockmanager srinu7358/stockmanager-myapp
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/stockmanager# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE stockmanager latest 3de0cce0b9d4 About a minute ago 317MB srinu7358/stockmanager-myapp latest 3de0cce0b9d4 About a minute ago 317MB shopfront latest 3ccf19de3929 47 hours ago 320MB srinu7358/shopfront-myapp latest 3ccf19de3929 47 hours ago 320MB gcr.io/k8s-minikube/kicbase v0.0.46 e72c4cbe9b29 2 months ago 1.31GB
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/stockmanager# docker login -u srinu7358
i Info → A Personal Access Token (PAT) can be used instead. To create a PAT, visit https://app.docker.com/settings
Password: Login Succeeded
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/stockmanager# docker push srinu7358/stockmanager-myapp
Using default tag: latest The push refers to repository [docker.io/srinu7358/stockmanager-myapp] 03b73450f8a0: Pushed 1aaddf64804f: Mounted from srinu7358/shopfront-myapp 990c5138f5d1: Mounted from srinu7358/shopfront-myapp 5c384ea5f752: Mounted from srinu7358/shopfront-myapp 293d5db30c9f: Mounted from srinu7358/shopfront-myapp 03127cdb479b: Mounted from srinu7358/shopfront-myapp 9c742cd6c7a5: Mounted from srinu7358/shopfront-myapp latest: digest: sha256:1104a4cb9737fc33cae8cfb60b7b0093942da0c201322e4e001ddb9fb417f23b size: 1794
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/productcatalogue# ls
Dockerfile pom.xml product-catalogue.yml src
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/productcatalogue# cd src/
root@ip-172-31-36-154:/docker-Java-kubernetes-project/productcatalogue/src# ls main root@ip-172-31-36-154:/docker-Java-kubernetes-project/productcatalogue/src# cd ..
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/productcatalogue# mvn clean install
[INFO] Scanning for projects...
[INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 9.130 s [INFO] Finished at: 2025-04-10T04:58:34Z [INFO] ------------------------------------------------------------------------ root@ip-172-31-36-154:~/docker-Java-kubernetes-project/productcatalogue# ls Dockerfile pom.xml product-catalogue.yml src target
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/productcatalogue# docker image build -t productcatalogue .
[+] Building 0.6s (8/8) FINISHED docker:default => [internal] load build definition from Dockerfile 0.0s => => transferring dockerfile: 273B 0.0s => [internal] load metadata for docker.io/library/openjdk:8-jre 0.1s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => CACHED [1/3] FROM docker.io/library/openjdk:8-jre@sha256:667a15e7bc533a90fb39ddb7e5bed63162ac3c13a97e6c698bf4f139f51b7d33 0.0s => [internal] load build context 0.2s => => transferring context: 17.63MB 0.2s => [2/3] ADD target/productcatalogue-0.0.1-SNAPSHOT.jar app.jar 0.1s => [3/3] ADD product-catalogue.yml app-config.yml 0.0s => exporting to image 0.1s => => exporting layers 0.1s => => writing image sha256:6c0847459aa3acde4375bfed34e3f04d029bf02a6ceedff1503657d3fc4e75e4 0.0s => => naming to docker.io/library/productcatalogue
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/productcatalogue# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE productcatalogue latest 6c0847459aa3 9 seconds ago 291MB stockmanager latest 3de0cce0b9d4 4 minutes ago 317MB srinu7358/stockmanager-myapp latest 3de0cce0b9d4 4 minutes ago 317MB shopfront latest 3ccf19de3929 47 hours ago 320MB srinu7358/shopfront-myapp latest 3ccf19de3929 47 hours ago 320MB gcr.io/k8s-minikube/kicbase v0.0.46 e72c4cbe9b29 2 months ago 1.31GB
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/productcatalogue# docker image tag productcatalogue
srinu7358/productcatalogue-myapp
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/productcatalogue# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE productcatalogue latest 6c0847459aa3 About a minute ago 291MB srinu7358/productcatalogue-myapp latest 6c0847459aa3 About a minute ago 291MB stockmanager latest 3de0cce0b9d4 5 minutes ago 317MB srinu7358/stockmanager-myapp latest 3de0cce0b9d4 5 minutes ago 317MB srinu7358/shopfront-myapp latest 3ccf19de3929 47 hours ago 320MB shopfront latest 3ccf19de3929 47 hours ago 320MB gcr.io/k8s-minikube/kicbase v0.0.46 e72c4cbe9b29 2 months ago 1.31GB
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/productcatalogue# docker push srinu7358/productcatalogue-myapp
Using default tag: latest The push refers to repository [docker.io/srinu7358/productcatalogue-myapp] c445b4f83c8c: Pushed 24772609f9a3: Pushed 1aaddf64804f: Mounted from srinu7358/stockmanager-myapp 990c5138f5d1: Mounted from srinu7358/stockmanager-myapp 5c384ea5f752: Mounted from srinu7358/stockmanager-myapp 293d5db30c9f: Mounted from srinu7358/stockmanager-myapp 03127cdb479b: Mounted from srinu7358/stockmanager-myapp 9c742cd6c7a5: Mounted from srinu7358/stockmanager-myapp latest: digest: sha256:5254cff2f0ce313265acee48dc8a8bd7a502ff0a6f08e3bb0dfa3ec7738676c8 size: 2001
edit the yaml file
root@ip-172-31-36-154:~/docker-Java-kubernetes-project# ls
README.md kubernetes productcatalogue shopfront stockmanager
root@ip-172-31-36-154:~/docker-Java-kubernetes-project# cd kubernetes/
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# ls
productcatalogue-service.yaml shopfront-service.yaml stockmanager-service.yaml
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# sudo vi shopfront-service.yaml
in yaml file please use your docker hub image------->srinu7358/shopfront-myapp
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get pods
No resources found in default namespace. root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get deploy
No resources found in default namespace. root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get service
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 10.96.0.1 443/TCP 47h
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl apply -f shopfront-service.yaml
service/shopfront created deployment.apps/shopfront created above command is used to created pods,deployments,servcies
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get po
NAME READY STATUS RESTARTS AGE shopfront-69467555f6-nzsxw 1/1 Running 0 22s
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get deploy
NAME READY UP-TO-DATE AVAILABLE AGE shopfront 1/1 1 1 7m2s
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get service
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 10.96.0.1 443/TCP 2d shopfront NodePort 10.109.12.218 8010:32451/TCP 7m14s
we need to do other 2 micro services as well
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# sudo vi productcatalogue-service.yaml
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl apply -f productcatalogue-service.yaml
service/productcatalogue created deployment.apps/productcatalogue created root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get po
NAME READY STATUS RESTARTS AGE productcatalogue-968c9cbf8-dl5zx 0/1 ErrImagePull 0 15s shopfront-69467555f6-nzsxw 1/1 Running 0 9m4s stockmanager-6c4454c6cb-2hhfd 1/1 Running 3 (2s ago) 2m43s root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get deploy
NAME READY UP-TO-DATE AVAILABLE AGE productcatalogue 0/1 1 0 42s shopfront 1/1 1 1 9m31s stockmanager 1/1 1 1 3m10s root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 10.96.0.1 443/TCP 2d productcatalogue NodePort 10.105.165.177 8020:32215/TCP 56s shopfront NodePort 10.109.12.218 8010:32451/TCP 9m45s stockmanager NodePort 10.96.92.240 8030:31767/TCP 3m24s root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get deploy
NAME READY UP-TO-DATE AVAILABLE AGE productcatalogue 0/1 1 0 71s shopfront 1/1 1 1 10m stockmanager 1/1 1 1 3m39s root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get po
NAME READY STATUS RESTARTS AGE productcatalogue-968c9cbf8-dl5zx 0/1 ImagePullBackOff 0 77s shopfront-69467555f6-nzsxw 1/1 Running 0 10m stockmanager-6c4454c6cb-2hhfd 1/1 Running 4 (14s ago) 3m45s
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get po
NAME READY STATUS RESTARTS AGE productcatalogue-968c9cbf8-dl5zx 0/1 ImagePullBackOff 0 2m8s shopfront-69467555f6-nzsxw 1/1 Running 0 10m stockmanager-6c4454c6cb-2hhfd 1/1 Running 5 (15s ago) 4m36s root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# sudo vi productcatalogue-service.yaml
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl apply -f productcatalogue-service.yaml
service/productcatalogue unchanged deployment.apps/productcatalogue configured root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get po
NAME READY STATUS RESTARTS AGE productcatalogue-86c9dd7b7b-bzj29 1/1 Running 0 16s shopfront-69467555f6-nzsxw 1/1 Running 0 14m stockmanager-6c4454c6cb-2hhfd 0/1 CrashLoopBackOff 6 (44s ago) 8m25s root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get po
NAME READY STATUS RESTARTS AGE productcatalogue-86c9dd7b7b-bzj29 1/1 Running 0 28s shopfront-69467555f6-nzsxw 1/1 Running 0 14m stockmanager-6c4454c6cb-2hhfd 0/1 CrashLoopBackOff 6 (56s ago) 8m37s root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl apply -f stockmanager-service.yaml
service/stockmanager unchanged deployment.apps/stockmanager configured root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get po
NAME READY STATUS RESTARTS AGE productcatalogue-86c9dd7b7b-bzj29 1/1 Running 0 47s shopfront-69467555f6-nzsxw 1/1 Running 0 15m stockmanager-6c4454c6cb-2hhfd 0/1 CrashLoopBackOff 6 (75s ago) 8m56s
if any pod is CrashLoopBackOff , please delete or update new image
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get po
NAME READY STATUS RESTARTS AGE productcatalogue-86c9dd7b7b-bzj29 1/1 Running 0 47s shopfront-69467555f6-nzsxw 1/1 Running 0 15m stockmanager-6c4454c6cb-2hhfd 0/1 CrashLoopBackOff 6 (75s ago) 8m56s root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl delete po stockmanager-6c4454c6cb-2hhfd
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get po
NAME READY STATUS RESTARTS AGE productcatalogue-86c9dd7b7b-bzj29 1/1 Running 0 91s shopfront-69467555f6-nzsxw 1/1 Running 0 16m stockmanager-6c4454c6cb-8wkxv 1/1 Running 0 5s
root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get po
NAME READY STATUS RESTARTS AGE productcatalogue-86c9dd7b7b-bzj29 1/1 Running 0 2m54s shopfront-69467555f6-wwfbv 1/1 Running 0 5s stockmanager-6c4454c6cb-8wkxv 1/1 Running 1 (28s ago) 88s root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get deploy
NAME READY UP-TO-DATE AVAILABLE AGE productcatalogue 1/1 1 1 10m shopfront 1/1 1 1 19m stockmanager 1/1 1 1 12m root@ip-172-31-36-154:~/docker-Java-kubernetes-project/kubernetes# kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 10.96.0.1 443/TCP 2d productcatalogue NodePort 10.105.165.177 8020:32215/TCP 10m shopfront NodePort 10.109.12.218 8010:32451/TCP 19m stockmanager NodePort 10.96.92.240 8030:31767/TCP 13m
kubectl describe svc shopfront
use above command to ge the details of service
YAML::
apiversion --v1 or v2 --standadard syntax kind ----deployment/service metadata ----we can define name of the service name: shopfront labels ---->laben are very important in kubernetes and match with pod and matcgh with service
spec type: clusterIP/NodePort
ClusterIP is the default service type in Kubernetes. It creates a virtual IP (VIP) inside the cluster that other internal components (pods/services) can access — but it's not accessible from outside the cluster.
apiVersion: v1 kind: Service metadata: name: backend-service spec: type: ClusterIP # This is the default, so it can be omitted selector: app: my-backend ports: - protocol: TCP port: 80 # Port exposed by the service targetPort: 8080 # Port the container is listening on
NodePort is a type of Kubernetes Service that exposes your app outside the cluster, by opening a specific port on each worker node's IP address.
apiVersion: v1 kind: Service metadata: name: my-nodeport-service spec: type: NodePort selector: app: my-app ports: - port: 80 # Service port (used internally by ClusterIP) targetPort: 8080 # Port on the pod nodePort: 30080 # Optional: if not set, Kubernetes picks one
root@k8smaster:~# kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 10.96.0.1 443/TCP 2d11h
nginx-app NodePort 10.102.214.44 80:31129/TCP 2d10h
productcatalogue NodePort 10.101.216.239 8020:32208/TCP 2d10h
shopfront NodePort 10.102.253.116 8010:31499/TCP 2d10h
stockmanager NodePort 10.96.66.251 8030:32579/TCP 2d10h
root@k8smaster:~# kubectl get deploy
NAME READY UP-TO-DATE AVAILABLE AGE
nginx-app 2/2 2 2 2d11h
productcatalogue 1/1 1 1 2d10h
shopfront 1/1 1 1 2d10h
stockmanager 1/6 6 1 2d10h
root@k8smaster:~# kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-app-5777b5f95-fcx8r 1/1 Running 0 2d11h
nginx-app-5777b5f95-v5ghx 1/1 Running 0 2d11h
productcatalogue-869f894bc7-66f86 1/1 Running 0 2d10h
shopfront-66555cc947-hkg9v 1/1 Running 0 2d10h
stockmanager-7657c6dfc5-4rntl 0/1 CrashLoopBackOff 995 (4m31s ago) 2d10h
stockmanager-7657c6dfc5-4skjh 0/1 CrashLoopBackOff 1016 (112s ago) 2d10h
stockmanager-7657c6dfc5-657z6 0/1 CrashLoopBackOff 997 (2m11s ago) 2d10h
stockmanager-7657c6dfc5-7nrdc 0/1 CrashLoopBackOff 995 (3m11s ago) 2d10h
stockmanager-7657c6dfc5-f46vf 1/1 Running 996 (5m41s ago) 2d10h
stockmanager-7657c6dfc5-qznfs 0/1 CrashLoopBackOff 999 (118s ago) 2d10h
root@k8smaster:~# kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 10.96.0.1 443/TCP 2d11h
nginx-app NodePort 10.102.214.44 80:31129/TCP 2d11h
productcatalogue NodePort 10.101.216.239 8020:32208/TCP 2d10h
shopfront NodePort 10.102.253.116 8010:31499/TCP 2d10h
stockmanager NodePort 10.96.66.251 8030:32579/TCP 2d10h
shopfront 8010:31499/TCP
productcatalogue 8020:32208/TCP
stockmanager 8030:32579/TCP
Navigate to browser url shopfront with port
Navigate to browser url productcatalogue with port
http://35.94.221.231:32208/products
Navigate to browser url stockmanager with port
http://35.94.221.231:32579/stocks