Discussed about rolling update, recreate , blue/green and canary deployment in kubernetes github link :- github.com/Dee... video on liveness and readiness probe - • readiness probe and li... Happy learning
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 !!!
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 {}
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 ?
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
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! :)
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 :)
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 :) :)