You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
= Defining cluster size requirements for an {ServerlessProductName} installation
7
+
= Defining cluster size requirements
3
8
4
9
To install and use {ServerlessProductName}, the {product-title} cluster must be sized correctly.
5
10
@@ -9,3 +14,5 @@ The following requirements relate only to the pool of worker machines of the {pr
9
14
====
10
15
11
16
The total size requirements to run {ServerlessProductName} are dependent on the applications deployed. By default, each pod requests approximately 400m of CPU, so the minimum requirements are based on this value. Lowering the actual CPU request of applications can increase the number of possible replicas.
17
+
18
+
If you have high availability (HA) enabled on your cluster, this requires between 0.5 - 1.5 cores and between 200MB - 2GB of memory for each replica of the Knative Serving control plane.
After uninstalling the {ServerlessProductName}, the Operator and API custom resource definitions (CRDs) remain on the cluster.
9
-
You can use the following procedure to remove the remaining CRDs.
9
+
After uninstalling the {ServerlessProductName}, the Operator and API custom resource definitions (CRDs) remain on the cluster. You can use the following procedure to remove the remaining CRDs.
10
10
11
11
[IMPORTANT]
12
12
====
13
-
Removing the Operator and API CRDs also removes all resources that were defined using them, including Knative services.
13
+
Removing the Operator and API CRDs also removes all resources that were defined by using them, including Knative services.
14
14
====
15
15
16
16
.Prerequisites
17
17
18
-
* You uninstalled Knative Serving and removed the {ServerlessOperatorName}.
18
+
* You have access to an {product-title} account with cluster administrator access.
19
+
* You have uninstalled Knative Serving and removed the {ServerlessOperatorName}.
This procedure describes how to install and subscribe to the {ServerlessOperatorName} from the OperatorHub using the {product-title} web console.
9
+
This procedure describes how to install and subscribe to the {ServerlessOperatorName} from the OperatorHub by using the {product-title} web console.
9
10
10
-
[IMPORTANT]
11
-
====
12
-
Before upgrading to the latest Serverless release, you must remove the community Knative Eventing Operator if you have previously installed it. Having the Knative Eventing Operator installed prevents you from being able to install the latest version of Knative Eventing using the {ServerlessOperatorName}.
13
-
====
11
+
.Prerequisites
12
+
13
+
* You have access to an {product-title} account with cluster administrator access.
14
+
* You have logged into the {product-title} web console.
14
15
15
16
.Procedure
16
17
@@ -21,15 +22,21 @@ Before upgrading to the latest Serverless release, you must remove the community
21
22
. Review the information about the Operator and click *Install*.
22
23
23
24
. On the *Install Operator* page:
25
+
24
26
.. The *Installation Mode* is *All namespaces on the cluster (default)*. This mode installs the Operator in the default `openshift-serverless` namespace to watch and be made available to all namespaces in the cluster.
27
+
25
28
.. The *Installed Namespace* will be `openshift-serverless`.
29
+
26
30
.. Select the *stable* channel as the *Update Channel*. The *stable* channel will enable installation of the latest stable release of the {ServerlessOperatorName}.
31
+
27
32
.. Select *Automatic* or *Manual* approval strategy.
28
33
29
34
. Click *Install* to make the Operator available to the selected namespaces on this {product-title} cluster.
30
35
31
36
. From the *Catalog*->*Operator Management* page, you can monitor the {ServerlessOperatorName} subscription's installation and upgrade progress.
37
+
32
38
.. If you selected a *Manual* approval strategy, the subscription's upgrade status will remain *Upgrading* until you review and approve its install plan. After approving on the *Install Plan* page, the subscription upgrade status moves to *Up to date*.
39
+
33
40
.. If you selected an *Automatic* approval strategy, the upgrade status should resolve to *Up to date* without intervention.
0 commit comments