Container Orchestration Explained
Vložit
- čas přidán 16. 04. 2019
- Learn more about Kubernetes: ibm.biz/BdPSfw
Check out the IBM Cloud Kubernetes Service: ibm.biz/BdPSft
We've talked about containerization already, and now Sai Vennam is going to take a step back and talk about why container orchestration is necessary in the first place.
Get started for free on IBM Cloud → ibm.biz/sign-up-today
#ContainerOrchestration #Containers #Kubernetes - Věda a technologie
IBM employees are so good at teaching... Thank You...
And at writing backwards.
Couln't be truer. I almost feel like I'm becoming a cloud-guru, simply because of these videos. Kudos to IBM for this.
@@ericsiggyscott173 They just mirror the video lol
@@ericsiggyscott173 😂😂😂😂
IBM is best at solutions
This is a fantastic capsule of knowledge on the essence of service orchestration. A term that is widely used, but not understood by any. I recommend to anyone who is keen on getting the big picture right. Thanks Sai
Glad to hear it, Bala. We appreciate you watching our videos.
Excellent illustration. Simple and well detailed to understand.
Never thought I'd have Venom explaining cloud concepts to me.
Man! I've always hated containers, but this video motivated me to learn more about containerization. Simple, straight to the point,,,,, 10 points :)
We love to hear that, Adam!
Great Sai.Well explained, waiting for more videos on Kubernetes.
The timestamp synched links to the relevant videos in the corner is just *chefs kiss*
Sai , you have a subtle tone in voice that settles gently on the ears and diffuses in like the smoke cloud from the incense sticks our moms use. The board is an excellent choice.
Great explanation. The more i see your videos the more curious i am getting. Continue your great work.
This is one of the best tech channels on CZcams. Congratulations 🎉
A very clean and on point explanation.
It made so much sense! Thank you IBM!
Very comprehensive! Thank you very much!
Thank You IBM for everything.. from my first PC Aptiva to this tutorial present day. :)
This is as concise as it gets!
Really good explanation. Thanks.
IBM is true IT services solutions provider
Great explanation with frindly diagrams.
Great video!
Amazing video Sai
The things that container orchestration will do:
1. Deployment
2. Scaling: schedule containers to the right worker node for the best resources utilization
3. Networking: create load balancers for external and internal services communication
4. Operations and Insight: automatically bring up instances of a services in failure; provide integration points for service mesh and logging
You explain it very nicely
Thank you for the great video. It gives a great explanation of the concepts
Thank you for making this fabulous video
Great explanation with ilustration. i thank you.
This was very helpful, thank you!
Thank you IBM for this video (:
Very well explained. Thank you so much
Amazing explanation. Thank you
Very clear and straight forward. Great whiteboard presenter. IBMer.
Thanks for watching!
The part that intrigued me the most about this lesson was his insane skills to write backwards 😂
See ibm.biz/write-backwards
to the point . well explained . thank you
lucid explanation....thanks a ton
impressive explanation!!!
straight forward thank you
Greatly explained, to the point, thank you! I would suggest to put load balancing (instead of putting it under network), availability with self healing. I would say that Containers is something that all developers and ops engineers need to learn as the essential component in building and running cloud native applications. It also brings next level/generation of virtualisation in a platform and language independent way.
Very well explained, thank you 🙏
Brilliant !
Superb explanation about orchestration.
Nice one! Quite helpful! :)
great teaching..
Amazing and simplified way of explanation . Thanks a lot Sai. This video adds to my knowledge.
Thank you, Nagakalyan!
@@IBMTechnology at 5:50 , I have heard Sai stating that as part of netweorking orchestration helps achieve singular point of access to the services (based on the video). Does it mean , the orchestration platform spinf a load balancer/would it be a single IP to all the simlilar services (example front end, back end , data base services).
Very well explained. It was like eating strawberries. Thanks!
Did anyone notice that he was writing backwards mirrored? This is how some folks used to write status on glass on a warship... amazing talent... oh and btw great explanation too
awesome video
Excellent. Thank you!
You're welcome! 👍
Hey Sai..Nice videos
I like this video. A very good ABCD guy. Container Orchestration
Intresting. Is there a video on how to do capacity planning?
thank you! :)
At 1:43 minutes, you say that these containers have key things like apps, OS and dependencies. But, in a previous video you said that containers do not contain OS. So, what is the reason behind mentioning OS here?
I have the same question
To help anyone who sees this comment:
Containers themselves do not contain an OS.. but what a container does is create a new interface/bridge between the processes inside of the container and the host/baremetal OS. For example, say I make a system call in my program to see what files are in the local running directory of the program. This is done by calling an OS function that does interaction with the kernel. What containers do (which is why it is called virtualization), is it asks the host kernel to create an interface that "lies" to the running process about what it is seeing as its local environment (a "virtual" environment one could say).
So when the process asks the kernel through system call what the heck is going on, the kernel gives it a virtual likeness of what is going on. This allows the OS to impersonate different file structures/networking/compute resources different from its actual setup (though not different kernels). Because of this, we can target a specific version of an OS and guarantee our application's local environment by virtualizing it with a container, and gives us an easy way to describe and share our target environment. Containers are not "virtual OSes", they are more aptly described as "virtualization of the OS environment for a group of one or more processes".
Great Video. We'll explained.
Thank you Ryan!
Simply great
Good for beginners
Hi Sai, excellent representation. Could you please comment on, how much indepth knowledge of Containers/ orchestration/ K8s is required from a Project manager's PoV? I dont have any hands on.
Question: what tools did you use to create this transparent overlay effect?
@7:55 FE will never access DBService directly for safety , but, good draw and thanks for sharing
Nice
Great stuff. Are you really writing backwards so well?
You can write stuff normally and then mirror the video)
@@MinecrafterKost No reason to ruin the illusion. :)
0:34 why isnt database access layer part of backend?
Do you have a book recommendation for working with this subject matter scientifically?
Great videos, thanks...
I have question, how does it manage multiple DB replicas ? Will the Write operation performed to all the DB replica's ? Blocking reads during it ?...
Writes would be typically done directly to primary DB. at set intervals, there would be a delay in DB syncing primary to replica, this way read from replica is always available. During the synch, the replica would be locked.
Kubernetes [container orchestration] is capable of setting up primary and multiple replicas, you just have to define in the YAML file.
you mentioned prometheus, can you create a tutorial about kubernetes and prometheus
We will take a look at that. --Sai
َAre those Nodes VMs ? Which means we have 4 VMs here (3 Worker Nodes and 1 Master Node) ?
So with Kubernetes, you don't need a load balancer or service discovery/registry? It's all included?
Yes, that's right!
@@svennam92 is it correct to say that the only benefit of using a service mesh (istio) with kubernetes are features like rate limiting, circuit breakers, improved telemetry?
I'm asking because we are currently using consul for service discovery and gradually shifting to kubernetes but not sure if we need a service mesh too
just for the feedback, sir! your accent sounds good for listening purposes but for understanding, it is quite hard.
Wait so Kubernetes has to run on it's own server? Won't that increase your costs by, in this case, 33% if you now need a whole new vm?
And you want 3 backend services? Is any of this relevant for a typical startup that can manage just fine with one server?
✅✅
Can you call front end as a microservice?!
Venommmmm!!!!
How to get a job at IBM:
Step 1 - Learn to write backward
Developers may see a "singular view of the world," as you say, but that is a good thing. Keep in mind that without applications (and developers), users have no reason to use an "orchestration" system in the first place. Without customers using APPLICATIONS, you don't have a business.
but at least explain what is orchesteration
He writes backwards.
Hi Mauro...many people think I do, but here's an explanation of how we make these videos. these videos here: ibm.co/2SA1vGd Thanks for checking us out, San
I thought the same thing... nice. Thanks IBM to clarify our question.. :)
Very disconnected🙄 explanation
Although your explanation was good I still found it difficult to understand this topic