Most of what is written about Computer science by computer scientists is embarrassing bullshit to the uninitiated. But the ones that usually refer to it as bullshit are the ones that have absolutely no idea what the entire field is about, not even an inkling of how the resident gurus think, nor even of what is being talked about. It is the ones who call it ‘bullshit’ that are the ones trying to pretend they understand in depth what it is all about. You do not want us to be honest, you want us to speak in terms that you might have a chance of understanding. Unfortunately, the language of Computer Science, like science in general, has to be absolutely precise so as to not be misinterpreted. It can not be ‘dummed down’ without losing much of its utility to other scientists.
I could have said "Kubernetes defines a set of building blocks (“primitives”) that collectively provide mechanisms that deploy, maintain, and scale applications based on CPU, memory[29] or custom metrics.[30] Kubernetes is loosely coupled and extensible to meet the needs of different workloads. The internal components as well as extensions and containers that run on Kubernetes rely on the Kubernetes API.[31][32]
"The platform exerts its control over compute and storage resources by defining resources as objects, which can then be managed as such.
“Kubernetes follows the primary/replica architecture. The components of Kubernetes can be divided into those that manage an individual node and those that are part of the control plane.” https://en.wikipedia.org/wiki/Kubernetes
But that is just a very fancy way of saying that Kubernetes developers look at a very complex computing environment consisting of many hardware vendors, several operating systems, several architectures, (some incomparable) but one common application outcome, and integrating them all together into one centrally controlled and managed interface using a common instruction set and command structure…
I should clarify that ‘YAML’ is used facetiously and generically to refer to the concept of ‘yet another markup language’ as an allegory, without specifically meaning Kubernetes produces the true implementation of ‘YAML’ the formal system. Maybe we should coin a new term ‘YAMLized’. That is, 'reduced to ‘yet another markup language’.
Most of what is written about Computer science by computer scientists is embarrassing bullshit to the uninitiated. But the ones that usually refer to it as bullshit are the ones that have absolutely no idea what the entire field is about, not even an inkling of how the resident gurus think, nor even of what is being talked about. It is the ones who call it ‘bullshit’ that are the ones trying to pretend they understand in depth what it is all about. You do not want us to be honest, you want us to speak in terms that you might have a chance of understanding. Unfortunately, the language of Computer Science, like science in general, has to be absolutely precise so as to not be misinterpreted. It can not be ‘dummed down’ without losing much of its utility to other scientists.
I could have said "Kubernetes defines a set of building blocks (“primitives”) that collectively provide mechanisms that deploy, maintain, and scale applications based on CPU, memory[29] or custom metrics.[30] Kubernetes is loosely coupled and extensible to meet the needs of different workloads. The internal components as well as extensions and containers that run on Kubernetes rely on the Kubernetes API.[31][32]
"The platform exerts its control over compute and storage resources by defining resources as objects, which can then be managed as such.
“Kubernetes follows the primary/replica architecture. The components of Kubernetes can be divided into those that manage an individual node and those that are part of the control plane.” https://en.wikipedia.org/wiki/Kubernetes
But that is just a very fancy way of saying that Kubernetes developers look at a very complex computing environment consisting of many hardware vendors, several operating systems, several architectures, (some incomparable) but one common application outcome, and integrating them all together into one centrally controlled and managed interface using a common instruction set and command structure…
I should clarify that ‘YAML’ is used facetiously and generically to refer to the concept of ‘yet another markup language’ as an allegory, without specifically meaning Kubernetes produces the true implementation of ‘YAML’ the formal system. Maybe we should coin a new term ‘YAMLized’. That is, 'reduced to ‘yet another markup language’.