deploying micro services application on kubernetes using helm charts

[@knrguy34]

Thanks deekshit please do a video on end to end application deployment which covers devops major tools like git jenkins, python scripting ( if needed) docker ansible/kubernetes, monitoring & logging. such that one can gain full knowledge on where to improve the skills. you can do kind of series like each part per every one/two weeks as per ur schedule. most of ppl benifit from this

[@maheshbabu8078]

Thanks Tyson For asking my concern also deekshit please do one viedo on end to end deployment

[@DeekshithSN]

Hey, Thanks for watching, I have already a playlist with name end to end project you can refer that it might help you 😊

[@maheshbabu8078]

@@DeekshithSN Thank you

[@interestingdatascience8057]

Hi Deekshith, thanks a lot for sharing this video, it will be great if you can show how to access the frontend application using INGRESS because that's the actual realtime use case which will help us in our project

[@DeekshithSN]

Thank you ☺️ Will do video on it

[@pasindunawodya9843]

Thank you for your well explanation. This is the only video I found that solve my problems. KEEP GOING. Best of luck.

[@valentinetong4813]

Brief and rich. Beautiful!!!

[@DeekshithSN]

Thank you for watching :)

[@prakashsingh3336]

Very easy and explained video. Thank you so much. 👍

[@souza8077]

Thanks for the awesome video! Could you please make a video about the "tpl" language in helm charts used in "helpers.tlp" file? Explaining the sintax and how to do the logics behind this language.

[@nikhithachandana]

Please make a video on how to make a common helm chart for multiple microservices.

[@DeekshithSN]

Thanks for watching, this video might help you kzbin.info/www/bejne/kKeqaaWcf5mLrq8

[@vikrantmehrol1950]

it is great explanation

[@DeekshithSN]

I am glad you liked it 😊

[@chiranjeevirachapudi4412]

very good explanation thank you so much

[@sreenuthota5482]

Hey deekshit superb explanation, can u do a complete video on ingress in k8s

[@mohammadzahid4390]

Thanks @deekshith for the awesome explanation. I have just one question. What problem did helm solved in this case of microservice? Let's say for each microservice you created 1 yaml file having deployment, service, config etc. with actual values that they need. This is exactly what the helm is doing. How exactly does helm solve my problem of DRY if you will be creating a helm chart for each microservice ? The amount of effort needed is same.

[@DeekshithSN]

Thanks for watching video, I am glad that this video was useful to you 😊 Helm is package manager for kubernetes manifest files, helm can be very helpful when your application is complex, same helm chart has to be deployed accross multiple environments with only few config changes, situations like if it's dev env need to create only few objects and if it's higher env then need to create all the objects. Above are few situation helm can be useful. If you want to learn helm from basics then refer - kzbin.info/aero/PLLYW3zEOaqlKYku0piyzzLFGpR9VpPvXR Also I have discussed how helm can be used in prod scenarios - kzbin.info/www/bejne/kKeqaaWcf5mLrq8

[@souza8077]

Thanks for your awesome explanation Make one video about the .tpl language used in helm charts, how it works and its sintax

[@ayencoscolfield3312]

Thanks my friend for another awesome video

[@DeekshithSN]

Thanks for the visit!!

[@_mr.engineer]

Awesome explanation 👏👌👍😀

[@sarathchandra6]

Your videos are very useful.Good stuff👍

[@DeekshithSN]

Glad you like them!

[@mustaphag]

Excellent work. Keep up the good work

[@sureshsg4060]

good stuff bro, do we have Knative video?

[@AnkitSharma-ph9kx]

hi all i am facing one query while implemeting helm charts . i have 3 helm charts seperately for 3 service namely s1,s2,s3 now i want to connect the s1 to s2 by providing the service name of s2 in s1 as the connections can be established through service name. but the service name is charts2.fullname in helm chart of s2 so how to tranfer the value of service name s2 in the helm chart of s1. or in short how to access the chart.fullname of s2 in the s1 helm chart. please answer

[@christymariam51]

Thankyou so much...this video helped!!💟

[@suryasharma3399]

thanks

[@aravindersuram6920]

In helm when we developed the helm chart the namespace is default I want to change the namespace without using helm install -- namespace it should create in template and it should install default when we Install the helm chart can you suggest any way

[@Castisland]

Nicely explained..

[@DeekshithSN]

Thank you 😊

[@GuruPrasad-be9ff]

I have two helm charts, each chart having one microservice, now my concern is I want to integrate two helm charts with one helm chart, like when I run helm install mychart, both services needs to run at a time Can you please help me on this.. Thanks in advance

[@abhishekmishra285]

thanks for sharing @deekshith. if i want to deploy such a appliaction using helm and argocd on kubenetes, then how can we replace "values.yml" with some other name. please help me out.

[@NotSureOf]

I dont get the point, why do we need helm charts for each micro service? we can do that by simple YAML file. just taking config through labels we need to go to helm? someone, please clarify this. thanks

[@santhoshs6662]

Helm Chart adavantages ? or why we need to move to helm chart ? Simplified deployment: Helm charts provide a simple and standardized way of deploying complex applications on Kubernetes. They help to reduce the amount of time and effort required to deploy an application by encapsulating all the necessary components, such as configuration files, Kubernetes manifests, and dependencies, into a single package. Scalability: Helm charts allow you to easily scale your application by deploying multiple replicas of the same chart. This can be done by simply changing the replica count value in the Helm chart's configuration file. Reusability: Helm charts can be shared and reused across different teams and environments. This means that you can easily deploy the same application in different environments, such as development, staging, and production, by simply adjusting the configuration files. Versioning and Rollbacks: Helm charts support versioning, which makes it easy to roll back to a previous version of the application if there are any issues with the current deployment. This can be done by simply specifying the version number of the chart during deployment. Community Support: Helm is an open-source tool with a large and active community. This means that there are many pre-built Helm charts available for popular applications and services, which can save you time and effort in deploying and managing your applications.

[@aravindersuram6920]

Can you explain pvc in helm chart

[@senthilkumar5129]

Thank you

[@Shakeersyed99499]

Tq bro

[@aravindersuram6920]

blue green deployment in helm

[@DeekshithSN]

Thanks for watching, Blue green is deployment strategy I guess nothing to do with helm charts

[@aravindersuram6920]

Yes we can used the Argocd for blue and green deployment in helm

[@Twox27]

app name?

[@DeekshithSN]

Thanks for watching, there is no app name as such. It's sample app to show the demo on microservice deployment