Knative Serving

    The Knative Serving project provides middleware components that enable:

    • Rapid deployment of serverless containers.
    • Autoscaling including scaling pods down to zero.
    • Support for multiple networking layers such as Ambassador, Contour, Kourier, Gloo, and Istio for integration into existing environments.
    • Point-in-time snapshots of deployed code and configurations.
    • Service: The resource automatically manages the whole lifecycle of your workload. It controls the creation of other objects to ensure that your app has a route, a configuration, and a new revision for each update of the service. Service can be defined to always route traffic to the latest revision or to a pinned revision.
    • : The route.serving.knative.dev resource maps a network endpoint to one or more revisions. You can manage the traffic in several ways, including fractional traffic and named routes.
    • Revision: The revision.serving.knative.dev resource is a point-in-time snapshot of the code and configuration for each modification made to the workload. Revisions are immutable objects and can be retained for as long as useful. Knative Serving Revisions can be automatically scaled up and down according to incoming traffic. See for more information.

    Getting Started

    With the Service resource, a deployed service will automatically have a matching route and configuration created. Each time the is updated, a new revision is created.

    Debugging Knative Serving issues

    Observability

    See the Knative Serving Issues page for a full list of known issues.