I've used Kubernetes for 5 years, but I never knew these 13 facts

I run the number one Kubernetes career I run the number one Kubernetes career community on the internet and someone community on the internet and someone community on the internet and someone from my community created a challenge from my community created a challenge from my community created a challenge for me with 13 facts about Kubernetes for me with 13 facts about Kubernetes for me with 13 facts about Kubernetes that he thinks I don't know. In this that he thinks I don't know. In this that he thinks I don't know. In this video, I'm going to go into it video, I'm going to go into it video, I'm going to go into it completely blind. I'm going to take you completely blind. I'm going to take you completely blind. I'm going to take you with me to see if you didn't know these with me to see if you didn't know these with me to see if you didn't know these facts, too. So, let's jump in. Challenge facts, too. So, let's jump in. Challenge facts, too. So, let's jump in. Challenge accepted. This is the presentation that accepted. This is the presentation that accepted. This is the presentation that was prepared for me and again, I have was prepared for me and again, I have was prepared for me and again, I have not seen these slides before. I'm going not seen these slides before. I'm going not seen these slides before. I'm going into this completely blind. I have no into this completely blind. I have no into this completely blind. I have no idea what's coming here. So, let's see idea what's coming here. So, let's see idea what's coming here. So, let's see how many of these facts I'm going to get how many of these facts I'm going to get how many of these facts I'm going to get right. Kubernetes worker nodes used to right. Kubernetes worker nodes used to right. Kubernetes worker nodes used to be called minions. Oh, cool. I did not be called minions. Oh, cool. I did not be called minions. Oh, cool. I did not know that. That's really cool. know that. That's really cool. know that. That's really cool. Early Kubernetes docs and commands used Early Kubernetes docs and commands used Early Kubernetes docs and commands used that word for the machines running that word for the machines running that word for the machines running workloads. workloads. workloads. The problem was that SaltStack also used The problem was that SaltStack also used The problem was that SaltStack also used minions. Interesting. And early minions. Interesting. And early minions. Interesting. And early Kubernetes setups could be configured Kubernetes setups could be configured Kubernetes setups could be configured with Salt. So, people started thinking with Salt. So, people started thinking with Salt. So, people started thinking Kubernetes depended on Salt more than it Kubernetes depended on Salt more than it Kubernetes depended on Salt more than it actually did. actually did. actually did. Eventually, the project renamed them to Eventually, the project renamed them to Eventually, the project renamed them to nodes, which is probably for the best nodes, which is probably for the best nodes, which is probably for the best because kubectl get minions sounds like because kubectl get minions sounds like because kubectl get minions sounds like you're a managing a supervillain army.

you're a managing a supervillain army. you're a managing a supervillain army. Well, I actually like the minion Well, I actually like the minion Well, I actually like the minion terminology. And SaltStack is uh as far terminology. And SaltStack is uh as far terminology. And SaltStack is uh as far as I know, like you have like Ansible, as I know, like you have like Ansible, as I know, like you have like Ansible, Puppet, Chef, and Salt. All of these Puppet, Chef, and Salt. All of these Puppet, Chef, and Salt. All of these tools are basically configuration tools are basically configuration tools are basically configuration management on Linux servers or servers management on Linux servers or servers management on Linux servers or servers in general. in general. in general. Uh that's my understanding of it. I I am Uh that's my understanding of it. I I am Uh that's my understanding of it. I I am experienced with Ansible, so that's what experienced with Ansible, so that's what experienced with Ansible, so that's what I know. You know, you use Ansible for I know. You know, you use Ansible for I know. You know, you use Ansible for configuring Linux servers, basically. configuring Linux servers, basically. configuring Linux servers, basically. And it's interesting that this was then And it's interesting that this was then And it's interesting that this was then tied up with with Kubernetes in this tied up with with Kubernetes in this tied up with with Kubernetes in this way. I do really like cattle or minions, way. I do really like cattle or minions, way. I do really like cattle or minions, though. So, yeah, I did not know this. I though. So, yeah, I did not know this. I though. So, yeah, I did not know this. I also do like the the cattle framing and also do like the the cattle framing and also do like the the cattle framing and especially Rancher does this a lot, especially Rancher does this a lot, especially Rancher does this a lot, right? Like Rancher, Harvester, that right? Like Rancher, Harvester, that right? Like Rancher, Harvester, that kind of thing. Maybe I I would move it kind of thing. Maybe I I would move it kind of thing. Maybe I I would move it more towards a farm architecture that more towards a farm architecture that more towards a farm architecture that rather than no nodes eventually. But rather than no nodes eventually. But rather than no nodes eventually. But yeah, we're over a decade in. Nodes it yeah, we're over a decade in. Nodes it yeah, we're over a decade in. Nodes it is, and that's probably not going to is, and that's probably not going to is, and that's probably not going to change. change. change. So, let's check out the next one. Google So, let's check out the next one. Google So, let's check out the next one. Google created Kubernetes.

created Kubernetes. created Kubernetes. I knew that. Before Kubernetes, there I knew that. Before Kubernetes, there I knew that. Before Kubernetes, there was Borg. Google ran it in secret for was Borg. Google ran it in secret for was Borg. Google ran it in secret for over a decade before revealing it to the over a decade before revealing it to the over a decade before revealing it to the public. public. public. In the early 2000s, Google was growing In the early 2000s, Google was growing In the early 2000s, Google was growing faster than any infrastructure faster than any infrastructure faster than any infrastructure technology could keep up with. Running technology could keep up with. Running technology could keep up with. Running Gmail, search, YouTube, and ads across Gmail, search, YouTube, and ads across Gmail, search, YouTube, and ads across thousands of servers meant someone had thousands of servers meant someone had thousands of servers meant someone had to describe what ran where, when, and on to describe what ran where, when, and on to describe what ran where, when, and on which machine automatically at massive which machine automatically at massive which machine automatically at massive scale. scale. scale. Borg became that system. It was Google's Borg became that system. It was Google's Borg became that system. It was Google's internal cluster manager, the control internal cluster manager, the control internal cluster manager, the control layer for running containerized layer for running containerized layer for running containerized workloads across its data centers. By workloads across its data centers. By workloads across its data centers. By the time Google finally published the time Google finally published the time Google finally published details in 2015, Borg had already details in 2015, Borg had already details in 2015, Borg had already accumulated roughly a decade of accumulated roughly a decade of accumulated roughly a decade of operational experience and was running operational experience and was running operational experience and was running over 100,000 jobs. over 100,000 jobs. over 100,000 jobs. The name was a deliberate Star Trek The name was a deliberate Star Trek The name was a deliberate Star Trek reference. Borg was meant to act like a reference. Borg was meant to act like a reference. Borg was meant to act like a collective brain for the data center. collective brain for the data center. collective brain for the data center. And yes, so so I knew this fact. I knew And yes, so so I knew this fact. I knew And yes, so so I knew this fact. I knew that the Google created Kubernetes that the Google created Kubernetes that the Google created Kubernetes basically and that it was based on their basically and that it was based on their basically and that it was based on their internal system called Borg. So, this internal system called Borg. So, this internal system called Borg. So, this one I knew. But, it is still surprising one I knew. But, it is still surprising one I knew. But, it is still surprising to people to hear that everything at to people to hear that everything at to people to hear that everything at Google runs in containers. This is they Google runs in containers. This is they Google runs in containers. This is they they publicly state this on their they publicly state this on their they publicly state this on their website, and people are still like website, and people are still like website, and people are still like doubting like should we containerize our doubting like should we containerize our doubting like should we containerize our application or not? Or should we application or not? Or should we application or not? Or should we actually be running in containers? Like actually be running in containers? Like actually be running in containers? Like Google has been doing this for well well Google has been doing this for well well Google has been doing this for well well well over a decade now, right? So, that well over a decade now, right? So, that well over a decade now, right? So, that is the way to do it, and Borg was is the way to do it, and Borg was is the way to do it, and Borg was created to run containers at scale. So, created to run containers at scale. So, created to run containers at scale. So, this one I knew. Google engineers this one I knew. Google engineers this one I knew. Google engineers created the Linux feature that made

created the Linux feature that made created the Linux feature that made Docker possible. Docker possible. Docker possible. To safely run many workloads on one To safely run many workloads on one To safely run many workloads on one machine, Borg needed process isolation machine, Borg needed process isolation machine, Borg needed process isolation and resource limits. So, Google and resource limits. So, Google and resource limits. So, Google engineers helped create Cgroups in engineers helped create Cgroups in engineers helped create Cgroups in Linux. Linux. Linux. Cgroups control CPU, memory, Cgroups control CPU, memory, Cgroups control CPU, memory, sand resource sand resource boundaries. sand resource sand resource boundaries. sand resource sand resource boundaries. I don't know what that means. Years I don't know what that means. Years I don't know what that means. Years later, Docker used Cgroups as a core later, Docker used Cgroups as a core later, Docker used Cgroups as a core building block. That means modern building block. That means modern building block. That means modern containers depend partly on engineering containers depend partly on engineering containers depend partly on engineering Google originally needed for Borg. Of Google originally needed for Borg. Of Google originally needed for Borg. Of course, I know about Cgroups, but I did course, I know about Cgroups, but I did course, I know about Cgroups, but I did not know that if this was originated by not know that if this was originated by not know that if this was originated by Google, that Google engineers created Google, that Google engineers created Google, that Google engineers created this this feature. I actually had no I this this feature. I actually had no I this this feature. I actually had no I didn't know that. I thought this was a didn't know that. I thought this was a didn't know that. I thought this was a lot older actually that this was way lot older actually that this was way lot older actually that this was way before Borg. But apparently it's not, before Borg. But apparently it's not, before Borg. But apparently it's not, Google created it. I do know that Google created it. I do know that Google created it. I do know that Cgroups control CPU, memory, et cetera, Cgroups control CPU, memory, et cetera, Cgroups control CPU, memory, et cetera, but sand resource boundaries, I don't but sand resource boundaries, I don't but sand resource boundaries, I don't know really know what that means. Or know really know what that means. Or know really know what that means. Or maybe it means sandbox or something like maybe it means sandbox or something like maybe it means sandbox or something like that. And of course, I knew that Docker that. And of course, I knew that Docker that. And of course, I knew that Docker then used Cgroups as a core building then used Cgroups as a core building then used Cgroups as a core building block. There's a tool that deliberately block. There's a tool that deliberately block. There's a tool that deliberately kills your pods during business hours. I kills your pods during business hours. I kills your pods during business hours. I think I know what's coming. In 2011, think I know what's coming. In 2011, think I know what's coming. In 2011, Netflix built Chaos Monkey. The name Netflix built Chaos Monkey. The name Netflix built Chaos Monkey. The name came from imagining a wild monkey loose came from imagining a wild monkey loose came from imagining a wild monkey loose in a data center pulling cables and in a data center pulling cables and in a data center pulling cables and smashing machines.

smashing machines. smashing machines. The challenge is building something that The challenge is building something that The challenge is building something that survives it. survives it. survives it. Kubernetes has its own version called Kubernetes has its own version called Kubernetes has its own version called kube monkey. It wakes up at 8:00 a.m. kube monkey. It wakes up at 8:00 a.m. kube monkey. It wakes up at 8:00 a.m. every weekday and kills a random every weekday and kills a random every weekday and kills a random selection of your pods. selection of your pods. selection of your pods. This way you can produce real production This way you can produce real production This way you can produce real production incidents and solve them. Yes, I I did incidents and solve them. Yes, I I did incidents and solve them. Yes, I I did know about this chaos monkey or the know about this chaos monkey or the know about this chaos monkey or the broader term chaos engineering. This is broader term chaos engineering. This is broader term chaos engineering. This is very common in mature Kubernetes very common in mature Kubernetes very common in mature Kubernetes environments and I also knew about the environments and I also knew about the environments and I also knew about the kube monkey tool. So yeah, this is this kube monkey tool. So yeah, this is this kube monkey tool. So yeah, this is this is very common and a very good practice is very common and a very good practice is very common and a very good practice to do as well. So yeah, I knew about to do as well. So yeah, I knew about to do as well. So yeah, I knew about this. Let's check out the next one. this. Let's check out the next one. this. Let's check out the next one. Kubernetes was also a strategic move Kubernetes was also a strategic move Kubernetes was also a strategic move against AWS. Interesting. By the early against AWS. Interesting. By the early against AWS. Interesting. By the early 2010s, AWS dominated cloud 2010s, AWS dominated cloud 2010s, AWS dominated cloud infrastructure. infrastructure. infrastructure. Once companies built deeply on AWS, Once companies built deeply on AWS, Once companies built deeply on AWS, switching was incredibly painful. That switching was incredibly painful. That switching was incredibly painful. That lock-in was Amazon's biggest advantage. lock-in was Amazon's biggest advantage. lock-in was Amazon's biggest advantage. Google wanted to change that. They Google wanted to change that. They Google wanted to change that. They admitted, "The plan was to intermediate admitted, "The plan was to intermediate admitted, "The plan was to intermediate the competition with a technology that the competition with a technology that the competition with a technology that we thought would run better on Google we thought would run better on Google we thought would run better on Google Cloud, and Kubernetes by its nature was Cloud, and Kubernetes by its nature was Cloud, and Kubernetes by its nature was an effective way to decouple the an effective way to decouple the an effective way to decouple the workload from the public cloud.

workload from the public cloud. workload from the public cloud. Kubernetes offered something dangerous Kubernetes offered something dangerous Kubernetes offered something dangerous to any cloud provider, portability." to any cloud provider, portability." to any cloud provider, portability." Yep. Run workloads on any cloud, any Yep. Run workloads on any cloud, any Yep. Run workloads on any cloud, any infrastructure, any provider, no infrastructure, any provider, no infrastructure, any provider, no lock-in, exactly. lock-in, exactly. lock-in, exactly. The irony is that it didn't actually The irony is that it didn't actually The irony is that it didn't actually hurt AWS. Amazon built EKS, their own hurt AWS. Amazon built EKS, their own hurt AWS. Amazon built EKS, their own fully managed Kubernetes service, and fully managed Kubernetes service, and fully managed Kubernetes service, and became one of the biggest beneficiaries became one of the biggest beneficiaries became one of the biggest beneficiaries of the Google of the Google of the Google standard that was created. Okay, so I standard that was created. Okay, so I standard that was created. Okay, so I didn't didn't didn't I didn't technically know that it was I didn't technically know that it was I didn't technically know that it was like deliberately done as a strategy like deliberately done as a strategy like deliberately done as a strategy against AWS, against AWS, against AWS, but the fact that Kubernetes is a way to but the fact that Kubernetes is a way to but the fact that Kubernetes is a way to create this infrastructure layer that is create this infrastructure layer that is create this infrastructure layer that is able to run both on prem, in the cloud, able to run both on prem, in the cloud, able to run both on prem, in the cloud, on multiple clouds, this I knew, and on multiple clouds, this I knew, and on multiple clouds, this I knew, and this is also why Kubernetes is such a this is also why Kubernetes is such a this is also why Kubernetes is such a compelling alternative to anything else. compelling alternative to anything else. compelling alternative to anything else. And obviously, like it is Kubernetes, And obviously, like it is Kubernetes, And obviously, like it is Kubernetes, but actually the thing that enables this but actually the thing that enables this but actually the thing that enables this is containerization, right? So, if you is containerization, right? So, if you is containerization, right? So, if you containerize your app, containerize your app, containerize your app, you can run it anywhere. You can run it you can run it anywhere. You can run it you can run it anywhere. You can run it in any in any in any uh infrastructure that has a container uh infrastructure that has a container uh infrastructure that has a container environment. But it just happens that environment. But it just happens that environment. But it just happens that Kubernetes is the standard for running Kubernetes is the standard for running Kubernetes is the standard for running containers at scale and in production.

containers at scale and in production. containers at scale and in production. If you're not doing that, then If you're not doing that, then If you're not doing that, then what are you doing, right? So, what are you doing, right? So, what are you doing, right? So, this is also why I always advise people, this is also why I always advise people, this is also why I always advise people, also my private students in Kubecraft, also my private students in Kubecraft, also my private students in Kubecraft, and I build my DevOps mentorship program and I build my DevOps mentorship program and I build my DevOps mentorship program around Kubernetes. It's in the name, around Kubernetes. It's in the name, around Kubernetes. It's in the name, Kubecraft. Like, I teach the craft of Kubecraft. Like, I teach the craft of Kubecraft. Like, I teach the craft of the Kubernetes engineer. No matter if the Kubernetes engineer. No matter if the Kubernetes engineer. No matter if you are a junior, if you have no tech you are a junior, if you have no tech you are a junior, if you have no tech experience, or if you're like a software experience, or if you're like a software experience, or if you're like a software engineer pivoting to to Kubernetes and engineer pivoting to to Kubernetes and engineer pivoting to to Kubernetes and DevOps, this is what I teach, and I it's DevOps, this is what I teach, and I it's DevOps, this is what I teach, and I it's in the name, CubeCraft, and I did that in the name, CubeCraft, and I did that in the name, CubeCraft, and I did that precisely for this reason, because I precisely for this reason, because I precisely for this reason, because I don't like vendor lock-in, I don't like don't like vendor lock-in, I don't like don't like vendor lock-in, I don't like to marry myself to ecosystems or brands to marry myself to ecosystems or brands to marry myself to ecosystems or brands in that sense. So, I focused my DevOps in that sense. So, I focused my DevOps in that sense. So, I focused my DevOps mentorship around Kubernetes, and I I mentorship around Kubernetes, and I I mentorship around Kubernetes, and I I don't regret it. Like, we're landing don't regret it. Like, we're landing don't regret it. Like, we're landing jobs every single week, precisely jobs every single week, precisely jobs every single week, precisely because of this this reason, because if because of this this reason, because if because of this this reason, because if you focus on this technology, you can you focus on this technology, you can you focus on this technology, you can carry this anywhere, Azure, AWS, on carry this anywhere, Azure, AWS, on carry this anywhere, Azure, AWS, on prem, it doesn't matter. And if you want prem, it doesn't matter. And if you want prem, it doesn't matter. And if you want to know more about this mentorship, you to know more about this mentorship, you to know more about this mentorship, you can check out the link below. Kubernetes can check out the link below. Kubernetes can check out the link below. Kubernetes was almost named something else before was almost named something else before was almost named something else before it getting its final name. The team it getting its final name. The team it getting its final name. The team explored many names over time.

explored many names over time. explored many names over time. One serious finalist was Carina. One serious finalist was Carina. One serious finalist was Carina. The code base had already been renamed The code base had already been renamed The code base had already been renamed as they thought that would be it. as they thought that would be it. as they thought that would be it. Then someone searched the name online Then someone searched the name online Then someone searched the name online and found adult content associations. and found adult content associations. and found adult content associations. Because of this, Carina got rejected. On Because of this, Carina got rejected. On Because of this, Carina got rejected. On the last day to decide the final name the last day to decide the final name the last day to decide the final name became Kubernetes, Greek for helmsman, became Kubernetes, Greek for helmsman, became Kubernetes, Greek for helmsman, who does not own the ship, but steers who does not own the ship, but steers who does not own the ship, but steers it. That matched the product, and it was it. That matched the product, and it was it. That matched the product, and it was unique and available, and it won. So, unique and available, and it won. So, unique and available, and it won. So, interesting. I Well, I do know the interesting. I Well, I do know the interesting. I Well, I do know the definition of Kubernetes and where it definition of Kubernetes and where it definition of Kubernetes and where it came from, but that they meant that they came from, but that they meant that they came from, but that they meant that they were considering Carina before, I did were considering Carina before, I did were considering Carina before, I did not know that. And I'm actually really not know that. And I'm actually really not know that. And I'm actually really happy that they went with Kubernetes happy that they went with Kubernetes happy that they went with Kubernetes instead of Carina. Kubernetes is a much instead of Carina. Kubernetes is a much instead of Carina. Kubernetes is a much cooler name. It sounds great. It has a cooler name. It sounds great. It has a cooler name. It sounds great. It has a much cooler meaning. And yeah, it's good much cooler meaning. And yeah, it's good much cooler meaning. And yeah, it's good that there's no that there's no that there's no uh uh uh adult association with with Kubernetes. adult association with with Kubernetes. adult association with with Kubernetes. Not as far as I know. Maybe there is Not as far as I know. Maybe there is Not as far as I know. Maybe there is some some some very niche um fetish out there for very niche um fetish out there for very niche um fetish out there for bearded guys and Kubernetes, who knows?

bearded guys and Kubernetes, who knows? bearded guys and Kubernetes, who knows? But, yeah. Carina, I'm glad they didn't But, yeah. Carina, I'm glad they didn't But, yeah. Carina, I'm glad they didn't go with that one. But, maybe here's a go with that one. But, maybe here's a go with that one. But, maybe here's a fun fact that you may not know is that fun fact that you may not know is that fun fact that you may not know is that you often see the you often see the you often see the abbreviation K8S. abbreviation K8S. abbreviation K8S. That is actually because the number of That is actually because the number of That is actually because the number of letters between the K and the S is letters between the K and the S is letters between the K and the S is eight. So if you do 1 2 3 4 5 6 7 8, eight. So if you do 1 2 3 4 5 6 7 8, eight. So if you do 1 2 3 4 5 6 7 8, the number of letters between the K and the number of letters between the K and the number of letters between the K and the S is eight. So that's why they write the S is eight. So that's why they write the S is eight. So that's why they write eight. So that's a little bonus factor eight. So that's a little bonus factor eight. So that's a little bonus factor for you. Kubernetes also had a secret for you. Kubernetes also had a secret for you. Kubernetes also had a secret code name Project 7 of 9. code name Project 7 of 9. code name Project 7 of 9. Before the launch, Kubernetes was Before the launch, Kubernetes was Before the launch, Kubernetes was internally nicknamed Project 7 of 9. In internally nicknamed Project 7 of 9. In internally nicknamed Project 7 of 9. In Star Trek, Seven of Nine was a character Star Trek, Seven of Nine was a character Star Trek, Seven of Nine was a character who came from the Borg collective but who came from the Borg collective but who came from the Borg collective but became independent. Kubernetes came from became independent. Kubernetes came from became independent. Kubernetes came from Borg's ideas but was rebuilt as a more Borg's ideas but was rebuilt as a more Borg's ideas but was rebuilt as a more open public version for everyone else. open public version for everyone else. open public version for everyone else. So while Kubernetes eventually won, even So while Kubernetes eventually won, even So while Kubernetes eventually won, even today the Kubernetes logo still has today the Kubernetes logo still has today the Kubernetes logo still has seven spokes as a permanent homage to seven spokes as a permanent homage to seven spokes as a permanent homage to the original internal code name of Seven the original internal code name of Seven the original internal code name of Seven of Nine. Very interesting. No, I did not of Nine. Very interesting. No, I did not of Nine. Very interesting. No, I did not know this. And maybe an interesting fact know this. And maybe an interesting fact know this. And maybe an interesting fact you may not know about me you may not know about me you may not know about me is that even though I'm really deep into is that even though I'm really deep into is that even though I'm really deep into tech, I am actually um I I never read tech, I am actually um I I never read tech, I am actually um I I never read science fiction. I never was able to get science fiction. I never was able to get science fiction. I never was able to get into it. There's actually an article on into it. There's actually an article on into it. There's actually an article on my blog where I go a little bit deeper my blog where I go a little bit deeper my blog where I go a little bit deeper into why and how.

into why and how. into why and how. But um so I never watched Star Wars or But um so I never watched Star Wars or But um so I never watched Star Wars or Star Trek. I am not into it at all for Star Trek. I am not into it at all for Star Trek. I am not into it at all for some strange reason. some strange reason. some strange reason. I I tried. I really really tried. I love I I tried. I really really tried. I love I I tried. I really really tried. I love everything about AI and technology but everything about AI and technology but everything about AI and technology but somehow it just doesn't grab me. Real somehow it just doesn't grab me. Real somehow it just doesn't grab me. Real quick, if these videos make you quick, if these videos make you quick, if these videos make you interested in learning Kubernetes, I interested in learning Kubernetes, I interested in learning Kubernetes, I created a completely free Kubernetes created a completely free Kubernetes created a completely free Kubernetes learning road map that you can get by learning road map that you can get by learning road map that you can get by clicking the link in the description clicking the link in the description clicking the link in the description below. It includes access to 8 hours of below. It includes access to 8 hours of below. It includes access to 8 hours of private courses that I created for my private courses that I created for my private courses that I created for my private students, road maps, everything private students, road maps, everything private students, road maps, everything you need to get started with learning you need to get started with learning you need to get started with learning Kubernetes. Check it out. It's in the Kubernetes. Check it out. It's in the Kubernetes. Check it out. It's in the description below and it's completely description below and it's completely description below and it's completely for free. Now back to the video. So, I for free. Now back to the video. So, I for free. Now back to the video. So, I did not know the reference, but I think did not know the reference, but I think did not know the reference, but I think it's very interesting that they did use it's very interesting that they did use it's very interesting that they did use Star Trek as a Star Trek as a Star Trek as a as a reference here. And I I love as a reference here. And I I love as a reference here. And I I love knowing the fact now that this is the knowing the fact now that this is the knowing the fact now that this is the reason why it has seven spokes. reason why it has seven spokes. reason why it has seven spokes. I love these kinds of facts, so thank I love these kinds of facts, so thank I love these kinds of facts, so thank you, dear community member, for teaching you, dear community member, for teaching you, dear community member, for teaching me this one. Let's check out the next me this one. Let's check out the next me this one. Let's check out the next one. Pods were actually called tasks one. Pods were actually called tasks one. Pods were actually called tasks until the last moment.

until the last moment. until the last moment. But during development, the name changed But during development, the name changed But during development, the name changed just shortly before launch. just shortly before launch. just shortly before launch. Pod fit better, a pod of whales, things Pod fit better, a pod of whales, things Pod fit better, a pod of whales, things grouped tightly together. Millions of grouped tightly together. Millions of grouped tightly together. Millions of engineers know now type kubectl get engineers know now type kubectl get engineers know now type kubectl get pods, and they almost typed kubectl get pods, and they almost typed kubectl get pods, and they almost typed kubectl get tasks. Okay, I didn't know that. tasks. Okay, I didn't know that. tasks. Okay, I didn't know that. And I'm really glad that they didn't go And I'm really glad that they didn't go And I'm really glad that they didn't go for tasks because that would be so for tasks because that would be so for tasks because that would be so confusing with jobs and tasks. confusing with jobs and tasks. confusing with jobs and tasks. Like Like Like it it sounds it it's very strange to me it it sounds it it's very strange to me it it sounds it it's very strange to me that they would name that tasks because that they would name that tasks because that they would name that tasks because collection of containers is not collection of containers is not collection of containers is not necessarily a task in my conception of necessarily a task in my conception of necessarily a task in my conception of it, right? So, yeah, they they went I I it, right? So, yeah, they they went I I it, right? So, yeah, they they went I I did know that pod came from a pod of did know that pod came from a pod of did know that pod came from a pod of whales, like a group of whales. And the whales, like a group of whales. And the whales, like a group of whales. And the reason for this is that reason for this is that reason for this is that people sometimes think that a pod is a people sometimes think that a pod is a people sometimes think that a pod is a container, that's the same, but that's container, that's the same, but that's container, that's the same, but that's wrong. A pod is like this collection of wrong. A pod is like this collection of wrong. A pod is like this collection of resources which can be multiple resources which can be multiple resources which can be multiple containers and all of their networking containers and all of their networking containers and all of their networking around it. Like that little package is around it. Like that little package is around it. Like that little package is called a pod, and they stuck with the called a pod, and they stuck with the called a pod, and they stuck with the nautical theme there, and they chose to nautical theme there, and they chose to nautical theme there, and they chose to use the word for a group of whales. So, use the word for a group of whales. So, use the word for a group of whales. So, that is that is cool, but I did not know that is that is cool, but I did not know that is that is cool, but I did not know that pods were actually called tasks that pods were actually called tasks that pods were actually called tasks until the last moment. And I'm really until the last moment. And I'm really until the last moment. And I'm really glad they went with pods instead.

glad they went with pods instead. glad they went with pods instead. Kubectl has an official pronunciation in Kubectl has an official pronunciation in Kubectl has an official pronunciation in the change log that almost nobody used. the change log that almost nobody used. the change log that almost nobody used. Kubectl is the command line tool you use Kubectl is the command line tool you use Kubectl is the command line tool you use to control a Kubernetes cluster a use to control a Kubernetes cluster a use to control a Kubernetes cluster a use countless of times. countless of times. countless of times. In the V1.9 change log released December In the V1.9 change log released December In the V1.9 change log released December 2017, 2017, 2017, the official project settled it. The the official project settled it. The the official project settled it. The canonical pronunciation of kubectl is canonical pronunciation of kubectl is canonical pronunciation of kubectl is cube control. cube control. cube control. Well, I'm literally pronouncing it wrong Well, I'm literally pronouncing it wrong Well, I'm literally pronouncing it wrong in the in the in the actual in the in the in the actual in the in the in the actual as I'm recording this, right? Cube as I'm recording this, right? Cube as I'm recording this, right? Cube control. Most engineers say kubectl control. Most engineers say kubectl control. Most engineers say kubectl instead. instead. instead. Okay. Well, this is a painful Okay. Well, this is a painful Okay. Well, this is a painful confrontation because I loved using confrontation because I loved using confrontation because I loved using official statements and pronunciations official statements and pronunciations official statements and pronunciations and and I like to do things things and and I like to do things things and and I like to do things things correctly. correctly. correctly. So, yeah, for 6 years now I've been So, yeah, for 6 years now I've been So, yeah, for 6 years now I've been doing it wrong and in this video as I'm doing it wrong and in this video as I'm doing it wrong and in this video as I'm I'm as I'm re- reading these slides, I'm I'm as I'm re- reading these slides, I'm I'm as I'm re- reading these slides, I'm doing it wrong. I'll have to revise a doing it wrong. I'll have to revise a doing it wrong. I'll have to revise a few things.

few things. few things. I mean, I do know like some people say I mean, I do know like some people say I mean, I do know like some people say cube cuddle. cube cuddle. cube cuddle. And yeah, that has I I I cringe so much And yeah, that has I I I cringe so much And yeah, that has I I I cringe so much every time I hear someone say that. every time I hear someone say that. every time I hear someone say that. Like cube cuddle, like that sounds like Like cube cuddle, like that sounds like Like cube cuddle, like that sounds like cuddling and yeah, no, that is cuddling and yeah, no, that is cuddling and yeah, no, that is definitely not the thing to do. So, I definitely not the thing to do. So, I definitely not the thing to do. So, I fortunately I've never done that. But fortunately I've never done that. But fortunately I've never done that. But now I'm really curious what the official now I'm really curious what the official now I'm really curious what the official pronunciation of systemctl pronunciation of systemctl pronunciation of systemctl is. Because am I saying that wrong a is. Because am I saying that wrong a is. Because am I saying that wrong a wrong too then? Systemctl wrong too then? Systemctl wrong too then? Systemctl pronunciation. pronunciation. pronunciation. How to pronounce systemctl? Well, I How to pronounce systemctl? Well, I How to pronounce systemctl? Well, I don't want to go to Reddit trans don't want to go to Reddit trans don't want to go to Reddit trans programmer. No, thank you. Let's see, programmer. No, thank you. Let's see, programmer. No, thank you. Let's see, superuser. What do they say? superuser. What do they say? superuser. What do they say? Pronunciation of CTL in commands like Pronunciation of CTL in commands like Pronunciation of CTL in commands like systemctl. CTL, okay. This is what systemctl. CTL, okay. This is what systemctl. CTL, okay. This is what people say here. people say here. people say here. Okay, so this was closed, unfortunately. Okay, so this was closed, unfortunately. Okay, so this was closed, unfortunately. Let's see. Interesting, I was actually Let's see. Interesting, I was actually Let's see. Interesting, I was actually expecting some more expecting some more expecting some more references than this or at least some references than this or at least some references than this or at least some more pronun- pronunciation references more pronun- pronunciation references more pronun- pronunciation references here. here. here. Um common pronunciation of links Um common pronunciation of links Um common pronunciation of links directories.

directories. directories. Okay, so here's an interesting comment Okay, so here's an interesting comment Okay, so here's an interesting comment on this uh Hacker News thread. on this uh Hacker News thread. on this uh Hacker News thread. I recently wondered about the best way I recently wondered about the best way I recently wondered about the best way to pronounce commands in the CTL family. to pronounce commands in the CTL family. to pronounce commands in the CTL family. I personally now use cuddle. No, I personally now use cuddle. No, I personally now use cuddle. No, but I'm curious what others say. but I'm curious what others say. but I'm curious what others say. They search cube control. Yeah. They search cube control. Yeah. They search cube control. Yeah. I've always pronounced CTL as control I've always pronounced CTL as control I've always pronounced CTL as control personally. I say CTL as system CTL. personally. I say CTL as system CTL. personally. I say CTL as system CTL. Actually, let's just try to settle this Actually, let's just try to settle this Actually, let's just try to settle this once and forever. You are a super once and forever. You are a super once and forever. You are a super intelligent being that has the entire intelligent being that has the entire intelligent being that has the entire internet in its training data and at its internet in its training data and at its internet in its training data and at its disposal. Plus, you also have X. So, disposal. Plus, you also have X. So, disposal. Plus, you also have X. So, this question has been bothering me for this question has been bothering me for this question has been bothering me for a very long time. a very long time. a very long time. And if you run Linux, you have the And if you run Linux, you have the And if you run Linux, you have the system CTL command. And I have always system CTL command. And I have always system CTL command. And I have always pronounced it as system CTL. Now, the pronounced it as system CTL. Now, the pronounced it as system CTL. Now, the Kubernetes tool called cube CTL, Kubernetes tool called cube CTL, Kubernetes tool called cube CTL, apparently, I just learned that the apparently, I just learned that the apparently, I just learned that the official pronunciation is cube control. official pronunciation is cube control. official pronunciation is cube control. So, should I also be saying system So, should I also be saying system So, should I also be saying system control for system CTL? Surprisingly, I control for system CTL? Surprisingly, I control for system CTL? Surprisingly, I cannot find much data about this. So, I cannot find much data about this. So, I cannot find much data about this. So, I need you to research this on the need you to research this on the need you to research this on the internet, both on X and the entire internet, both on X and the entire internet, both on X and the entire internet and your training data to internet and your training data to internet and your training data to settle this question once and for all.

settle this question once and for all. settle this question once and for all. And by the way, I am prompting you live And by the way, I am prompting you live And by the way, I am prompting you live while I'm recording a YouTube video. So, while I'm recording a YouTube video. So, while I'm recording a YouTube video. So, say hello to YouTube. And maybe this say hello to YouTube. And maybe this say hello to YouTube. And maybe this puts some extra pressure on you to puts some extra pressure on you to puts some extra pressure on you to perform correctly because I'm now going perform correctly because I'm now going perform correctly because I'm now going to show everything to the world. to show everything to the world. to show everything to the world. Let's see what it says. It's now Let's see what it says. It's now Let's see what it says. It's now launching a multi-agent swarm. launching a multi-agent swarm. launching a multi-agent swarm. Hello, YouTube. Thanks for tuning in Hello, YouTube. Thanks for tuning in Hello, YouTube. Thanks for tuning in live. I hope this settles the live. I hope this settles the live. I hope this settles the pronunciation debate once and for all. pronunciation debate once and for all. pronunciation debate once and for all. Let's see. Let's see. Let's see. No official pronunciation for system No official pronunciation for system No official pronunciation for system CTL. CTL. CTL. Unlike cube CTL, which explicitly Unlike cube CTL, which explicitly Unlike cube CTL, which explicitly documented as cube control, documented as cube control, documented as cube control, has zero official guidance from the has zero official guidance from the has zero official guidance from the systemd project. What the community says systemd project. What the community says systemd project. What the community says from years of Reddit threads, from years of Reddit threads, from years of Reddit threads, system CTL is the split. Yeah, so it's system CTL is the split. Yeah, so it's system CTL is the split. Yeah, so it's system CTL, that's my current system CTL, that's my current system CTL, that's my current pronunciation, super common. System pronunciation, super common. System pronunciation, super common. System control, very widespread. So, should you control, very widespread. So, should you control, very widespread. So, should you switch to system control? Not switch to system control? Not switch to system control? Not necessarily. Your system CTL necessarily. Your system CTL necessarily. Your system CTL pronunciation is perfectly valid and pronunciation is perfectly valid and pronunciation is perfectly valid and widely used in the wild.

widely used in the wild. widely used in the wild. That said, system control is also That said, system control is also That said, system control is also totally correct and has the advantage of totally correct and has the advantage of totally correct and has the advantage of being consistent with how Kubernetes being consistent with how Kubernetes being consistent with how Kubernetes officially handled the exact same officially handled the exact same officially handled the exact same abbreviation. better. Apparently, the abbreviation. better. Apparently, the abbreviation. better. Apparently, the correct way to do this is to say cube correct way to do this is to say cube correct way to do this is to say cube control. I'll have to get used to that. control. I'll have to get used to that. control. I'll have to get used to that. So, let's move on to the next one. So, let's move on to the next one. So, let's move on to the next one. Tesla's Kubernetes dashboard has no Tesla's Kubernetes dashboard has no Tesla's Kubernetes dashboard has no password and hackers mined crypto on it. password and hackers mined crypto on it. password and hackers mined crypto on it. What? What? What? Okay, on February 2018, cybersecurity Okay, on February 2018, cybersecurity Okay, on February 2018, cybersecurity firm Red Lock discovered Tesla's firm Red Lock discovered Tesla's firm Red Lock discovered Tesla's Kubernetes console was accessible Kubernetes console was accessible Kubernetes console was accessible without any password. This is so bad. without any password. This is so bad. without any password. This is so bad. Hackers had already infiltrated, found Hackers had already infiltrated, found Hackers had already infiltrated, found AWS credentials exposed within a pod, AWS credentials exposed within a pod, AWS credentials exposed within a pod, access an S3 bucket with sensitive access an S3 bucket with sensitive access an S3 bucket with sensitive telemetry data, and deployed crypto telemetry data, and deployed crypto telemetry data, and deployed crypto mining software. Well deserved. They hid mining software. Well deserved. They hid mining software. Well deserved. They hid behind Cloudflare, non-standard ports, behind Cloudflare, non-standard ports, behind Cloudflare, non-standard ports, and intentionally throttled CPU usage to and intentionally throttled CPU usage to and intentionally throttled CPU usage to avoid detection. avoid detection. avoid detection. Tesla fixed the vulnerability within Tesla fixed the vulnerability within Tesla fixed the vulnerability within hours and awarded the researchers hours and awarded the researchers hours and awarded the researchers $3,133.70.

That is a very specific number. That is a very specific number. Uh through their bug bounty program. Uh through their bug bounty program. Uh through their bug bounty program. The amount of 1337 is hacker slang for The amount of 1337 is hacker slang for The amount of 1337 is hacker slang for elite. Yeah, if you have ever played CS elite. Yeah, if you have ever played CS elite. Yeah, if you have ever played CS 1.6, you will know. Tesla stated the 1.6, you will know. Tesla stated the 1.6, you will know. Tesla stated the impact was limited to internally used uh impact was limited to internally used uh impact was limited to internally used uh engineering test cars. Okay, well, I did engineering test cars. Okay, well, I did engineering test cars. Okay, well, I did not know this. Uh I do know that plenty not know this. Uh I do know that plenty not know this. Uh I do know that plenty of Kubernetes environments are exposed of Kubernetes environments are exposed of Kubernetes environments are exposed through their dashboards this way. So, through their dashboards this way. So, through their dashboards this way. So, it's a very it's a common thing, but I it's a very it's a common thing, but I it's a very it's a common thing, but I had not expected a company like Tesla to had not expected a company like Tesla to had not expected a company like Tesla to have um have um have um a vulnerability like this. So, today I a vulnerability like this. So, today I a vulnerability like this. So, today I learned. Next one. Kubernetes destroyed learned. Next one. Kubernetes destroyed learned. Next one. Kubernetes destroyed a 4 billion valuation without writing a a 4 billion valuation without writing a a 4 billion valuation without writing a single line of Docker's code. Okay. In single line of Docker's code. Okay. In single line of Docker's code. Okay. In 2016, Docker turned down a 4 billion 2016, Docker turned down a 4 billion 2016, Docker turned down a 4 billion Microsoft acquisition offer. They had Microsoft acquisition offer. They had Microsoft acquisition offer. They had Swarm. Swarm. Swarm. They weren't worried. Kubernetes kept They weren't worried. Kubernetes kept They weren't worried. Kubernetes kept growing anyway. growing anyway. growing anyway. By 2017, Docker was forced to announce By 2017, Docker was forced to announce By 2017, Docker was forced to announce Kubernetes support from its own stage. Kubernetes support from its own stage. Kubernetes support from its own stage. By 2019, the enterprise business was By 2019, the enterprise business was By 2019, the enterprise business was sold to Mirantis. sold to Mirantis. sold to Mirantis. 300 people were gone and the company had 300 people were gone and the company had 300 people were gone and the company had collapsed into a 60-person startup.

collapsed into a 60-person startup. collapsed into a 60-person startup. Kubernetes didn't sue them, didn't fork Kubernetes didn't sue them, didn't fork Kubernetes didn't sue them, didn't fork them, and didn't acquire them. It just them, and didn't acquire them. It just them, and didn't acquire them. It just won. Yeah, interesting. No, I I did not won. Yeah, interesting. No, I I did not won. Yeah, interesting. No, I I did not know this history. I didn't know that know this history. I didn't know that know this history. I didn't know that Docker was actually valued at 4 billion Docker was actually valued at 4 billion Docker was actually valued at 4 billion by Microsoft at that stage. Like, they by Microsoft at that stage. Like, they by Microsoft at that stage. Like, they must be must be must be regretting that now so much. Yeah, I'm regretting that now so much. Yeah, I'm regretting that now so much. Yeah, I'm very much aware that Docker Swarm has uh very much aware that Docker Swarm has uh very much aware that Docker Swarm has uh lost the game. Kubernetes has won, but lost the game. Kubernetes has won, but lost the game. Kubernetes has won, but still there are people recommending still there are people recommending still there are people recommending Swarm. Like, Swarm. Like, Swarm. Like, it is such a big misinformation for it is such a big misinformation for it is such a big misinformation for people to do that. Like, if you ever people to do that. Like, if you ever people to do that. Like, if you ever hear someone talk about Docker Swarm, hear someone talk about Docker Swarm, hear someone talk about Docker Swarm, please just skip to the next chapter please just skip to the next chapter please just skip to the next chapter because they clearly because they clearly because they clearly um are operating on outdated um are operating on outdated um are operating on outdated information. Kubernetes won, okay? Stop information. Kubernetes won, okay? Stop information. Kubernetes won, okay? Stop thinking about Docker Swarm. thinking about Docker Swarm. thinking about Docker Swarm. But, yeah, interesting. I didn't know But, yeah, interesting. I didn't know But, yeah, interesting. I didn't know that. Kubernetes is projected to grow that. Kubernetes is projected to grow that. Kubernetes is projected to grow over 250% over 250% over 250% this decade. this decade. this decade. This I know. The global Kubernetes This I know. The global Kubernetes This I know. The global Kubernetes market was estimated at 2.3 billion in market was estimated at 2.3 billion in market was estimated at 2.3 billion in 2024. By 2030, forecasts expect it to 2024. By 2030, forecasts expect it to 2024. By 2030, forecasts expect it to reach 8.2 billion. Go Kubernetes.

reach 8.2 billion. Go Kubernetes. reach 8.2 billion. Go Kubernetes. That's 3 and 1/2 x growth in just 6 That's 3 and 1/2 x growth in just 6 That's 3 and 1/2 x growth in just 6 years, a 23.8 years, a 23.8 years, a 23.8 annual growth rate. Most technologies annual growth rate. Most technologies annual growth rate. Most technologies slow down after going mainstream. slow down after going mainstream. slow down after going mainstream. Kubernetes is doing the opposite. The Kubernetes is doing the opposite. The Kubernetes is doing the opposite. The market around it is still expanding market around it is still expanding market around it is still expanding fast. Yes, I I I know about this and fast. Yes, I I I know about this and fast. Yes, I I I know about this and this is what I what I basically this is what I what I basically this is what I what I basically investigate almost weekly. Like, what is investigate almost weekly. Like, what is investigate almost weekly. Like, what is the state of the market like I am the state of the market like I am the state of the market like I am arguably one of the people in the world arguably one of the people in the world arguably one of the people in the world who is closest to these kinds of numbers who is closest to these kinds of numbers who is closest to these kinds of numbers because I because I because I I'm fascinated by it. I can also explain I'm fascinated by it. I can also explain I'm fascinated by it. I can also explain some of the reasons for this, right? some of the reasons for this, right? some of the reasons for this, right? Because Kubernetes is over a decade old Because Kubernetes is over a decade old Because Kubernetes is over a decade old now and generally in the IT industry now and generally in the IT industry now and generally in the IT industry what you see is that it takes about 10 what you see is that it takes about 10 what you see is that it takes about 10 years for tools to get wide adopted years for tools to get wide adopted years for tools to get wide adopted enterprise trust. And this is what you enterprise trust. And this is what you enterprise trust. And this is what you start seeing happening now. Like huge start seeing happening now. Like huge start seeing happening now. Like huge government organizations, huge government organizations, huge government organizations, huge enterprises, massive companies are now enterprises, massive companies are now enterprises, massive companies are now adopting Kubernetes as the de facto adopting Kubernetes as the de facto adopting Kubernetes as the de facto orchestration layer for containers, orchestration layer for containers, orchestration layer for containers, workloads, workloads, workloads, batch computing, all of these things.

batch computing, all of these things. batch computing, all of these things. Kubernetes has won that game and it's Kubernetes has won that game and it's Kubernetes has won that game and it's now being rolled out related to the now being rolled out related to the now being rolled out related to the earlier point about Kubernetes being earlier point about Kubernetes being earlier point about Kubernetes being this sort of independent layer in this sort of independent layer in this sort of independent layer in between that you can easily relatively between that you can easily relatively between that you can easily relatively easily migrate to clouds or on prem or easily migrate to clouds or on prem or easily migrate to clouds or on prem or or anything like that. or anything like that. or anything like that. So that's the first reason and the So that's the first reason and the So that's the first reason and the second reason is AI. Like Kubernetes is second reason is AI. Like Kubernetes is second reason is AI. Like Kubernetes is the de facto operating system for AI. the de facto operating system for AI. the de facto operating system for AI. Publicly stated by the CNCF Foundation Publicly stated by the CNCF Foundation Publicly stated by the CNCF Foundation in the 2025 survey and I did a full in the 2025 survey and I did a full in the 2025 survey and I did a full video about that that you can find here. video about that that you can find here. video about that that you can find here. And so Kubernetes has won that game. And so Kubernetes has won that game. And so Kubernetes has won that game. Chat GPT, Anthropic Claude, Grok, XAI Chat GPT, Anthropic Claude, Grok, XAI Chat GPT, Anthropic Claude, Grok, XAI that you just saw me use, all of that is that you just saw me use, all of that is that you just saw me use, all of that is being trained, built, and run. So the being trained, built, and run. So the being trained, built, and run. So the inference is running on Kubernetes. And inference is running on Kubernetes. And inference is running on Kubernetes. And this is why it is not slowing down by this is why it is not slowing down by this is why it is not slowing down by any means. It is growing. So if you want any means. It is growing. So if you want any means. It is growing. So if you want to have a stable tech career making six to have a stable tech career making six to have a stable tech career making six figures plus over the next decade or so, figures plus over the next decade or so, figures plus over the next decade or so, Kubernetes is the thing to focus on. And Kubernetes is the thing to focus on. And Kubernetes is the thing to focus on. And if you want to know more about how I can if you want to know more about how I can if you want to know more about how I can help you with that, check out the link help you with that, check out the link help you with that, check out the link in the description. On March the 6th, in the description. On March the 6th, in the description. On March the 6th, 2028, Kubernetes ranked second in the 2028, Kubernetes ranked second in the 2028, Kubernetes ranked second in the world for active contributors and open world for active contributors and open world for active contributors and open issues on GitHub behind only the Linux issues on GitHub behind only the Linux issues on GitHub behind only the Linux kernel.

kernel. kernel. Not starts or downloads, but the number Not starts or downloads, but the number Not starts or downloads, but the number of engineers from different companies of engineers from different companies of engineers from different companies actively writing code for it every actively writing code for it every actively writing code for it every single day. single day. single day. A project that began as a 250 file code A project that began as a 250 file code A project that began as a 250 file code dump in June 2014 dump in June 2014 dump in June 2014 had in under 4 years matched the had in under 4 years matched the had in under 4 years matched the development velocity of a 27-year-old development velocity of a 27-year-old development velocity of a 27-year-old operating system. Very interesting. operating system. Very interesting. operating system. Very interesting. This video started with Linux. It ends This video started with Linux. It ends This video started with Linux. It ends here. here. here. Misha, I hope you like this one and Misha, I hope you like this one and Misha, I hope you like this one and thank you for all that you do. thank you for all that you do. thank you for all that you do. Appreciate it. Um no, I did not know Appreciate it. Um no, I did not know Appreciate it. Um no, I did not know this. I I actually did not know this. this. I I actually did not know this. this. I I actually did not know this. This is a really interesting fact to me This is a really interesting fact to me This is a really interesting fact to me that Kubernetes ranked second. And that Kubernetes ranked second. And that Kubernetes ranked second. And what's even more interesting to me is what's even more interesting to me is what's even more interesting to me is that this was not like 2024 or whatever. that this was not like 2024 or whatever. that this was not like 2024 or whatever. No, it's 2018. So, already like it's No, it's 2018. So, already like it's No, it's 2018. So, already like it's almost 10 years ago, it was already almost 10 years ago, it was already almost 10 years ago, it was already ranked second in the world for active ranked second in the world for active ranked second in the world for active contributors. And it also attests to contributors. And it also attests to contributors. And it also attests to the power of the of open source the power of the of open source the power of the of open source development and enterprise tooling like development and enterprise tooling like development and enterprise tooling like this. So, yeah, I I I didn't know this this. So, yeah, I I I didn't know this this. So, yeah, I I I didn't know this one specifically. Very interesting.

one specifically. Very interesting. one specifically. Very interesting. Thank you so much for creating this Thank you so much for creating this Thank you so much for creating this presentation for me. I really presentation for me. I really presentation for me. I really appreciated it. And if this video piqued appreciated it. And if this video piqued appreciated it. And if this video piqued your interest in learning more about your interest in learning more about your interest in learning more about Kubernetes, I created a free Kubernetes Kubernetes, I created a free Kubernetes Kubernetes, I created a free Kubernetes learning road map that you can get by learning road map that you can get by learning road map that you can get by clicking the link in the description clicking the link in the description clicking the link in the description down below. Completely for free. Make down below. Completely for free. Make down below. Completely for free. Make use of it while you can, and I'll see use of it while you can, and I'll see use of it while you can, and I'll see you in the next video.