Most Common Kubernetes Deployment Strategies (Examples & Code)
Вставка
- Опубліковано 18 чер 2024
- 🔴 - To support my channel, I’d like to offer Mentorship/On-the-Job Support/Consulting - me@antonputra.com
▬▬▬▬▬ Experience & Location 💼 ▬▬▬▬▬
► I’m a Senior Software Engineer at Juniper Networks (12+ years of experience)
► Located in San Francisco Bay Area, CA (US citizen)
▬▬▬▬▬▬ Connect with me 👋 ▬▬▬▬▬▬
► LinkedIn: / anton-putra
► Twitter/X: / antonvputra
► GitHub: github.com/antonputra
► Email: me@antonputra.com
▬▬▬▬▬▬ Related videos 👨🏫 ▬▬▬▬▬▬
👉 [Playlist] Kubernetes Tutorials: • Kubernetes Tutorials
👉 [Playlist] Terraform Tutorials: • Terraform Tutorials fo...
👉 [Playlist] Network Tutorials: • Network Tutorials
👉 [Playlist] Apache Kafka Tutorials: • Apache Kafka Tutorials
👉 [Playlist] Performance Benchmarks: • Performance Benchmarks
👉 [Playlist] Database Tutorials: • Database Tutorials
▬▬▬▬▬▬▬ Timestamps ⏰ ▬▬▬▬▬▬▬
0:00 Intro
1:35 Kubernetes Rolling Update Deployment
8:12 Kubernetes Recreate Strategy
10:19 Kubernetes Blue/Green Deployment
17:05 Kubernetes Canary Deployment
▬▬▬▬▬▬▬ Source Code 📚 ▬▬▬▬▬▬▬
► GitHub: github.com/antonputra/tutoria...
#kubernetes #devops #cloud - Наука та технологія
🔴 - To support my channel, I’d like to offer Mentorship/On-the-Job Support/Consulting - me@antonputra.com
Thanks! Usually all videos show these deployment strategies conceptually, but you demonstrated how it's actually done! Big thanks!
Never seen before such clear explanation..Hatts off 👍👍
thanks a lot!
В нетленку!!!! 🔥🌟🔥🌟🔥🌟🔥Сердечно благодарю, Антон!!! 🙏❤🙏❤🙏❤🙏
spasibo=)
this is amazing, well explained!
This is always an exciting topic, a fantastic video, thanks for sharing this quality of content!!!
thanks!
I love your explanations, very clear, awesome examples, and straight to the point. Thank you for your hard work!!
Thank you!
awesome structured video, thanks!
Thank you!
Thanks for sharing your knowledge, your explanation is up to the mark.
Thank you!
Great Content, Thanks Sir, best IT teacher, learned a lot from You! ❤
Thank you❤
Wow! this is really very help full K8s Deployment contents for when we call a service api and it show "Service Upstream problem". Sir your content is Unique on the k8s Tutorials. 💝
Thank you very much for all your content.
my pleasure
underrated channel
Thanks a lot Anton!
welcome!
you deserve lots of subscribers, thank you for sharing your knowledge.
Thanks :)
Anton my man! Quality contents as usual
Thank you!
Masterclass. Thanks Teacher!
Thank you!
great explanation! thankyou for doing this
thanks!
otlicino, spasibo!
pojaluysta!
very good explained as always. thanks a lot for all your videos
🫡
This is so well explained.
You also added in examples that we can understand and apply in the real world.
Great thanks for sharing such knowledge. subscribed.
thanks!
Thanks
very nice explanation and helpful , thx a lot
thank you!
These tutorials are amazing
thanks you!!
Thanks!
Thank you for support!
Hi, i m fron india, and your teaching style is very good. I'm waiting for more videos for kubernates and terraform with azure
Thanks, Azure is coming soon =)
Love your content! What workstation you have? ARM MacBook laptop?
Thanks, yes Apple M1 Pro
Thank you! Can we balance traffic between services in the different namespaces by istio with flagger or something?
It's not common, what's your use case? I'll see if I can test istio with cross namespace virtual service
it would be great. There are three services in different namespaces stage, prod and green. I need to balance traffic between them. this can be done using ingress canary, but in this case, if the application crashes, it is not excluded from balancing and the user will receive either 200 or 503.
thanks for the video, question: what is a deployment strategy like when there are database migrations and how do you plan a rollback in this type of situation?
it's case by case but in general try to make migration backward compatible
Yes, although as the company grows and technology teams are formed, it becomes necessary to implement policies to ensure that these methodologies are followed by everyone on the team. So, in the case of databases, what would the policies be like? One policy could be: modifying a field in the database involves the following steps: 1) Create a new field with a different name, migrate, run a test; 2) Ensure new information is recorded in the new table, keeping new records in both tables, run a test; 3) Migrate data from one table to another, run a test; 4) Ensure new information only enters the row, run a test; 5) Delete the old table; 6) End.?
sir do you have video about kubernetes pod termination and sig term? how the pod gracefully terminated specially in prod?
I don't, but there is a hook that you can use and provide a custom command to execute before terminating the pod - kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/
plz make a DETAILED video on Cortex.
Love your videos. Both prometheus operator videos helped me out a lot
Sure will do!
So, in canary deployment as we can forward 10% of traffic to new version. Can we make sure that only our team users can access this new version 10% . And end-users or customer should access 90% of old version.
Is it possible
Sure, if you use native K8s objects, you would add an additional label to the deployment, for example, "deployment: canary". Then, you'd create another service that selects only canary pods, similar to the blue/green example. In Flagger, this is already implemented, and when you run a test, it will target only the canary.
another question: how do we deploy a pod if its task or actions are executed internally and not by a request from a user?
do you mean like a data pipeline (kafka consumer/producer), you can automate and it's much harder and that's why most examples focused on request based apps :)
I have a question, why are there 2 pods being created in 5:08 minute while the specified maxSurge is 25% from 4 replicas which should be 1
yes, 25% is 1 pod (4 total), but k8s terminated at the same time 1, so total 5
I’m using argocd rollout but I don’t know what’s the main difference between native k8s deployment strategy and Argo d rollout
It uses default rolling-update unless you explicitly update it in the yaml
ArgoRollouts can do canary and bluegreen
'Promo SM'
you should enable "join" so we can support you
Thanks will do =)