1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-06 15:46:57 +01:00
Files
openshift-docs/modules/serverless-config-replicas.adoc
abrennan b919193344 Updating code blocks to guideline format for OPC 4.3
Conflicts:
	modules/serverless-creating-broker.adoc
	modules/serverless-rn-1-6-0.adoc
2020-09-02 12:38:26 -05:00

55 lines
2.1 KiB
Plaintext

// Module is included in the following assemblies:
//
// serverless/serverless-HA.adoc
[id="serverless-config-replicas_{context}"]
= Configuring high availability replicas on {ServerlessProductName}
High availability (HA) functionality is available by default on {ServerlessProductName} for the `autoscaler-hpa`, `controller`, `activator` , `kourier-control`, and `kourier-gateway` components. These components are configured with two replicas by default.
You modify the number of replicas that are created per controller by changing the configuration of `KnativeServing.spec.highAvailability` in the KnativeServing custom resource definition.
// This field also specifies the minimum number of _activators_ if you are using the Horizontal Pod Autoscaler (HPA). For more information about HPA, see
.Prerequisites
* An {product-title} account with cluster administrator access.
* Installed the {ServerlessOperatorName} and Knative Serving.
.Procedure
. In the {product-title} web console *Administrator* perspective, navigate to *OperatorHub* -> *Installed Operators*.
+
image::serving-installed-operator.png[Installed Operators page]
+
. Select the `knative-serving` namespace.
+
. Click *Knative Serving* in the list of *Provided APIs* for the {ServerlessOperatorName} to go to the *Knative Serving* tab.
+
image::serving-tab-created.png[Knative Serving tab]
+
. Click *knative-serving*, then go to the *YAML* tab in the *knative-serving* page.
+
image::serving-YAML-HA.png[Knative Serving YAML]
+
. Edit the custom resource definition YAML:
+
.Example YAML
+
[source,yaml]
----
spec:
high-availability:
replicas: 3
----
+
[IMPORTANT]
====
Do not modify any YAML contained inside the `config` field. Some of the configuration values in this field are injected by the {ServerlessOperatorName}, and modifying them will cause your deployment to become unsupported.
====
+
* The default `replicas` value is `2`.
* Changing the value to `1` will disable HA, or you can increase the number of replicas as required. The example configuration shown specifies a replica count of `3` for all HA controllers.