Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

Chapter 1. Preparing to install {ServerlessProductName}

Read the following information about supported configurations and prerequisites before you install OpenShift Serverless. The set of supported features, configurations, and integrations for OpenShift Serverless, current and past versions, are available at the Supported Configurations page.

For OpenShift Container Platform, you can install OpenShift Serverless in a restricted or disconnected network environment except for OpenShift Serverless Functions, but you cannot use it in a multitenant configuration on a single cluster.

1.1. Scalability and performance on OpenShift Container Platform
Copiar enlace

The cluster includes 3 main nodes and 3 worker nodes. Each node has 64 CPUs, 457 GB of memory, and 394 GB of storage. Testing showed the following time values for a simple Quarkus application:

  • The average scale-from-zero response time was about 3.4 seconds.
  • The maximum response time was 8 seconds.
  • The 99.9th percentile of response times was 4.5 seconds.

These times might vary depending on the application and the runtime of the application.

The maximum number of Knative services that can be created is 3,000. This corresponds to theOpenShift Container Platform Kubernetes services limit of 10,000, since 1 Knative service creates 3 Kubernetes services.

You can use the OpenShift Container Platform MachineSet API to manually scale your cluster up to the required size. The minimum requirements usually mean that you must scale up one of the default compute machine sets by two additional machines.

1.2. Defining cluster size requirements
Copiar enlace

You must size the cluster correctly to install and use OpenShift Serverless.

Note

The following requirements apply only to the worker node pool in the cluster. The system does not use control plane nodes for general scheduling and therefore excludes them from these requirements.

Note

The following section on defining cluster size requirements applies to these distributions:

  • OpenShift Container Platform
  • OpenShift Dedicated
  • Red Hat OpenShift Service on AWS

The minimum requirement to use OpenShift Serverless is a cluster with 10 CPUs and 40GB memory. By default, each pod requests about 400m of CPU, so the system calculates the minimum requirements based on this value.

The total size requirements for running OpenShift Serverless depend on the installed components and deployed applications, and can vary by deployment.

1.2.1. Additional requirements for advanced use-cases
Copiar enlace

For more advanced use-cases such as logging or metering on OpenShift Container Platform, you must deploy more resources. Recommended requirements for such use-cases are 24 CPUs and 96GB of memory.

If you enable high availability (HA) on your cluster, each Knative Serving control plane replica requires 0.5–1.5 CPU cores and 200 MB–2 GB of memory.

Some Knative Serving components enable HA by default. To disable HA, follow the documentation for Configuring high availability replicas.

Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2026 Red HatVolver arriba