Knative 1.0, a platform for Kubernetes serverless

Google recently unveiled the new version of the Knative 1.0 platform which is positioned as stable and designed to create a serverless computing infrastructure deployed on a container isolation system based on the Kubernetes platform.

In addition to Google, companies such as IBM, Red Hat, SAP and VMware are also involved in the development of Knative. The release of Knative 1.0 marked the stabilization of the API for application development, which will remain unchanged from now on and will remain backward compatible.

Today, the Knative project released version 1.0, reaching an important milestone that was made possible by the contributions and collaboration of more than 600 developers. Over the past three years, Knative became the most widely installed serverless tier in Kubernete s.

The Knative project was launched by Google in July 2018, with the vision of systematizing best practices in the development of native applications in the cloud, with a focus on three areas: container construction, service and scaling of workloads and events. .

For those who are unfamiliar with the Knative platform, they should know that this specializes in the launch of containers prepared as needed (the application is not tied to any specific container), organizes management and provides scaling of the environments required to perform functions and applications.

Platform It can be deployed on your own premises without having to be linked to external cloud services. Only Kubernetes is required to run, providing a wealth of tools to support a wide variety of common frameworks, of which Django, Ruby on Rails, and Spring are already included.

It is also important to mention that the command line interface (CLI) can be used to control the operation of the platform. The platform provides two main components:

  • Serving- Deployment and management of applications and functions in the form of serverless containers. Containers run on Kubernetes with automatic network configuration, routing, change tracking (creating snapshots of hosted code and configuration), and maintaining the required level of scaling (down to zero pods in the absence of activity). The developer focuses only on logic, everything related to execution is handled by the platform. The Ambassador, Contour, Kourier, Gloo, and Istio network subsystems can be used to organize network and route requests. There is support for HTTP / 2, gRPC, and WebSockets.
  • Events: is a universal system for subscribing (attaching drivers), delivering and managing events. It allows the creation of asynchronous applications by attaching computational resources to data flows using the object model and event handling. Knative Eventing's high-level mission is: Enable asynchronous application development by delivering events from anywhere.

What's new in Knative 1.0?

In this new version 1.0 an autoscaling has been performed (including zero scaling), plus revision tracking and developer abstractions were some of Knative's first goals.

In addition to meeting those goals, the project also incorporated support for multiple layers of HTTP routing, support for multiple layers of storage for event concepts with common subscription methods, and designed an abstraction of "duck types" to allow processing of arbitrary Kubernetes resources that have common fields, to name a few changes.

Knative is now available in 1.0, and although the API is closed for changes, its definition is publicly available so that anyone can demonstrate compliance with Knative. This stable API enables customers and vendors to support application portability and establishes a new cloud-native developer architecture.

Finally, if you are interested in knowing more about this new version, you can consult the details In the following link.

As for those who are interested in knowing about this platform, they can consult the following link.

The content of the article adheres to our principles of editorial ethics. To report an error click here!.

Be the first to comment

Leave a Comment

Your email address will not be published.



  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.