Thank you so much sir. finally i able to understand all these deployment strategy with practical... also sir i have a suggestion for you that , you can use to demonstrate the real time service bouncing for one pod to another and versioning also. Again thanks a lot !!!
Thanks for the usefull video.Well explained..👍 can you please update if we are perform the blue/green deployment how can we handle live connection and stick bit session?
Thanks for watching I am not aware of live connection and stick bit session, but what I can make out those words is live connection --> about persistence of data and stick bit session --> routing request all these deployment strategies are good to non persistence applications not for databases, if we have database then the deployment should point to old database. routing in blue green is very simple your just changing the service configurations to point new deployments also you can make use service mesh tools to handle request in better way Hope this clarifies your douts :) :)
Hi Vaibhav, Please refer the pros and cons of each strategy mentioned at the start of the video and see which is best fit for your use case. As Akshay mentioned, rolling update is max used, that's is correct as it is a default one, but it is advised to pick the one which is best fit for your use case. Happy Learning! :)
Hi.. thanks for the tutorial.. its very helpful. However when you say the QA team verify the version and given a go ahead, can you tell me which url they hit ? As the same url and port is already used by the old version. This makes more difficult when we have IP address and port bind to the DNS Name... Can you tell me how to get the URL for new version ?
I am facing an error while running patch command in blue/green strategy: Error from server (BadRequest): json: cannot unmarshal string into Go value of type map[string]interface {}
Except Recreate, all other deployment strategies does not have down time. Based on your requirement you need to choose any in rolling update, blue green or canary. also please have look into pros and cons of each deployment strategy.
oh in that case use blue/green or canary in blue/green once your deployment is fine then you will redirect the service to new deployment until then your old deployments will be serving user requests in Canary some traffic will be sent new deployment if it works then full redirect the request and there are other deployment strategies as well but i have not worked on them :)
Mac is ideal for Devops, if you budget go for it. Else in windows many options are there, personally I use asus gaming laptop Below is the link - www.flipkart.com/asus-tuf-gaming-f15-core-i5-10th-gen-8-gb-512-gb-ssd-windows-10-home-4-graphics-nvidia-geforce-gtx-1650-ti-144-hz-fx506li-hn271ts-laptop/p/itme14aa4095ad4c?pid=COMGFVWMZXNEDHFB&lid=LSTCOMGFVWMZXNEDHFBKVM1HI
Thank you for detailed explanation followed by demo without any rush. Appreciate you help as always, Sir!
Glad it was helpful!
Thank you so much sir. finally i able to understand all these deployment strategy with practical... also sir i have a suggestion for you that , you can use to demonstrate the real time service bouncing for one pod to another and versioning also. Again thanks a lot !!!
Thanks for watching, will consider suggestions in coming videos :)
very good explanation from basic ...thank you
Execellent Explained and very well showed visually the LAB thanks a Lot
You are welcome!, I am Glad that it helped you :)
@@DeekshithSN any email id? How to contact with you ?
you can send mail at deekshithsn@gmail.com
Congratulations. Content is great and well explained. Sound quality can be improved, I also had a hard time with the enunciation.
Thanks for watching, will consider your feedback for upcoming videos 😊
Love your Demo. Its great.
good video, but for B-G and Canary examples are not proper. This is not the way the real production deployment shall work.
Very helpful - Thank you !!
PLZ DO UPLOAD COMPLETE KUBERNETES SERIES FROM SCRATCH TO ADVANCED
Thanks for watching, will plan to do the same
Well explanation with more info..
Thank you sujay :)
Thanks for the usefull video.Well explained..👍 can you please update if we are perform the blue/green deployment how can we handle live connection and stick bit session?
Thanks for watching I am not aware of live connection and stick bit session, but what I can make out those words is live connection --> about persistence of data and stick bit session --> routing request
all these deployment strategies are good to non persistence applications not for databases, if we have database then the deployment should point to old database.
routing in blue green is very simple your just changing the service configurations to point new deployments also you can make use service mesh tools to handle request in better way
Hope this clarifies your douts :) :)
hi deekshith... thanks for the detail video.
would like to know which strategy is usually/max used while deployment?
Rolling upgrade
Hi Vaibhav,
Please refer the pros and cons of each strategy mentioned at the start of the video and see which is best fit for your use case. As Akshay mentioned, rolling update is max used, that's is correct as it is a default one, but it is advised to pick the one which is best fit for your use case. Happy Learning! :)
👌👌👌👌
Hi.. thanks for the tutorial.. its very helpful. However when you say the QA team verify the version and given a go ahead, can you tell me which url they hit ? As the same url and port is already used by the old version. This makes more difficult when we have IP address and port bind to the DNS Name... Can you tell me how to get the URL for new version ?
for this to handle you need to know service mesh tools like istio, using which we can route the requests
I am facing an error while running patch command in blue/green strategy:
Error from server (BadRequest): json: cannot unmarshal string into Go value of type map[string]interface {}
From the error i can make out its syntax issue, if you share yml file then i can help you out :)
Did you have situation: app-v1 and app-v2 has the diffirence database's structure . How to update deployment with no downtime ?
Except Recreate, all other deployment strategies does not have down time. Based on your requirement you need to choose any in rolling update, blue green or canary. also please have look into pros and cons of each deployment strategy.
@@DeekshithSN seems you missed my conditions about changing database for each app version
oh in that case use blue/green or canary
in blue/green once your deployment is fine then you will redirect the service to new deployment until then your old deployments will be serving user requests
in Canary some traffic will be sent new deployment if it works then full redirect the request and there are other deployment strategies as well but i have not worked on them :)
Current version in blue and updated is green
Please explain about the service and how to keep it high available
Sure i will do video on services and high availability , thanks a ton for suggestion :)
Good explanation
Thank you @saviour king , please do watch my other video :)
Hi Deekshith can you tell me which laptop is good for Devops... Oct 2022
Mac is ideal for Devops, if you budget go for it.
Else in windows many options are there, personally I use asus gaming laptop
Below is the link - www.flipkart.com/asus-tuf-gaming-f15-core-i5-10th-gen-8-gb-512-gb-ssd-windows-10-home-4-graphics-nvidia-geforce-gtx-1650-ti-144-hz-fx506li-hn271ts-laptop/p/itme14aa4095ad4c?pid=COMGFVWMZXNEDHFB&lid=LSTCOMGFVWMZXNEDHFBKVM1HI
@@DeekshithSN we are waiting for your videos when it will come ...
well explained
Thanks for watching, glad you liked it :)
Can you please upload a video on common issues faced in kubernetes
Sure will do on that soon