Summary: Knative recently reached an important milestone with the release of version 1.0. Since Knative was first released in July 2018, the version has evolved iteratively, with a number of chronological improvements, outlined below, in addition to numerous bug fixes, stability, and performance enhancements.
Author: Yuan Yi
takeaway
Knative is an open source Serverless application framework based on Kubernetes, which helps users to deploy and manage modern Serverless workloads and build enterprise-class Serverless platforms. Knative has the following advantages:
- Build scalable, secure, stateless services in seconds.
- Apis with higher levels of Kubernetes application abstraction.
- Pluggable components that allow you to use your own logging and monitoring, network, and service grids.
- You can run Knative anywhere Kubernetes runs without worrying about vendor lock-in.
- Developers have a seamless experience with support for GitOps, DockerOps, ManualOps, and more.
- Support for common tools and frameworks, such as Django, Ruby on Rails, Spring, etc.
Knative 1.0
Knative recently reached an important milestone with the release of version 1.0. Since Knative was first released in July 2018, the version has evolved iteratively, with the following improvements in chronological order, in addition to numerous bug fixes, stability and performance enhancements:
- Support for multiple HTTP routing layers (including Istio, Contour, Kourier, and Ambassador)
- Support for event-driven Eventing concepts and common subscription methods (including Kafka, GCP PubSub, and RabbitMQ)
- The “duck type” abstraction allows processing of any Kubernetes resource with common fields such as status.conditions and status.address
- Command line client that supports additional functionality plug-ins
- 6 Weekly regular release process
- Support HTTP/2, gRPC, and WebSockets
- Brokers and triggers to simplify publishing and subscribing to events while decoupling producers and consumers
- Support for event components to be passed to non-Knative components, including out-of-cluster components or specific urls on hosts
- Support for automatic provisioning of TLS certificates (via DNS or HTTP01 challenge)
- Custom event delivery options, including retries for undeliverable events and dead-letter queues
- Event tracing support for brokers and channels to improve debugging
- Tekton project spawned by Knative Build
- Support for parallel and sequential components for orchestrating the workflow of events
- Documentation for event sources and how to contribute to the description, which currently covers about 40 different event sources
- No Interrupt smooth upgrade, no request interrupt during minor version upgrade
- Redesigned Serving API to match PodTemplateSpec used by Deployment, CronJob, etc., simplifying Kubernetes user usage
- Support for injecting event target addresses into PodTemplateSpec objects
- Supports automatic expansion and scaling of horizontal Pod based on concurrency or RPS
- High availability of control plane components using leader election
- Provides an Operator to help administrators install Knative
- Quick start for developers to try Out Knative locally
- Use DomainMapping to simplify service management and publishing
How many fans Knative has
From the birth of Knative to the 1.0 release, a series of questions like: How many enterprises are using Knative? Is it available for production?
According to CNCF 2020 China Cloud Native Survey report, Knative has become the most widely installed serverless on Kubernetes.
In addition, the Knative community recently launched a survey of which cloud vendors or enterprises are currently offering or using Knative. Here’s how it’s counted (and the list is still being updated) :
We can see that almost all large manufacturers support or integrate Knative, such as Ali Cloud, Google Cloud, IBM, Red Hat, etc., and most of them provide Production level capabilities. With the release of Knative 1.0, We believe that more users will embrace Knative.
Ali cloud Knative
Ali Cloud container service started product integration from Knative version 0.6.0, continued to follow up the function iteration of Knative community, and now fully supports Knative version 1.0. During this period, Ali Cloud Knative and container service Kubernetes ecology, messaging, storage and other cloud products have been integrated in an all-round way. Include:
- Rich message cloud product event sources: Kafka, MNS, RocketMQ
- Service access: SLB
- Storage: NAS and cloud disks
- Observability: Logging service, ARMS
- IaaS resources: ECS and ECI
In addition, in order to reduce the threshold for users to use Knative, the container service UI console provides one-click deployment capability, and fully hosts The Knative control components in Serverless Kubernetes (ASK), which greatly saves users’ resources and operation and maintenance costs.
In the continuous iteration of productization, it also brings more abundant customer application scenarios. Currently, typical application scenarios of Ali Cloud Knative (including but not limited) are as follows:
- AI audio and video coding/decoding scenarios
- Heterogeneous computing scenarios such as GPU
- Big data and AI deep learning, machine vision
- Traditional management software
- .
The industry covers smart healthcare, online education, digital space modeling and other fields. Ali Cloud container service Knative is continuously providing users with enterprise-class Serverless platform capabilities.
summary
If you’re struggling with complex and diverse Kubernetes resources (Deploymemt, Service, Ingress, etc.), Knative might help you. If you are facing cost pressures and operational burdens, Knative can ease your burden. Welcome interested students to communicate together.
The original link
This article is the original content of Aliyun and shall not be reproduced without permission.