Thank you! so much for explaining in detail each step. Very helpful!
@mp40fan
2 жыл бұрын
Thank you! Very helpful video!
@louiegietrinanes4798
2 жыл бұрын
❤️❤️❤️ thank you
@jakejacobs9213
Жыл бұрын
Very Helmful😊. thank you.
@gijith
Жыл бұрын
Thank you. It was really helpful.
@kbrajeshwaran
2 жыл бұрын
Much Appreciated your efforts
@breaktimeclips
5 ай бұрын
Very useful content
@adityanarayan7658
2 жыл бұрын
It was really helpful... well said... Thankyou!
@kavacham222
5 ай бұрын
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
@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
@vigneshsweekaran
2 жыл бұрын
Very good video
@technicallearning3652
2 жыл бұрын
Good one Sir.
@azterixz1234
2 жыл бұрын
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
2 жыл бұрын
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
2 жыл бұрын
You create different HELM chart for different microservices.
@azterixz1234
2 жыл бұрын
@@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
2 жыл бұрын
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
2 жыл бұрын
@@techpark2111 Thanks for the quick reply. Trying it now. Will keep you posted if it works
@ajitrepal7966
2 жыл бұрын
Thanks. This was really helpful video. What need to be done if ACR and AKS are in different subscriptions?
@techpark2111
2 жыл бұрын
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.
@pedavea2
2 жыл бұрын
Thank you so much for putting this together, I am getting error "##[error]Error: Invalid Semantic Version" at helm package step.
@pedavea2
2 жыл бұрын
I was able to pass this step
@anuragkunchamwar8465
2 жыл бұрын
can you share the github link, its missing
@techpark2111
2 жыл бұрын
please check the description section. you will get it there.
Пікірлер: 29