openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 06:46:26 +01:00
Code Issues Releases Activity

Added note about limits on no of services and revisions

Browse Source
This commit is contained in:
abrennan
2020-04-28 12:12:19 -05:00
committed by openshift-cherrypick-robot
parent 0ed0cfbc4e
commit 6a29eb6ef6
1 changed files with 16 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
serverless/installing_serverless/installing-openshift-serverless.adoc
View File

@@ -22,24 +22,35 @@ The total size requirements to run {ServerlessProductName} are dependent on the
In the size requirement provided, an application can scale up to 10 replicas. Lowering the actual CPU request of applications can increase the number of possible replicas.
For more advanced use-cases such as logging, monitoring, or metering on {product-title}, you must deploy more resources. Recommended requirements for such use-cases are 24 CPUs and 96GB of memory.
You can use the MachineSet API to manually scale your cluster up to the desired size. The minimum requirements usually mean that you must scale up one of the default MachineSets by two additional machines.
For more information on using the MachineSet API, see the documentation on xref:../../machine_management/creating_machinesets/creating-machineset-aws.adoc#creating-machineset-aws[Creating MachineSets].
For more information on scaling a MachineSet manually, see the documentation on xref:../../machine_management/manually-scaling-machineset.adoc#manually-scaling-machineset[manually scaling MachineSets].
// Check requirements for HA and whether we need to up the requirements for memory etc.
[NOTE]
====
The requirements provided relate only to the pool of worker machines of the {product-title} cluster. Master nodes are not used for general scheduling and are omitted from the requirements.
====
[NOTE]
====
The following limitations apply to all {ServerlessProductName} deployments:
* Maximum number of Knative services: 1000
* Maximum number of Knative revisions: 1000
====
=== Additional requirements for advanced use-cases
For more advanced use-cases such as logging or metering on {product-title}, you must deploy more resources. Recommended requirements for such use-cases are 24 CPUs and 96GB of memory.
// If you have high availability (HA) enabled on your cluster, this requires between 0.5 - 1.5 cores and between 200m - 2GB of memory for each replica of the Knative Serving control plane.
// HA is enabled for some Knative Serving components by default. You can disable HA by following the documentation on xref:../../serverless-config-HA.adoc#serverless-config-HA[Configuring High Availability components].
include::modules/serverless-install-web-console.adoc[leveloffset=+1]
== Next steps
* After the {ServerlessOperatorName} is installed, you can install the Knative Serving component. See the documentation on xref:../installing_serverless/installing-knative-serving.adoc#installing-knative-serving[Installing Knative Serving].
// * Once the {ServerlessOperatorName} is installed, you can install the Knative Eventing component. See the documentation on xref:../installing-knative-eventing.adoc#installing-knative-eventing[Installing Knative Eventing].
// * After the {ServerlessOperatorName} is installed, you can install the Knative Eventing component. See the documentation on xref:../installing-knative-eventing.adoc#installing-knative-eventing[Installing Knative Eventing].