We are going to learn how to Automate build and deploy of Springboot Microservices App into Azure Kubernetes Cluster(AKS) using Helm and Jenkins pipeline.
Sample springboot App Code:
I have created a sample Springboot App setup in GitHub. Click here to access code base in GitHub.
Jenkins pipeline will:
- Automate maven build(jar) using Jenkins
- Automate Docker image creation
- Automate Docker image upload into Azure container registry
- Automate Springboot docker container Deployments to Azure Kubernetes Cluster using Helm charts
Watch Steps in YouTube Channel:
1. AKS cluster needs to be up running. You can create AKS cluster, ACR Repo using shell script provided in my website.
Go to Jenkins-> Manage Jenkins. Create credentials.
Enter ID as ACR and enter some text for description and Save
Execute the below command to get kubeconfig info, copy the entire content of the file:
2. Jenkins instance is up and running
3. Make sure to Install Docker, Docker pipeline
4. Install Docker in Jenkins and Jenkins have proper permission to perform Docker builds
5. Install Kubectl on Jenkins instance
6. ACR is also setup in Azure cloud.
7. Make sure AKS has pull access from ACR
8. Dockerfile created along with the application source code for springboot App.
9. Install Azure CLI on your local machine. (We will be creating the AKS cluster from our local machine)
10. Helm installed on Jenkins instance
The Code for this video is here:
Make sure you fork my repo https://github.com/akannan1087/docker-spring-boot
Step # 1 - Create Credentials to connect to ACR from Jenkins
Go to Azure Portal console, go to container registry
Settings--> Access keys
Get the username and password
Enter ID as ACR and enter some text for description and Save
Step #2 - Create Credentials for connecting to AKS cluster using Kubeconfig
Go to Jenkins UI, click on Credentials -->
Click on Global credentials
use secret file from drop down.
Click on Global credentials
Click on Add Credentials
use secret file from drop down.
you should see the nodes running in EKS cluster.
kubectl get nodes
cat ~/.kube/config
Open your text editor or notepad, copy and paste the entire content and save in a file.
We will upload this file.
Enter ID as K8S and choose File and upload the file and save.
Step # 3 - Create a pipeline in Jenkins
Create a new pipeline job.
Step # 4 - Copy the pipeline code from below
Make sure you change values as per your settings highlighted in yellow below:
Make sure you change values as per your settings highlighted in yellow below:
pipeline {
tools {
maven 'Maven3'
}
agent any
environment {
//once you create ACR in Azure cloud, use that here
registryName = "myacrrepo531"
//- update your credentials ID after creating credentials for connecting to ACR
registryCredential = 'ACR'
dockerImage = ''
registryUrl = 'myacrrepo531.azurecr.io'
}
stages {
stage('checkout') {
steps {
checkout([$class: 'GitSCM', branches: [[name: '*/main']], extensions: [], userRemoteConfigs: [[url: 'check_out_from_your_repo_after_forking_my_repo']]])
}
}
stage ('Build') {
steps {
sh 'mvn clean install'
}
}
stage ('Build Docker image') {
steps {
script {
dockerImage = docker.build registryName
}
}
}
// Uploading Docker images into ACR
stage('Upload Image to ACR') {
steps{
script {
docker.withRegistry( "http://${registryUrl}", registryCredential ) {
dockerImage.push("$BUILD_NUMBER")
}
}
}
}
stage ('Helm Deploy') {
steps {
script {
sh "helm upgrade ver-$BUILD_NUMBER --install mychart --namespace helm-deployment --set image.tag=$BUILD_NUMBER"
}
}
}
}
}
Step # 5 - Build the pipeline
Step # 6 - Verify deployments in AKS
Execute the below command to list the helm deployments:
helm ls -n helm-deployment
kubectl get pods -n helm-deployment
kubectl get services -n helm-deployment
Steps # 7 - Access Springboot App Deployed in AKS cluster
Once deployment is successful, go to browser and enter above load balancer URL mentioned above
You should see page like below:
Clean up the Cluster:
To avoid charges from Azure, you should clean up unneeded resources. When the cluster is no longer needed, use the az group delete command to remove the resource group, container service, and all related resources.
az group delete --name myResourceGroup --yes --no-wait
No comments:
Post a Comment