I hope this clarifies all your questions, if not - leave a comment and I will try to answer it! If it was helpful, please leave a like and subscribe 😊 👍 Follow me on Instagram for behind the scenes content 🎬: bit.ly/2F3LXYJ 🔗 Useful Links: * kubernetes.io/blog/2020/12/02/dockershim-faq/ * kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/ ▬▬▬▬▬▬ T I M E S T A M P S ⏰ ▬▬▬▬▬▬ 0:00 - Intro 0:18 - Why has Docker been deprecated? 3:10 - Container Runtime alternatives? 4:17 - What does this change mean for YOU as a Kubernetes User? 5:07 - What does this change mean for YOU as a Kubernetes Administrator? 5:30 - when using Managed Kubernetes Service 6:32 - with self-managed Kubernetes cluster 7:58 - When do you need to take action? 8:45 - Impact on using Kubernetes locally with Minikube and Docker Desktop 9:42 - Still learn Docker? CI/CD Pipeline with Docker? 12:00 - Wrap-Up
I think what's left unanswered for me is, okay so if docker and all of its networking and etc is going away. whats taking over? how is the ipam and host-container nat going to be taken care of?
Nice video: This video just clarified the hoopla and garbage that a lot of people are throwing around. Basically nothing changes for people who are using docker tech correctly, which is proabably 98% of people out there anyways, and the benefit is kubernetes made their product more lightweight and not have to worry about the hell annoying updates of docker that happen all the time, and can break (updates are good, but annoying) Disclaimer: I am not an experienced netop/devops, my main role is developer, but I maintain servers on AWS (8 servers) for my side business, and lead netops/devops (not 100% professional, but probably better than the avg 2 yr experienced fool that has blogs online about bullcrap as I have been working with online tech for 18+ years). As for what others are saying: should I learn docker? I think the easiest answer is this: if you don't know why you are using docker, then maybe you don't use it? If you know why you want to use docker, then use it. Docker is a good choice, all others saying: this is better, that is better - yah probably 1-sided experience. Docker is easy to use, esp for beginners and THIS IS MOST IMPORTANT. If people are saying "10% faster" and stuff like that, this is pure garbage, if you know systems, you aren't concerned about 10% faster for your servers/containers, 10% would be MAYBE important for SQL server, when you are at the cusp of a breaking point of the system, but even then, you gotta change the implementation: split DBs into two servers. So rule: 10% faster means nothing, really, because you just spin up another load balanced server anyways to reduce load - these are just foolish people if they want to really make this into an issue. FASTER BY 10% DOESN'T MATTER REALLY. I will give a case where we want to use docker, and docker is good - docker runs on major OSes, and allows you to build containers (which is basically functions like a VM, without the overhead that most VMs have) - for example, we have a system where we have 4 different servers, we use cloud providers and Centos 7 (screw IBM RH), to develop locally, it's great to use dockers so that we can mimic the interactions of servers right on our computer (local dev env). DOCKER IS GOOD FOR DEVS! So on production, when to use containers? You have a choice now (AWS) - use EC2 instances OR use containers. What are the differences, and benefits for each? A lot goes to having experience - if you running lightweight processes that don't do much, like the majority of nodeJs servers people write, and services which they offer, then containers are a great option on cloud providers especially, because it's cheaper to have 1-2 live and 1 backup containers, then lets say than paying for 3 servers. It's almost always safer to have several servers running than 1 super server (what happens if that hardware dies on the super server, your services are GONE). Keyword: load balancing. Now 1 type of server is our web servers, so obviously you want to load balance two or more in production. CONTAINERS COULD BE CHEAPER THAN SERVERS. Is it easier to maintain containers than lets say traditional servers? I'm going to say if you are spinning up 64 load balanced servers, it's gonna get costly, and containers makes more sense, as they were built for huge numbers. But in all small to medium network sizes of small to medium companies, or start ups, it doesn't really matter tbh. If you actually have 1K concurrent users, then containers are great! If you running even apache php servers, you could go with containers too! it's understanding the resources/performance and costs. CONTAINERS ARE GOOD IF YOU WANT TO LOAD BALANCE 100 "SERVERS" ON LOAD BALANCER. In the end, when using cloud providers, like AWS, you have a choice of deployment now - ec2 load balanced or fargate containers. As far as I am concerned, if you don't have 1k+ concurrent users, you might not necessarily use fargate (or kubernetes) and container images. But you never had to because you could always use the traditional methods of using servers. DEPENDING ON REALISTIC SCALES AND WHAT YOUR SYSTEM IS, CONTAINERS OR NON-CONTAINERS ARE VIABLE IN A LOT OF GENERAL CASES. Anyone pushing anything real hard outside of this are just "experts" in their own fields, because all container tech are about the same, docker is great for the dev process, and it's big, like in this video. But those tools AREN'T NEEDED on your production servers (docker full features) because you shouldn't be building debugging your containers on production and for sure, you shouldn't be using docker network layer AT ALL on production. DOCKER RUNNING IN PRODUCTION IS DANGEROUS (SECURITY), DON'T NEED FULL DOCKER ON PRODUCTION ANYWAYS. In the end, you just have to think of a container as a VM and you can 32/64 "servers" in containers on a computer, think of it that way. It's probably safer and better than running 1 service on a computer (in general), which may crash in an edge case or some other weird issue (which maybe due to degradation over time, bad 3rd party software).
Nana, great video. Isn't the question a bit misleading? Is it not the case that K8s are dropping support for docker shim rather than docker? The K8s support for OCI has never been in doubt and the docker obviously is compliant with OCI. K8s are not required to support individual containers but rather focus on the Open Container Initiative, which is still the case. Would you agree to that?
As someone with a self managed and on-prem K8s cluster, I will say that changing the container runtime from docker to containerd was not only fairly straight forward, but I'm also noticing better node resource availability which makes sense given the heaviness of dockershim vs natively supported cri. I will say, the process to change runtimes was not well documented as of yet, but if anyone needs assistance and is also using kubdadm to manage their on-prem clusters, just hit me up!
No matter how difficult or confusing the subject may be, Nana knows the way to break it down to make super duper easy. My 2 year old has no further questions, so do I :) Thanks Nana...
Nana, you are the best to explain the change, I was boiling the ocean to understand the change, but you nailed it in 12 min. Thanks a lot, keep up the good work. always following you.
Thanks for the rundown of the cluster changes. Having to fight to find documentation for setting a local private K8 cluster, I was set a back that this was going to be a bad thing. But with your explanation, sound like it will be smooth sailing. I would take this as a advantage to move Docker closer to the top of the stack. Containers are very slow compared to VM's(around half speed. You want VM's over containers for time sensitive services) So to take out another layer of slowness would be a bonus, if you choose the container option. If for some reason you still need the shim , it's an option.
When we watch a video we get so many questions,.how why, and this video answers all those questions the next minute/seconds... Thank you so much. Subscribed!!
Just brilliant Nana. Keep up the good work !. I have referred a couple of your videos and became your big fan. The way you explain the concept is just amazing. God bless you.
Hi Nana, just FYI, u mentioned in the video that EKS has adopted containerd as the container runtime, which is not 100% the case, to be precise. EKS for Fargate has adopted containerd, but not for EKS for EC2.
It's the first time I see your channel and I'm really impressed by the quality of your explanations and the way you're presenting them. Pleased continue this great work. Thank you.
Bird's eye view of the recent K8's announcement, there were articles that mislead (for various reasons) "Docker" (instead of Dockershime) being dropped.
There is still going to be an issue. The docker-in-docker pattern will no longer work in Kubernetes, because there is no Docker engine underneath and I don't think that's something criO or containerD can do alone. The Docker images are OCI compliant but the Docker engine isn't, and that's the whole problem Kubernetes are having - the engine, and hence its removal. So, if you're using /var/run/docker.sock in ur cluster, that's going to break.
Fantastic video! Although, a correction around 11:30 : Actually, Docker doesn't comply to OCI. That's why, dockershim (which is OCI compliant) was used in the past (and still is used) to compensate for that (because kubernetes CRI must be OCI compliant). If docker would ve been OCI compliant, then there wouldn't ve been any need of dockershim on k8s's side. But now, with the new update, kubernetes can directly use containerd as its CRI because containerd is OCI compliant. Similarly, it can use crio too because it is also OCI compliant. Apart from this, the video was fab. It covered all the required and relevant details. Good job :D
Ok, does that mean it is not usefull to learn docker because it isn´t OCI compliant? I mean Nana said, you can still learn Docker, because the images that docker produce are still able to run in a k8s cluster. Am i right?
@@affemakla6884 when did I suggest to not learn docker? I just emphasized on a point which might have been useful to atleast one person going over the comments. Calm down and read my entire comment and be a little less pessimistic. Man, some people just can't bear constructive criticism provided diplomatically.
@@yash_renaissance_athlete Excuse me, i'm no native englsh speaker and in my comment should nothing, critisim or anything that could offend you, implied. It is a real question, that aims to knowing is it still usefull to learn docker(i am a beginner) because the images that docker build could still run in k8s because there OCI compliant? Again no offend!
@@affemakla6884 I m so sorry. I interpreted your tone in a wrong manner. It's tough to interpret the right kind of emotion from the bare text at times 😅. Apologies from my side. To answer your question, Yes it's absolutely useful to learn docker. Although Docker technically is not OCI compliant but still it runs over containerd (high-level container runtime) and runc (low-level container runtime) due to which it emulates an OCI compliant nature. So do check it out, it's extremely useful to learn it.
Thank you for your explanation! I know a bit of docker and I didn't already start to study kubernetes. This video was clear even to me that I don't know anything about it. I'll keep going this journey in the docker+kubernets world then!
Thanks a lot for wrapping it up meticulously. I love to watch your videos. They are very helpful. You will soon be one of the popular teachers on TH-cam reaching 100s of thousands of subscribers. Viel Erfolg ;-)
Yet another cristal clear straight to the point video, bravo! which leaves me begging for others, specifically on the container runtime landscape. I understand CRI-O or containerd can only replace Docker **within** kubernetes as container runtime, i.e that can't be used to build or run a standalone containerized workload --> is that correct? more generally, some intro videos on docker alternatives will be more than welcome : how to install them to set-up a k8S cluster, how to configure the latter accordingly, how do they work ... etc. Thanks again for the great content
I've just started learning Docker and Kubernetes (or K8s as I've just learned) and was a bit worried if this was a waste of time - until I saw your video. Thank You :-)
I am a developer and have no idea what are Kubernetes. I use docker containers (by docker-compose) the last couple of years everyday. The video is an interesting into to Kubernetes for me. Thanks!
Woow, the details you provide is an excellent, I'd love your videos Nana. I appreciate you to making this video, and sharing. Keep on uploading new videos. You're a good teacher. Thank you.
Thanks a lot, I opened the video a bit scared about the change, but you basically answered all the questions I had, especially about CI/CD. Excellent video!
Thanks! I will publish more infos once the bootcamp is finished and up for sale including a dedicated video about it on TH-cam 😊 But in the meantime, you can of course write your questions to techworld-with-nana@nnsoftware.at and I will try to answer them asap.
Thanks for resolving all doubts .... amazing explanation ... now im not worried about running Docker images in Kube clusters...the CI CD Docker pipelines will run the same way
Docker is still good for development as it ships with everything you need to build a fixed, repeatable environment. And docker uses containerd, so if you learn about docker, you learn about containerd anyway.
But after pulling several docker image to Kubernetes node , how to delete those image without docker install, like how we are docker rmi , please suggest solution to delete docker images in my k8's master node , i am using contained now
Hey, I hope you are doing good. My doubt is whether can we still use docker containers during development and later during production make the conversion or whatever to deploy. I have very little knowledge in docker and still learning. I haven't even get started with kubernetes too, I just know few commands. If my question feels dump please ignore it :)
I hope this clarifies all your questions, if not - leave a comment and I will try to answer it!
If it was helpful, please leave a like and subscribe 😊 👍
Follow me on Instagram for behind the scenes content 🎬: bit.ly/2F3LXYJ
🔗 Useful Links:
* kubernetes.io/blog/2020/12/02/dockershim-faq/
* kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/
▬▬▬▬▬▬ T I M E S T A M P S ⏰ ▬▬▬▬▬▬
0:00 - Intro
0:18 - Why has Docker been deprecated?
3:10 - Container Runtime alternatives?
4:17 - What does this change mean for YOU as a Kubernetes User?
5:07 - What does this change mean for YOU as a Kubernetes Administrator?
5:30 - when using Managed Kubernetes Service
6:32 - with self-managed Kubernetes cluster
7:58 - When do you need to take action?
8:45 - Impact on using Kubernetes locally with Minikube and Docker Desktop
9:42 - Still learn Docker? CI/CD Pipeline with Docker?
12:00 - Wrap-Up
I think you did not clearly answered to the question: "Should ppl learn/use docker or move forward and use containerd or cri-o?"
I think what's left unanswered for me is, okay so if docker and all of its networking and etc is going away. whats taking over? how is the ipam and host-container nat going to be taken care of?
Nice video: This video just clarified the hoopla and garbage that a lot of people are throwing around. Basically nothing changes for people who are using docker tech correctly, which is proabably 98% of people out there anyways, and the benefit is kubernetes made their product more lightweight and not have to worry about the hell annoying updates of docker that happen all the time, and can break (updates are good, but annoying)
Disclaimer: I am not an experienced netop/devops, my main role is developer, but I maintain servers on AWS (8 servers) for my side business, and lead netops/devops (not 100% professional, but probably better than the avg 2 yr experienced fool that has blogs online about bullcrap as I have been working with online tech for 18+ years).
As for what others are saying: should I learn docker? I think the easiest answer is this: if you don't know why you are using docker, then maybe you don't use it? If you know why you want to use docker, then use it. Docker is a good choice, all others saying: this is better, that is better - yah probably 1-sided experience. Docker is easy to use, esp for beginners and THIS IS MOST IMPORTANT.
If people are saying "10% faster" and stuff like that, this is pure garbage, if you know systems, you aren't concerned about 10% faster for your servers/containers, 10% would be MAYBE important for SQL server, when you are at the cusp of a breaking point of the system, but even then, you gotta change the implementation: split DBs into two servers. So rule: 10% faster means nothing, really, because you just spin up another load balanced server anyways to reduce load - these are just foolish people if they want to really make this into an issue. FASTER BY 10% DOESN'T MATTER REALLY.
I will give a case where we want to use docker, and docker is good - docker runs on major OSes, and allows you to build containers (which is basically functions like a VM, without the overhead that most VMs have) - for example, we have a system where we have 4 different servers, we use cloud providers and Centos 7 (screw IBM RH), to develop locally, it's great to use dockers so that we can mimic the interactions of servers right on our computer (local dev env). DOCKER IS GOOD FOR DEVS!
So on production, when to use containers? You have a choice now (AWS) - use EC2 instances OR use containers. What are the differences, and benefits for each? A lot goes to having experience - if you running lightweight processes that don't do much, like the majority of nodeJs servers people write, and services which they offer, then containers are a great option on cloud providers especially, because it's cheaper to have 1-2 live and 1 backup containers, then lets say than paying for 3 servers. It's almost always safer to have several servers running than 1 super server (what happens if that hardware dies on the super server, your services are GONE). Keyword: load balancing. Now 1 type of server is our web servers, so obviously you want to load balance two or more in production. CONTAINERS COULD BE CHEAPER THAN SERVERS.
Is it easier to maintain containers than lets say traditional servers? I'm going to say if you are spinning up 64 load balanced servers, it's gonna get costly, and containers makes more sense, as they were built for huge numbers. But in all small to medium network sizes of small to medium companies, or start ups, it doesn't really matter tbh. If you actually have 1K concurrent users, then containers are great! If you running even apache php servers, you could go with containers too! it's understanding the resources/performance and costs. CONTAINERS ARE GOOD IF YOU WANT TO LOAD BALANCE 100 "SERVERS" ON LOAD BALANCER.
In the end, when using cloud providers, like AWS, you have a choice of deployment now - ec2 load balanced or fargate containers. As far as I am concerned, if you don't have 1k+ concurrent users, you might not necessarily use fargate (or kubernetes) and container images. But you never had to because you could always use the traditional methods of using servers. DEPENDING ON REALISTIC SCALES AND WHAT YOUR SYSTEM IS, CONTAINERS OR NON-CONTAINERS ARE VIABLE IN A LOT OF GENERAL CASES.
Anyone pushing anything real hard outside of this are just "experts" in their own fields, because all container tech are about the same, docker is great for the dev process, and it's big, like in this video. But those tools AREN'T NEEDED on your production servers (docker full features) because you shouldn't be building debugging your containers on production and for sure, you shouldn't be using docker network layer AT ALL on production. DOCKER RUNNING IN PRODUCTION IS DANGEROUS (SECURITY), DON'T NEED FULL DOCKER ON PRODUCTION ANYWAYS.
In the end, you just have to think of a container as a VM and you can 32/64 "servers" in containers on a computer, think of it that way. It's probably safer and better than running 1 service on a computer (in general), which may crash in an edge case or some other weird issue (which maybe due to degradation over time, bad 3rd party software).
]]i
Nana, great video. Isn't the question a bit misleading? Is it not the case that K8s are dropping support for docker shim rather than docker? The K8s support for OCI has never been in doubt and the docker obviously is compliant with OCI. K8s are not required to support individual containers but rather focus on the Open Container Initiative, which is still the case. Would you agree to that?
Went from "Oh Shit! we're screwed" to "Ah, this is fine" in 12 minutes.
Yep :D
As someone with a self managed and on-prem K8s cluster, I will say that changing the container runtime from docker to containerd was not only fairly straight forward, but I'm also noticing better node resource availability which makes sense given the heaviness of dockershim vs natively supported cri. I will say, the process to change runtimes was not well documented as of yet, but if anyone needs assistance and is also using kubdadm to manage their on-prem clusters, just hit me up!
200% clear, no more questions.. Great explanation.. Thank you..
Glad it was helpful for you 😊
I couldn't agree more. It's been a while since I watched a video about tech, with such a clear explanation of the topic - thx!
No matter how difficult or confusing the subject may be, Nana knows the way to break it down to make super duper easy. My 2 year old has no further questions, so do I :) Thanks Nana...
Nana, you are the best to explain the change, I was boiling the ocean to understand the change, but you nailed it in 12 min. Thanks a lot, keep up the good work. always following you.
I have never seen a topic explained with this level of clarity on TH-cam
I am in love with this women. The way she explains the things is "Next Level".
Thanks Shahvez! :)
So now you can go back to the dictionary and learn about the difference between "woman" and "women".
@@goqsane "woman" is singular and "women" is plural.
So I'm I, I am now trying not to watch 😊🙆
Simp
i love how she explained.
She awesome!!!
The Queen of DevOps, sharp as always!
Thank you Pedro! 😀
Clear, concise enough, saves people's time to look elsewhere. Nana, I support you.
Thanks for your feedback Allen, glad it's helpful :)
Thanks for the rundown of the cluster changes. Having to fight to find documentation for setting a local private K8 cluster, I was set a back that this was going to be a bad thing. But with your explanation, sound like it will be smooth sailing. I would take this as a advantage to move Docker closer to the top of the stack. Containers are very slow compared to VM's(around half speed. You want VM's over containers for time sensitive services) So to take out another layer of slowness would be a bonus, if you choose the container option. If for some reason you still need the shim , it's an option.
When we watch a video we get so many questions,.how why, and this video answers all those questions the next minute/seconds... Thank you so much. Subscribed!!
Welcome to the channel 😊 Thank you so much for your positive comment!
Just brilliant Nana. Keep up the good work !. I have referred a couple of your videos and became your big fan. The way you explain the concept is just amazing. God bless you.
My most productive 12.21 minutes of today; Thank you Nana :-)
Glad to hear :)
i wish i had discovered this channel earlier ... you got yourself a new subscriber
Hi Nana, just FYI, u mentioned in the video that EKS has adopted containerd as the container runtime, which is not 100% the case, to be precise. EKS for Fargate has adopted containerd, but not for EKS for EC2.
i am a simple man, i see Nana posts something i watch immediately :) !
😀
It's the first time I see your channel and I'm really impressed by the quality of your explanations and the way you're presenting them. Pleased continue this great work. Thank you.
Excellent as always!! How do you anticipate all the questions that can arise!! Just awesome..
😀 thank you so much! I read a lot of your comments and questions and try to answer them in the videos 😊
Whew, thank you for this video! As a newbie using docker for development this took a load off my mind.
Thanks!
I'm a beginner in Docker and a total noob in K8s, but I found your video really informative and easy to follow. The graphics are top notch!
Bird's eye view of the recent K8's announcement, there were articles that mislead (for various reasons) "Docker" (instead of Dockershime) being dropped.
So did the title of this video!
There is still going to be an issue. The docker-in-docker pattern will no longer work in Kubernetes, because there is no Docker engine underneath and I don't think that's something criO or containerD can do alone. The Docker images are OCI compliant but the Docker engine isn't, and that's the whole problem Kubernetes are having - the engine, and hence its removal. So, if you're using /var/run/docker.sock in ur cluster, that's going to break.
Fantastic video!
Although, a correction around 11:30 : Actually, Docker doesn't comply to OCI. That's why, dockershim (which is OCI compliant) was used in the past (and still is used) to compensate for that (because kubernetes CRI must be OCI compliant).
If docker would ve been OCI compliant, then there wouldn't ve been any need of dockershim on k8s's side.
But now, with the new update, kubernetes can directly use containerd as its CRI because containerd is OCI compliant. Similarly, it can use crio too because it is also OCI compliant.
Apart from this, the video was fab. It covered all the required and relevant details. Good job :D
Ok, does that mean it is not usefull to learn docker because it isn´t OCI compliant? I mean Nana said, you can still learn Docker, because the images that docker produce are still able to run in a k8s cluster. Am i right?
@@affemakla6884 when did I suggest to not learn docker? I just emphasized on a point which might have been useful to atleast one person going over the comments. Calm down and read my entire comment and be a little less pessimistic. Man, some people just can't bear constructive criticism provided diplomatically.
@@yash_renaissance_athlete Excuse me, i'm no native englsh speaker and in my comment should nothing, critisim or anything that could offend you, implied. It is a real question, that aims to knowing is it still usefull to learn docker(i am a beginner) because the images that docker build could still run in k8s because there OCI compliant? Again no offend!
@@affemakla6884 I m so sorry. I interpreted your tone in a wrong manner. It's tough to interpret the right kind of emotion from the bare text at times 😅. Apologies from my side.
To answer your question, Yes it's absolutely useful to learn docker. Although Docker technically is not OCI compliant but still it runs over containerd (high-level container runtime) and runc (low-level container runtime) due to which it emulates an OCI compliant nature.
So do check it out, it's extremely useful to learn it.
@@yash_renaissance_athlete thanks for your answer i appriciate it!
Thank you Nana... Actually, I never knew about this change and at first, I got worried, as I only worked with docker...
Perfect explanation, just the thing I needed, just as request, can you do a tutorial on crio or containerd.
I'm not even a DevOps engineer and this made perfect sense. And I learned some new things! 👍 Excellent video
Thanks
At 10:13 in the video, do not forget those running kubeenetes clusters of kaniko containers..
I was clapping👏when you clearly explaining the CI/CI part needs docker or not. thank's nana.
😊🙏
So comprehensive and clear! If you can explain it simply, you understand it perfectly...
Thanks a lot Nana!!! You are our first info source in this k8s world!! You are brilliant nana!.
Thank you for your explanation! I know a bit of docker and I didn't already start to study kubernetes. This video was clear even to me that I don't know anything about it. I'll keep going this journey in the docker+kubernets world then!
That's awesome, thank you Andrea :)
Thanks for sharing new valuable insights. Love your approach. All content creators should create value as maximum as possible.
Thanks so much! :)
Your videos really create impact on freshers like me... Thanks Nana form bottom of my heart.....
Happy to hear, thank you 🙂
Now I am cristal clear about changes! Thanks, Tina!
Thanks a lot for wrapping it up meticulously. I love to watch your videos. They are very helpful.
You will soon be one of the popular teachers on TH-cam reaching 100s of thousands of subscribers. Viel Erfolg ;-)
Thank you so much! Appreciate your comment 🙂 danke :)
waiting for this video to get all the doubts cleared. Thanks Nana
Hope it was helpful Rohit :)
Thank you Nana! Such a simple explanation🙏 Subscribed!
One of the best videos about this subject... but I just don't know why are you not able to say Azure, when you are listing clouds providers lol
Yet another cristal clear straight to the point video, bravo! which leaves me begging for others, specifically on the container runtime landscape.
I understand CRI-O or containerd can only replace Docker **within** kubernetes as container runtime, i.e that can't be used to build or run a standalone containerized workload --> is that correct?
more generally, some intro videos on docker alternatives will be more than welcome : how to install them to set-up a k8S cluster, how to configure the latter accordingly, how do they work ... etc.
Thanks again for the great content
Thanks Nana. Recently I started exploring Docker. Great explanation from your side and this video is very helpful.
This is the most Simplest explanation ever i have ever seen ❤️❤️❤️
Very much clear 👍🙂. as always great explanation Nana...👍
Thanks a lot :)
I love how well researched and articulated this is!!! 👏 thank you! I learnt a lot about “the in between bits” too.
Thank you Josh, appreciate your comment :)
I already knew the deprecation but your video gives me a lot more details. Thanks, Nana!
So clear a video. Thanks for the hard work you do with all these videos. I don't get why you don't have 1 million subs yet.
Thank you so much Henrik 😊
I've just started learning Docker and Kubernetes (or K8s as I've just learned) and was a bit worried if this was a waste of time - until I saw your video. Thank You :-)
Perfect... More such videos are welcome whenever we hear new announcements or deprecations
Thanks a lot Nana for the clarification. Clarified all my questions on the k8s deprecation of Docker.
Nana, thank you for this!
Thank you it enlightens me in just 12mins than reading articles from different sources ^^.
Happy to hear 😊
Finally someone that explains clearly! Great Work!
Thanks a ton Sergio! 😊
I am a developer and have no idea what are Kubernetes. I use docker containers (by docker-compose) the last couple of years everyday. The video is an interesting into to Kubernetes for me. Thanks!
It can't be explained better, really. Thanks you so much!
Thank you John, appreciate your feedback :)
Woow, the details you provide is an excellent, I'd love your videos Nana. I appreciate you to making this video, and sharing. Keep on uploading new videos. You're a good teacher. Thank you.
Not dropping the support but just moving ! It is wrong interpretation Nana!
Simple, sweet, and concise. 👍
Thanks a lot, I opened the video a bit scared about the change, but you basically answered all the questions I had, especially about CI/CD. Excellent video!
Your presentation and explanation is at next level 👌
Thank you :D
Excellent review & explanation of the issue with crystal clear wording and graphics. Thanks!
Thank you for this feedback, appreciate it very much :)
More than clear
You just rock, waiting fr ur bootcamp. Where can i ask some questions related to the bootcamp?
Thanks! I will publish more infos once the bootcamp is finished and up for sale including a dedicated video about it on TH-cam 😊 But in the meantime, you can of course write your questions to techworld-with-nana@nnsoftware.at and I will try to answer them asap.
@@TechWorldwithNana perfect! Keep us updated!
Clear all the doubts.Great explanation
Thanks for resolving all doubts .... amazing explanation ... now im not worried about running Docker images in Kube clusters...the CI CD Docker pipelines will run the same way
Your videos are the best, I can learn a lot in only a few minutes, thanks so much
Thank you Diego. I'm happy to hear 😊
BRAVO Nana!!! Your explanation is clear. Kudos to you.
You have a new subscriber. :)
Thanks for the explanation, Nana! Great as always :D
Thanks for sharing this update! Joining the fan club. :D
Very clear; short and sweet like master's approach; great video
Crisp & Clear Explanation As Always !!!
Thank you Pravin 🙂
So the question u haven't answered clearly. Should newcomers keep learning docker or containerd instead? Thanks for the great video !
Docker is still good for development as it ships with everything you need to build a fixed, repeatable environment. And docker uses containerd, so if you learn about docker, you learn about containerd anyway.
I taught containerd was only for running containers. And docker, among others, also for building them
You still should learn docker, since you build your images with it. containerd is just the component that runs the containers.
You made it so clear ! I love the way you explain things
Thank you Ilyas, really glad you like my way of explaining it :)
As usual, simple, relevant and clear. 👍 Thanks
I have a homework about ANN. I don't use K8. I've never used k8. I'm very good at procrastinating.
Really clear explanation though.
Crystal clear, just watched one of your videos, i subscribed right away
Awesome clear explanation. Thanks a lot for publishing this video.
Interesting and informative video. I was looking for such a comprehensive video. You saved at least 4 hours of my time .
That's amazing to hear! Thank you!
Excellent explanation, Thanks Nana
Happy to hear, thank you :)
Thanks Nana for excellent explanation of the topic. This is really useful. Thank you.
But after pulling several docker image to Kubernetes node , how to delete those image without docker install, like how we are docker rmi , please suggest solution to delete docker images in my k8's master node , i am using contained now
wow! that's clear and precise. No bullshit. From where did you learn all these devops concepts? can you share your experiences
Just had this question posed to me yesterday. Well now I know. Excellent and timely information.
glad to hear! 🙂
Excellent and well required video - as always.
the far the most clear !! thank you
Thank you Jasser, appreciate your comment :)
@@TechWorldwithNana :)
Clear in 3 minutes!!!! Very good explanation thanks
very complete video, well written script and nice pacing.
just subscribed because of the great work here :)
Brilliantly clarified -thanks!
Explained perfectly and with complete clarity... Thanks for video
amazing. I bet it was a difficult decision for all team envolved, but things must happen for development and security reasons
Thanks Marco, yes I agree
Very good explanation, i subscribed and going to watch all your videos Nana. please put more videos for learning :)
Perfectly cleared all the doubts. Thanks :)
Glad to hear! :)
super fantastic... you are mind blowing..
very much hard topic now i understand in few minutes..
credit goes to ur video..
thanks
Ur explanation is so clear . Thank you
As always, extremely clear!!
Great video! For a moment I thought I lost hours learning docker.
Great video, perfectly explained. Greetings from Ecuador.
Thank you Victor! :)
Awesome vidoes. I have been following some of the videos and there can't be more lucid and logical explanations than this.
Hey, I hope you are doing good. My doubt is whether can we still use docker containers during development and later during production make the conversion or whatever to deploy. I have very little knowledge in docker and still learning. I haven't even get started with kubernetes too, I just know few commands. If my question feels dump please ignore it :)