Setup AKS Cluster & Deploy Springboot Docker Container to AKS Cluster using Helm and Azure Pipeline
Vložit
- čas přidán 3. 05. 2023
- www.coachdevops.com/2023/04/h...
Implementation steps:
Create a resource group, AKS cluster and Azure container registry
Provide pull access for AKS to pull image from ACR
Create a namespace for helm deployment
Create a helm chart for spring boot app
Create a build pipeline to automate docker image
Customize pipeline with helm package tasks
Create a release pipeline
Customize pipeline with helm upgrade tasks
Run the pipeline to deploy springboot app into AKS
Verify deployments in the namespace in AKS
Use kubectl port forward to access app locally
Access the app in the browser
Pre-requisites:
Azure CLI is installed on your local machine.
Helm installed
kubectl installed
Azure subscription, click here if you don't have one.
AKS cluster needs to be up running. You can create AKS cluster, ACR Repo using shell script provided in my website.
Azure DevOps project dashboard in dev.azure.com/
Dockerfile created along with the application source code for springboot App.
Make sure AKS has pull access from ACR
Pipeline Implementation Steps:
Part 1 - Create Azure Build pipeline for building Docker image, uploading image into ACR and packaging helm chart.
Part 2 - Create Azure Release pipeline for deploying Springboot Docker containers into AKS using helm upgrade task. - Věda a technologie
Nice work and presentation with code and explanation
Glad you liked it
Very helpful tutorial, thanks for sharing!
Glad it was helpful!
Its very helpful but please do a video using YAML pipeline, now a days everyone using YAML
This is really concise and most of concepts covered. Would be great if github actions can be covered. Thanks a lot sir.
Noted, Glad you liked this video. GitHub actions also will be covered in upcoming videos
here you go on GitHub Actions --> czcams.com/play/PLJwvtUqYDmA7_mSdCJHtPmtxe_D3NwXHg.html
Excellent!!!
I am getting
It lollks like you are trying to use a client-go credentials plugin that is not isntalled.
Kubelogin is not installed which is required to connect to AAD enabled cluster. in case of helm Upgrade task in release pipeline. And I donot have agent installed machine access.
Brother please do the video with yaml pipeline for the same thing ASAP
I'm getting an error during Hem Upgrade task for client rate limiter Wait returned an error: context deadline exceeded
this can happen due to various issues. n/w latency, issues with helm.
chart. Check Resource(cpu, memory) Usage by executing kubectl top command. and also see if you can increase time out duration for the helm operation.
.helm upgrade --timeout 10m
Hi Sir, Thanks for the video, This is not working for me currently, i am unable to find the helm package in release pipeline. Could you please help ?
It's unclear to me what I should fill in for image repository. You say "you kind of know", but how do I know mine?
Can u please create video, do the same with private hosted agent?
How to communicate agent that is hosted ( Gitlab ) with private network ?