DEV Community

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 post

Thorsten Hirsch • May 19 '19

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".

Chris Noring • May 19 '19

Hi Thorsten. This is what Google themselves say..

kubernetes.io/docs/concepts/overvi...

But who knows what else is true ;)

Sam Benskin • May 23 '19

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

Thorsten Hirsch • May 23 '19

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

Sam Benskin • Jul 14 '19

...doh!

Jayendran Arumugam • Feb 9 '21

After running the below

kubectl run kubernetes-first-app --image=gcr.io/google-samples/kubernetes-bootcamp:v1 --port=8080

When I run kubectl get deployments its gives back like No resources found in default namespace.

So I ran like
kubectl create deployment kubernetes-first-app --image=gcr.io/google-samples/kubernetes-bootcamp:v1 --port=8080

Then the deployment list can able to work. Not sure whether I missed any earlier steps.

Dendi Handian • Jan 12 '21

It's failed to start on my machine:

C:\Users\dendi>minikube start
* minikube v1.15.1 on Microsoft Windows 10 Home Single Language 10.0.19041 Build 19041
* Using the hyperv driver based on existing profile
* minikube 1.16.0 is available! Download it: https://github.com/kubernetes/minikube/releases/tag/v1.16.0
* To disable this notice, run: 'minikube config set WantUpdateNotification false'

* Starting control plane node minikube in cluster minikube
* Creating hyperv VM (CPUs=2, Memory=3000MB, Disk=20000MB) ...
! StartHost failed, but will try again: creating host: create: precreate: Hyper-V PowerShell Module is not available
* Creating hyperv VM (CPUs=2, Memory=3000MB, Disk=20000MB) ...
* Failed to start hyperv VM. Running "minikube delete" may fix it: creating host: create: precreate: Hyper-V PowerShell Module is not available

X Exiting due to PR_HYPERV_MODULE_NOT_INSTALLED: Failed to start host: creating host: create: precreate: Hyper-V PowerShell Module is not available
* Suggestion: Run: 'Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Tools-All'
* Documentation: https://www.altaro.com/hyper-v/install-hyper-v-powershell-module/
* Related issue: https://github.com/kubernetes/minikube/issues/9040

Chris Noring • Jan 12 '21

Seems like the error message is saying what's wrong

Hyper-V PowerShell Module is not installed

Here's a thread where people seem to have a similar issue, maybe that helps?
github.com/kubernetes/minikube/iss...

Shaiju T • Mar 2 '20

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.

dev.to/shaijut/kubernetes-vs-azure...

Chris Noring • Mar 2 '20

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

Shaiju T • Mar 2 '20 • Edited

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.

Chris Noring • Mar 2 '20

np :). Here's some resources to get you started docs.microsoft.com/en-us/azure/aks... dotnet.microsoft.com/apps/aspnet/m...

Arnold Acho • May 28 '19

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:

Chris Noring • May 28 '19

Hi thanks. Appreciate you pointing that out :)

Sam Benskin • May 23 '19

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

Chris Noring • May 23 '19

Hi Sam. Thanks for that. Will update it

Sam Benskin • Jul 14 '19

You're welcome 😀

Eammon Hanlon • May 19 '19 • Edited

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

Chris Noring • May 19 '19

Thanks :) Appreciate your comments

Martin Huter • May 20 '19

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?

Chris Noring • May 20 '19

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

Grégoire Willmann • May 21 '19

Excellent introduction! Thank you!

Chris Noring • May 25 '19

Thank you :)

jericomanapsal • May 19 '19

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 ☸️