Knative lets you set minimum and maximum levels for CPU share and bytes of RAM. This is another case of directly exposing the underlying Kubernetes feature, which is called resources. (link)
It modifies any probes so that their port value is the same as the port value of the container itself, which will be the same as the PORT environment variable that’s injected. (link)
This leads to different treatment for each kind of probe. When liveness checks fail, Kubernetes eventually kills the container and relaunches it someplace else. When readiness checks fail, Kubernetes prevents network traffic from reaching the container (link)
Software that’s otherwise alive might not be ready for traffic. For example, during a long startup, the software is alive, but it’s not ready (link)
Remember that Knative Serving spits out a new Revision every time you touch the template. That includes environment variables, which can be used to change system behavior. (link)
The names of labels and annotations follow a pattern: .knative.dev/ (link)
changing the template causes Revisions to be created. (link)
A Configuration is a definition of your software. (link)
Revisions are created only when Configurations are changed or created. (link)
Kubernetes explicitly models its architecture on feedback control loops and provides infrastructure to enable the easy development of a variety of controllers for different purposes. Kubernetes then uses hierarchical control to layer responsibilities: Pods can be supervised by ReplicaSets that are supervised by Deployments. (link)
This should be recognizable as architectural layering according to the Single Responsibility Principle (link)
Blocking is still blocking, but blocking on threads is faster than blocking on HTTP. (link)
Each Service combines a Configuration and a Route. (link)
These are snapshots of a Configuration. Each time that you change a Configuration, Knative first creates a Revision (link)
As a developer, Knative gives you three basic types of document you can use to express your desires: Configuration, Revision, and Route. (link)
Each Trigger represents an interest in some set of events and where to forward these. (link)
Vikram: [Is it the same as subscription?]
NOTE Inventory, capacity, and time really are the only options for buffering variability (link)
This layer creates a firmer boundary between the developer and the platform, allowing the developer to concentrate on the software they are directly responsible for. (link)
Knative builds on the toolbox Kubernetes provides, but it also sets out to achieve a level of consistency, simplicity, and ease of use that brings Kubernetes much closer to meeting the Test’s high standard. Knative is a machine (link)