404 Not Found
  • Introduction
  • Monitoring related
    • K8s cluster monitoring
    • Monitor Jenkins with G.A.P on K8s cluster
    • Monitoring tools | projects
      • Grafana
      • AlertManager
      • Prometheus
      • Wavefront
  • Logging related
    • BOSH logs
    • How to gather systemd log
    • K8s cluster logging
    • Logging tools | projects
      • vRealize Log Insight
      • Fluentd
      • syslog vs fluentd
  • Having fun with docker
    • Using docker-compose for redmine
    • Customize Fluentd docker image
  • K8S or Apache Mesos
  • K8S Related
    • Main Architecture
      • Master components
        • API Server
        • etcd
        • Controller Manager
        • Kube Scheduler
      • Worker components
        • kubelet
        • kube-proxy
    • K8S Storage
      • Volume Provisioning
      • Understand CSI
      • How to write CSI
      • VMware CNS
      • K8S storage e2e experiment under VMware vSphere
      • Experiment on Persistent Volume Access Mode
      • Design: Storage in Cluster-API architecture
    • K8S Networking
      • Ingress
      • Endpoints
    • K8S Policies
      • Resource Quotas
    • K8S Management Platform
    • K8S Tests Tool
    • K8S Extension
      • CRDs
        • Custom Resources
        • Custom Controllers
        • How to user code-generator
        • K8S Operators
        • Operators Development Tools
          • Kubebuilder
          • Metacontroller
          • Operator SDK
      • Custom API Server
    • K8S Resource CRUD Workflow
    • K8S Garbage Collection
  • K8S CONTROLLER RELATED
    • IsController: true
    • Controller clients
  • PKS RELATED
    • How to Access VMs and Databases related to PKS
    • PKS Basics
    • BOSH Director
    • Backup and Restore on Ent. PKS with Velero
  • CICD RELATED
    • Configure Jenkins to run on K8S
    • Customize Jenkins JNLP slave image
    • Jenkins global shared libs
  • Google Anthos
    • Google Anthos Day from KubeCon 2019 San Diego
    • Migrate for Anthos
    • Config Connector
  • SYSTEM DESIGN RELATED
    • Design Data Intensive Application - Notes
      • RSM
        • Reliability
        • Scalability
      • Data models and Query Languages
      • Storage and Retrieval
    • How Alibaba Ensure K8S Performance At Large Scale
  • Miscellaneous
    • Knative
    • Serverless
    • Service Mesh
    • gRPC
    • Local persistent volumes
    • ownerReferences in K8S
    • File(NAS) vs Block(SAN) vs Object storage
    • KubeVirt
    • Why K8S HA chooses 3 instead of 5..6..7 as the size of masters?
    • goroutine & go channel
    • How to make docker images smaller
Powered by GitBook
On this page
  • What is Knative?
  • What are the benefits of Knative?
  • What are the components of Knative?
  • What challenges does Knative solve?

Was this helpful?

  1. Miscellaneous

Knative

PreviousHow Alibaba Ensure K8S Performance At Large ScaleNextServerless

Last updated 5 years ago

Was this helpful?

What is Knative?

(pronounced kay-nay-tiv) is an community project which adds components for deploying, running, and managing , applications to .

What are the benefits of Knative?

With Knative, you create a service by packaging your code as a container image and handing it to the system. Your code only runs when it needs to, with Knative starting and stopping instances automatically. Resources aren’t consumed unless your code needs to do something. Operations costs can be reduced you can pay for cloud-based compute time as it’s needed instead of running and managing your own servers all the time.

What are the components of Knative?

  • Build - A flexible approach to building source code into containers.

    • Configurable and flexible approach to building source code into containers

    • Pluggable approach leveraging Dockerfiles or built templates

    • No cross-compiling or need for local build tools

    • Support for cached artifacts for faster builds

    • Allow your organization to utilize spare capacity for better resource usage

  • Serving - Enables rapid deployment and automatic scaling of containers through a request-driven model for serving workloads based on demand.

    • Higher level abstraction, easy to reason about the object model

    • Seamless autoscaling based on HTTP requests

    • Gradual rollouts for new revisions

    • Integrates networking and service mesh automatically

    • Pluggable: connect your own logging and monitoring platform

  • Eventing - An infrastructure for consuming and producing events to stimulate applications. Applications can be triggered by a variety of sources, such as events from your own applications, cloud services from multiple providers, Software-as-a-Service (SaaS) systems.

    • Universal subscription, delivery, and management of events

    • Build loosely coupled, event-driven systems with high-level objects

    • Declarative binding between event producers and event consuming services

    • Scalable from just a few events to live streams

    • Custom event pipelines to connect with your own existing systems

Knative is thinking to move Build out, so one might wonder why there are only Serving and Eventing from its official website.

What challenges does Knative solve?

Knative's benefits can help solve a variety of real-world challenges facing today's developers, including the following:

  • CI/CD set up: Continuous integration and deployment workflows are a linchpin of DevOps processes. Automated gating for software builds and deployments can reduce deployment times while increasing software quality. The problem is that these automated workflows can take time and expertise to set up, often involving many different products. Knative is a useful tool that can be used as part of a pipeline automation project to get DevOps teams up and running.

  • Easier customer rollouts: The problem with a fast release cadence is that developers end up testing software on their users. Rolling out new releases to the customer base can expose software issues that may affect business processes. Knative's configuration and routing system allow you to expose new container revisions to a subset of the user base, gradually increasing that audience over time and quickly rolling back to older versions should problems arise.

Knative consists of 3 primary components based on :

here
Knative
open source
serverless
cloud-native
Kubernetes
Home - Knative
Logo