Learn Kubernetes, Part I, Basics, Deployment and Minikube

Chris Noring on May 18, 2019

Follow me on Twitter, happy to take your suggestions on topics or improvements /Chris Kubernetes is about orchestrating containerized apps. Docke... [Read Full]
Editor guide

It's Also called K8s so Kubernete*s*, 8 characters in the middle are removed. Now you can impress your friends that you know why it's referred to as K8.

I always thought the reason for this is that "ete" in "Kubernetes" sounds like an 8, so we have "Kubern8s". What kind of eights? Well, "Kubern" eights are not a real thing, so we skip the "ubern", and now we have "K'8s", which just becomes "K8s".


Hi Thorsten. This is what Google themselves say..


But who knows what else is true ;)


Yeah it's a similar principle to internationalisation being shortened to i11n as it has 11 letters in the middle and just makes it quicker to type and slightly quicker to say

But... it's i18n, because 18 letters have been dropped.


Hi Chris,

I have a doubt whether Its worth for .NET developers to learn kubernetes. Can you explain by adding some comment on below post. I have posted it long ago but no answers.



hi Shaijut. In trying to answer you I must make some assumptions. When you say .NET you mean .NET and not .NET Core.. Let's assume you are doing .NET Core, so you can easily containerize. Otherwise I think App Service is your only option. For me, Kubernetes vs App Service is a matter of what architecture I have. If I have several Microservices rather than a Monolith then I need an orchestrator like Docker Swarm, Kubernetes or similar. The reason is to be able to scale easily, load balance and whatever else you need. App Service does a decent job of scaling as it is a PaaS but I would say if you have a very large operation 500k users and a Microservice Architecture it makes sense to look further into Kubernetes and AKS for example . Azure Service Fabric is another option we have. For ppl already using it, keep using it. For others, look into AKS.. We support multiple ecosystems for containers but all indications I have says the future is Kubernetes. Don't take that as an official statement though


Thanks for detail explanation 😄, Actually I heard someone saying two points 1. For .NET Core Apps Azure Service Fabric is good choice. 2. Use Kubernetes for other stacks like Java, NodeJS etc...

So from your comments I am able conclude that I being a .NET Developer its worth to learn Kubernetes. Actually planning to do Kubernetes certification.


Excellent post @softchris !

There are a couple of typos:

  • curl http://localhost:8001/api/v1/namespaces/default/pod/$POD_NAME should be curl http://localhost:8001/api/v1/namespaces/default/pods/$POD_NAME

  • curl http:localhost:8080 should be curl http://localhost:8080


Thanks :) Appreciate your comments


Thanks for this awesome writeup. I think there's a little typo here

Instead of typing kubectl proxy we can now type curl http://localhost:8001/version and get the same results:

I think it should be

Instead of typing kubectl version we can now type curl http://localhost:8001/version and get the same results:


Hi thanks. Appreciate you pointing that out :)


Great read, thanks for sharing your knowledge in an easy to understand way. Looking forward to part 3.

Just a small suggestion. A link to the next article in the series at the bottom helps the reader move on without having to scroll all the way back to the top to find the link


Hi Sam. Thanks for that. Will update it


You're welcome 😀


Really nice post.

I got a small setup at home for some local services with docker-compose. Do you think its worth it to switch to k8s with a single node (master)? Or is it to much overhead to maintain it?


hi Martin.. I'd say it depends. If you are hosting it in the Cloud then horizontal scaling is enabled by default and that might be all you need. To me it sounds like it might be overkill but trying it out on a hobby basis is how most of us learn anything


Thanks Chris for this, I too am fascinated by Kubernetes, wrote up a post on



For windows 10 users with HyperV, you must explicitly specify 'hyperv' as a driver since minikube use VirtualBox by default.

minikube start --vm-driver=hyperv


Dang it. Take my heart. I appreciate that high quality gif.


Great, soft, and effective introduction about k8s. I'm looking forward for part two. In fact, I'm looking forward to the entire series. Please do more ☸️


part two is here dev.to/azure/kubernetes-part-ii-re... working on part 3 :)


Excellent introduction! Thank you!


Thank you :)


when will you do part 2. I am exciting about it.


Nice read, Chris. Looking for next part!


Thanks a lot. I learn so much of all your articles


hi Lucas. That's very nice of you to say. Thank you.. :)


Nodes were historically called Minions, but not so anymore. :(


yea it's the most disappointing thing about K8s :)


Wow awesome, can't wait for part 2


hi Ariaseta. Thanks for the comment :). The 2nd part is gonna be published in the next week.


Exceptional Post on Dev.to about Kubernetes a.k.a K8. Already looking forward to Part II


hi Ali. Really appreciate that comment.. thank you.. Yes will work hard to release second part in the next few days :)

Code of Conduct Report abuse