HELM Chart Deployment to Kubernetes using Azure DevOps CICD

HELM Chart Deployment to Kubernetes using Azure DevOps CICD
GitHub Link:
Sample API:
github.com/iqrabismi/CZcamsD...
Fig Sample:
github.com/iqrabismi/FIG
#CICD #Azure #Kubernetes #helm #AKS

[@skg7958]

Thank you! so much for explaining in detail each step. Very helpful!

[@mp40fan]

Thank you! Very helpful video!

[@kbrajeshwaran]

Much Appreciated your efforts

[@adityanarayan7658]

It was really helpful... well said... Thankyou!

[@jakejacobs9213]

Very Helmful😊. thank you.

[@louiegietrinanes4798]

❤️❤️❤️ thank you

[@breaktimeclips]

Very useful content

[@technicallearning3652]

Good one Sir.

[@vigneshsweekaran2096]

Very good video

[@kavacham222]

Thanks for the video. I have one question like who will write the yaml file which are related to Helm.like chart.yaml and values.yaml. as far as i know devops persin also wrtie the dep.yml, service yml, etc. I want to know wgo will write those yaml file

[@ajitrepal7966]

Thanks. This was really helpful video. What need to be done if ACR and AKS are in different subscriptions?

[@techpark2111]

Well in that case you need to create two different service principle and at the time of pipeline creation you need to select correct service principle name, you will be getting the acr and aks name in the dropdownlist.

[@Orphen86]

Thanks , this is a very helpful, but I have a one problem, in realese helm upgrade throwing a exception for time out this is a Error: timed out waiting for the condition this is a command (elm upgrade --namespace default --install --wait --set image.tag=6 preubasdevapi /home/vsts/work/r1/a/_PruebasDEV_API_CI/pruebasdevapi/helm-6.tgz) what do you thing about that?

[@itorisaias9031]

discovered something about ?

[@Orphen86]

@@itorisaias9031 noup, I continue working in this process, I'm working in CD, but it is the same error.

[@itorisaias9031]

@@Orphen86 I removed the await flag and passed succeed, but I'm still testing more

[@azterixz1234]

Thank you so much for this video. This was exactly what I was looking for.
How do we deploy multiple micro services using then helm charts?

[@techpark2111]

Lets say there are 4 microservices, you can create a single CICD Pipeline to manage all 4 microservices, but in this case you might face difficulty to manage. My recommendation would be create 4 different CICD pipeline. The easy way to create other pipeline would be, you can download the json file of your pipeline and import the downloaded file again and then change the desired congratulations and other things.

[@techpark2111]

You create different HELM chart for different microservices.

[@azterixz1234]

@@techpark2111 Thank you. Let me try this out. We cant deploy multiple helm charts in one CI/CD pipeline is it? Whats currently happening for me is that only the last helm chart is being deployed and all the previous deployments are being deleted. Its strange that its working that way

[@techpark2111]

Probably you are giving same release name for all microservices, if this is the case, then, please give different release name for every microservices. It may resolve your problem.

[@azterixz1234]

@@techpark2111 Thanks for the quick reply. Trying it now. Will keep you posted if it works

[@pedavea2]

Thank you so much for putting this together, I am getting error "##[error]Error: Invalid Semantic Version" at helm package step.

[@pedavea2]

I was able to pass this step

[@anuragkunchamwar8465]

can you share the github link, its missing

[@techpark2111]

please check the description section. you will get it there.

[@gijith]

Thank you. It was really helpful.