- Documentation
- Red Hat OpenShift Serverless
- Serving
- External and Ingress routing
- Routing overview history
OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
You are viewing documentation for a release that is no longer maintained. To view the documentation for the most recent version, see the latest Serverless docs.
- About Serverless
- Installing Serverless
- Preparing to install OpenShift Serverless
- Installing the Serverless Operator
- Installing the Knative CLI
- Installing Knative Serving
- Installing Knative Eventing
- Configuring Knative for Apache Kafka
- Configuring kube-rbac-proxy resources for Knative for Apache Kafka
- Configuring Serverless Functions
- Serverless upgrades
- Functions
- Getting started with functions
- Creating functions
- Running functions locally
- Deploying functions
- Building functions
- Listing existing functions
- Invoking functions
- Deleting functions
- Building and deploying functions on the cluster
- Connecting an event source to a function
- Functions development reference guide
- Configuring functions
- Serving
- Getting started with Knative Serving
- Autoscaling
- Configuring Serverless applications
- Traffic splitting
- External and Ingress routing
- Routing overview
- Customizing labels and annotations
- Configuring routes for Knative services
- Global HTTPS redirection
- URL scheme for external routes
- HTTPS redirection per service
- Cluster local availability
- Kourier Gateway service type
- Using HTTP2 and gRPC
- Using Serving with OpenShift ingress sharding
- Configuring access to Knative services
- Configuring kube-rbac-proxy resources for Serving
- Configuring burst and QPS for net-kourier
- Configuring custom domains for Knative services
- High availability configuration for Knative Serving
- Tuning serving configuration
- Eventing
- Knative CLI
- Observability
- Integrations
- Removing Serverless
×
Routing overview
Knative leverages OpenShift Container Platform TLS termination to provide routing for Knative services. When a Knative service is created, an OpenShift Container Platform route is automatically created for the service. This route is managed by the OpenShift Serverless Operator. The OpenShift Container Platform route exposes the Knative service through the same domain as the OpenShift Container Platform cluster.
You can disable Operator control of OpenShift Container Platform routing so that you can configure a Knative route to directly use your TLS certificates instead.
Knative routes can also be used alongside the OpenShift Container Platform route to provide additional fine-grained routing capabilities, such as traffic splitting.