Este contenido no está disponible en el idioma seleccionado.
Chapter 3. Knative Serving overview
Knative Serving helps developers create, deploy, and manage cloud-native applications. It provides Kubernetes custom resource definitions (CRDs) that define and control serverless workloads on an OpenShift Container Platform cluster. Developers use these CRDs to create custom resources (CRs) as building blocks for complex use cases such as rapidly deploying serverless containers or automatically scaling pods.
3.1. Knative Eventing use cases Copiar enlaceEnlace copiado en el portapapeles!
Knative Serving defines a set of resources that manage the lifecycle, configuration, and traffic routing of serverless applications on a Kubernetes cluster.
- Service
-
The
service.serving.knative.devcustom resource definition (CRD) manages the lifecycle of your workload and ensures that the application runs and remains reachable through the network. It creates a route, a configuration, and a new revision for each change to a user-created service, or custom resource. Developers interact with Knative primarily by modifying services. - Revision
-
The
revision.serving.knative.devcustom resource definition (CRD) represents a point-in-time snapshot of the code and configuration for each modification to the workload. Revisions are immutable objects and you can retain them, if needed. - Route
- The route.serving.knative.dev CRD maps a network endpoint to one or more revisions. You can manage the traffic in several ways, including fractional traffic and named routes.
- Configuration
- The configuration.serving.knative.dev CRD maintains the required state for your deployment. It provides a clean separation between code and configuration. Modifying a configuration creates a new revision.