OpenShift 4.8 brings, among other improvements, an additional OCI-compliant runtime based on Kata Containers, NVIDIA multi-instance GPU, OpenShift Pipelines, IPv6 support, and serverless functions as a technology preview.
In competing visions of the future of Kubernetes, Paul Czarkowski, principal technologist at Pivotal, predicts that VMs will replace containers, and Joe Fernandes, a VP at Red Hat, considers that VMs usage is evolving for Kubernetes rather than replacing containers. In addition, Chris Short, Red Hat's principal product marketing manager, said that Kubernetes is close to replacing the hypervisor.
TL;DR: containers are not VMs; stop calling everything "Docker"; don't use Kubernetes for tiny projects, use Swarm instead; Kubernetes will only solve your org's problems if you are willing to go all-in, anything in between will fail the same way it failed before.
Today Rancher Labs is announcing a new open source project, k3s, which is a lightweight, easy to install Kubernetes distribution geared towards resource-constrained environments and low touch operations.
The cost and performance models are two of the key drivers of the popularity of serverless and Function-as-a-Service (FaaS).
Cold starts have gone down a lot, from multiple seconds to 100s of milliseconds, but there is still much space for improvement.
There are various techniques that are being used to improve the performance of serverless functions, most of which focus on reducing or avoiding cold starts.
These optimizations are not free; it is a trade-off between performance and cost, which depends on the requirements of your application.
Currently, closed-source serverless services offered by public clouds offer few options for users to influence these trade-offs. Open-source FaaS frameworks that can run anywhere (such as Fission) offer full flexibility to tweak these performance/cost tradeoffs.
Serverless computing is not just about paying for the resources that you use; it is about only paying for the performance you actually need.