Principles mentioned: 1. Kubernetes APIs are declarative rather than imperative. 2. The Kubernetes control plane is transparent. There are no hidden internal APIs. 3. Meet the user where they are. 4. Workload portability.
also at 30:53, great presentation! I would like to add some discussion at the end to reflect those points: 1. Self-healing, extensible 2. Immutable. transparent 3. Ease of adoption 4. Cloud/Cluster agnostic - separation of concern, easy for maintenance
Excellent presentation.. Hats off!! Very precise very detailed.. If one is architect he understand each and evey word in depth... His explaination is very simple but huge is meaning microservice deployement to containerization
One thing missing from this presentation: why k8s in the first place? It took me a while to answer this: horizontal scaling. How do you use up more resources by creating replicas of your software and running them on different machines instead of having a single copy of your software running on a beefier VM. This actually is a slight paradigm-shift from the traditional "one executable" model.
Yup. This video is having very less views for the content and presentation it has to offer - watching it will definitely fill in the gaps in k8s understanding for anyone.
It more sounds to me that Kubernetes just rebranded OSGi principles and used containers instead of bundles as primitives. Its a great achievement by k8s but they could at least attribute where they borrowed the core concepts from.
@@karimmanaouil7278 If you know OSGi then you'd understand the conceptual similarities I was pointing out. My comment (2yrs) ago was more on the ironic side. Similarities are because concepts such as a declarative api with extensible control plane (whiteboard pattern) are good ideas. Both OSGi and Kubernetes implemented them. At different scales: one is for orchestrating java components (through services & bundles) and the other for containers. Just wanted to make that clear. No worries.
@@ToniMenzel82 makes sense what you said and I totally agree. My previous reply was addressing the part where you said that the k8s authors should attribute OSGi because they got the concepts from there, and I just wanted to point out that they probably had no idea about OSGi. Many concepts gets rediscovered independently all the time in software engineering, but in different contexts.
We are awslagi team on Udemy. We are providing actual exam for GCP and AWS. We ensure you can pass the exam at the first attempt in the fastest and easiest way.
Fuck you!!! you will see what you have in your heart. There is racial discrimination in your mother's heart, and everything is racial discrimination. The pure land of technology is all dirty by you hybrids! ! !
Do you seriously believe that pushing for this will serve BLM cause? My impression so far is that it only makes you and the cause seem ridiculous. You won't get even by changing the language in totally irrelevant areas. You'll only make things and root causes _harder_ to see next time this happens.
![CNCF [Cloud Native Computing Foundation]](http://yt3.ggpht.com/txe66EjpkDQQlx_4jDV0yA0PPsww0rqQrFhMpDqagLWN2-EUBBO65IuIyy5tEFVmpI4_RRduzXc=s48-c-k-c0x00ffffff-no-rj)
The single best video on RUclips that explicates the Kubernetes design philosophy. Very helpful.
Principles mentioned:
1. Kubernetes APIs are declarative rather than imperative.
2. The Kubernetes control plane is transparent. There are no hidden internal APIs.
3. Meet the user where they are.
4. Workload portability.
also at 30:53, great presentation! I would like to add some discussion at the end to reflect those points:
1. Self-healing, extensible
2. Immutable. transparent
3. Ease of adoption
4. Cloud/Cluster agnostic - separation of concern, easy for maintenance
Excellent presentation.. Hats off!! Very precise very detailed.. If one is architect he understand each and evey word in depth... His explaination is very simple but huge is meaning microservice deployement to containerization
In Kubernetes, You do not tell the system....
The system tells you.......
😂
Excellent explanation and much-needed insights about Kubernetes components
Thanks Saad, I enjoyed the presentation - a good starting primer as I get into Kubernetes
One thing missing from this presentation: why k8s in the first place? It took me a while to answer this: horizontal scaling. How do you use up more resources by creating replicas of your software and running them on different machines instead of having a single copy of your software running on a beefier VM. This actually is a slight paradigm-shift from the traditional "one executable" model.
Very useful explanation, thank you very much.❤
Excellent talk on kubernetes. I’m new to this tech, coming from Hadoop world, this talk helped me to get understanding of the internals
Whole-to-parts learning, thank you. Can’t go shopping without a basket!
Damn, the talk makes k8s so obvious
This is super insightful and very valuable❤❤
Great video thanks. I wish I saw this 3 years back
Yup. This video is having very less views for the content and presentation it has to offer - watching it will definitely fill in the gaps in k8s understanding for anyone.
no explanation about schedule and workload distribution
Great talk, excellent presentation!
Kubernetes is the Holy Grail of modern software design patterns.
It more sounds to me that Kubernetes just rebranded OSGi principles and used containers instead of bundles as primitives. Its a great achievement by k8s but they could at least attribute where they borrowed the core concepts from.
@@ToniMenzel82 Kubernetes is an application deployment system that was inspired from Borg. It has nothing to do with OSGi.
@@karimmanaouil7278 If you know OSGi then you'd understand the conceptual similarities I was pointing out. My comment (2yrs) ago was more on the ironic side. Similarities are because concepts such as a declarative api with extensible control plane (whiteboard pattern) are good ideas. Both OSGi and Kubernetes implemented them. At different scales: one is for orchestrating java components (through services & bundles) and the other for containers. Just wanted to make that clear. No worries.
@@ToniMenzel82 makes sense what you said and I totally agree. My previous reply was addressing the part where you said that the k8s authors should attribute OSGi because they got the concepts from there, and I just wanted to point out that they probably had no idea about OSGi. Many concepts gets rediscovered independently all the time in software engineering, but in different contexts.
Ain’t you two the sweetest❤
Amazing presentation
Very informative! Thank you
Very informative!
Great video thanks :)
Very informative! Thank you
Thanks Saad Ali
amazing!
Excellent 👌
nice stuff
Awesome presentation. Very informative
Thank you’re
Is a backup solution such as Kasten highly sought after for stateful workloads since volume plug-ins exist?
Thanks
Good one,,
In Kubernetes, You do not tell the system....
The system tells you.......
CockRoach DB?!! Oy VAy!!!!
The coughing is insane
Slave? No more please. Kubernetes uses worker instead. This is the progress.
We are awslagi team on Udemy. We are providing actual exam for GCP and AWS. We ensure you can pass the exam at the first attempt in the fastest and easiest way.
please stop using the term slave or concentration camp or internment camp or 911 towers as descriptive terms in our field.
Nobody cares
grow the f up
Fuck you!!! you will see what you have in your heart. There is racial discrimination in your mother's heart, and everything is racial discrimination. The pure land of technology is all dirty by you hybrids! ! !
Do you seriously believe that pushing for this will serve BLM cause? My impression so far is that it only makes you and the cause seem ridiculous. You won't get even by changing the language in totally irrelevant areas. You'll only make things and root causes _harder_ to see next time this happens.
"K LR" is a fucking idiot.