What is Kubernetes

Показать описание

You have a working knowledge of Docker and you're looking to take your container game to the next level. Time to take a look at Kubernetes. In this video, you'll learn about what Kubernetes is and some of the main benefits that you can get from using it. We'll talk about how Kubernetes makes deploying, scaling, and maintaining Docker containers (or rather just containers in general) easier in the wild and at scale.

-~-~~-~~~-~~-~-
Please watch: "How to Write Better Automated Tests"
-~-~~-~~~-~~-~-

Рекомендации по теме

Комментарии

When you add more containers, you are not scaling up but scaling out. Scaling up means adding more resources to the same server.

TarikGuney

I've looked up this alien word "Kubernetes" at least twice before and never found an explanation that came close to making sense. This video does a great job of explaining! Thanks!

matthewm.

Has Kubernetes been on your radar or is this your first introduction? Where might Kubernetes be useful for you?

Coderjourney

Kubernetes is for orchestrating containers. In provides a framework to define infrastructure. The cluster will orchestrate the infrastructure for you and deal with connecting everything together, setting up ip addresses and dns, and most importantly maintaining the infrastructure should cluster nodes die. It also allows you to redeploy infrastructure without interruption, should a new container image be introduced.

armunro

This playlist is the best explanation for kubernetes I have found to date.

saurabhs

Better explanation than the VMware channel. Thanks!

jboomhauer

Thanx for the really simple and straight forward video. I just read about Kubernetes this morning and some how my reading lead me to this video and I am amazed at how awesome Kubernetes is. Thumbs up.

michaelkasede

I work as an infrastructure/devops developer on a lot of large websites around the world at public webscale and have been working with containers for a while now and it really annoys me that still... developers are not properly developing micro-service architecture from the app layer to container layer...
I have spent countless training sessions trying to get it in to developers heads to start coding at the functional service level thinking about the container level... that is - develop each of your services to be loosely coupled in a way that you can seperate core functions in to their own services that run on their own containers, this means scaling can actually be significantly more efficient and my job as an infrastructure developer becomes much more effective.
Do people understand what I mean by this?
I mean you basically seperate each core function in your code to its own "service" then when scaling you can scale individual functions/components of the complete application stack... no longer is an application just one say java app but multiple java apps that all talk to each other, then when I develop the infrastructure stack I can design intelligent metrics that can read the load for each service and scale out these components uniquely... when done right its truly beautiful

basslinr

Hey, Thanks for this nice effort.
Your audio is so clear and crisply done...
Can you please share your setup info...like mic, post processing etc

JagdishAdusumalli

Excellent job! Great voice! And great overview of Kubernetes. I have bookmarked this and will share! Well Done.... rare that I see work of this quality on Youtube. Keep it up... you've got a talent!

fredeberlein

You did an outstanding job explaining this. As a Newbie to this particular technology, you covered exactly what I was looking for. I wish you the best at dealing with all of the "Opinion Monsters" who work as SysAdmins in the comments. Great audio too!

busyrand

Great. Really enjoy such short and to the point explanation. Got good understanding of Kubernetes

vittal

Awesome Intro, I'm so watching the rest of your videos! Thanks for the great content!

inafew

Thank you for this. A big problem with being a programmer is that it's a completely ungrateful field. No matter how much you learn/know, you'll be out of date 5 years later, obsolete 10 years later. After so many years of thinking "docker is junk, we solved this problem 30 years ago with chroot", I find myself having to submit.

andychow