{"id":52709,"date":"2019-11-15T00:00:00","date_gmt":"2019-11-14T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/knative-platforma-kak-usluga-na-osnove-k8s-s-podderzhkoj-serverless"},"modified":"2020-02-18T14:00:30","modified_gmt":"2020-02-18T11:00:30","slug":"knative-platforma-kak-usluga-na-osnove-k8s-s-podderzhkoj-serverless","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/knative-platforma-kak-usluga-na-osnove-k8s-s-podderzhkoj-serverless","title":{"rendered":"Knative \u2013 Platform as a Service based on k8s with serverless support","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Knative<\/p>\n

<\/p>\n

Kubernetes has undoubtedly become the dominant platform for container deployment. It allows for management of virtually everything using its APIs and custom controllers that extend its API through custom resources.<\/p>\n

<\/p>\n

However, the user still needs to make detailed decisions about how to deploy, configure, manage, and scale applications. Questions concerning application scaling, security, and traffic management remain at the user's discretion. This is what distinguishes Kubernetes from typical \"platforms as a service\" (PaaS), such as Cloud Foundry and Heroku.<\/p>\n

<\/p>\n

These platforms feature a simplified user interface aimed at application developers, who often focus on configuring individual applications. Routing, deployment, and metrics are transparently managed by the underlying PaaS system.<\/p>\n

<\/a><\/noindex><\/p>\n

The workflow of \u2018source code to delivery\u2019 is handled by PaaS through the creation of a custom container image, its deployment, the setup of a new route, and a DNS subdomain for incoming traffic. All of this is triggered on command. git push<\/code>.<\/p>\n

<\/p>\n

In Kubernetes, only the basic building blocks are intentionally provided for such platforms, giving the community the opportunity to do this work themselves. As Kelsey Hightower said,<\/a><\/noindex>:<\/p>\n

<\/p>\n

Kubernetes is a platform for building platforms. The best starting point, but not the finish line.<\/p><\/blockquote>\n

As a result, we see a flurry of Kubernetes builds and hosting solutions attempting to create PaaS for Kubernetes, such as OpenShift and Rancher. Against the backdrop of a growing Kube-PaaS market, Knative entered the ring, created in July 2018 by Google and Pivotal.<\/p>\n

<\/p>\n

Knative emerged from a collaboration between Google and Pivotal, with some assistance from other companies like IBM, RedHat, and Solo.im. It offers similar PaaS capabilities for Kubernetes with top-notch support for serverless application deployment. Unlike Kubernetes builds, Knative is installed as an extension on any compatible Kubernetes cluster and is configured through custom resources.<\/p>\n

<\/p>\n

What is Knative?<\/h2>\n

<\/p>\n

Knative is described as \"A Kubernetes-based platform for deploying workloads and managing them using modern serverless computing.\" By declaring itself such a platform, Knative actively scales containers automatically in proportion to concurrent HTTP requests. Unused services eventually scale down to zero, providing on-demand scaling in a serverless computing style.<\/p>\n

<\/p>\n

Knative consists of a set of controllers that are installed in any Kubernetes cluster and provide the following capabilities:<\/p>\n

<\/p>\n