Skip to content

Commit f7ec929

Browse files
committed
[SRVKS-950] [SRVKE-1262]: Bug fixes
1 parent f1f020b commit f7ec929

File tree

2 files changed

+11
-5
lines changed

2 files changed

+11
-5
lines changed

modules/serverless-config-replicas-eventing.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
[id="serverless-config-replicas-eventing_{context}"]
77
= Configuring high availability replicas for Knative Eventing
88

9-
High availability (HA) is available by default for the Knative Eventing `eventing-controller`, `eventing-webhook`, `imc-controller`, `imc-dispatcher`, `mt-broker-controller`, and `sugar-controller` components, which are configured to have two replicas each by default. You can change the number of replicas for these components by modifying the `spec.high-availability.replicas` value in the `KnativeEventing` custom resource (CR).
9+
High availability (HA) is available by default for the Knative Eventing `eventing-controller`, `eventing-webhook`, `imc-controller`, `imc-dispatcher`, and `mt-broker-controller` components, which are configured to have two replicas each by default. You can change the number of replicas for these components by modifying the `spec.high-availability.replicas` value in the `KnativeEventing` custom resource (CR).
1010

1111
[NOTE]
1212
====

modules/serverless-ossm-setup.adoc

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,14 +19,20 @@ ifdef::openshift-dedicated,openshift-rosa[]
1919
endif::[]
2020

2121
* You have created a project or have access to a project with the appropriate roles and permissions to create applications and other workloads in {product-title}.
22-
* Install {SMProductName}. {ServerlessProductName} with {SMProductShortName} only is supported for use with {SMProductName} version 2.0.5 or later.
22+
23+
* Install the {SMProductName} Operator and create a `ServiceMeshControlPlane` resource in the `istio-system` namespace. If you want to use mTLS functionality, you must also set the `spec.security.dataPlane.mtls` field for the `ServiceMeshControlPlane` resource to `true`.
24+
+
25+
[IMPORTANT]
26+
====
27+
Using {ServerlessProductName} with {SMProductShortName} is only supported with {SMProductName} version 2.0.5 or later.
28+
====
29+
2330
* Install the {ServerlessOperatorName}.
31+
2432
* Install the OpenShift CLI (`oc`).
2533
2634
.Procedure
2735

28-
. Create a `ServiceMeshControlPlane` object in the `istio-system` namespace. If you want to use the mTLS functionality, this must be enabled for the `istio-system` namespace.
29-
3036
. Add the namespaces that you would like to integrate with {SMProductShortName} to the `ServiceMeshMemberRoll` object as members:
3137
+
3238
[source,yaml]
@@ -111,7 +117,7 @@ spec:
111117
port: 80
112118
targetPort: 8081
113119
----
114-
<1> Add the name of your wildcard certificate.
120+
<1> Add the name of the secret that contains the wildcard certificate.
115121
<2> The `knative-local-gateway` serves HTTP traffic. Using HTTP means that traffic coming from outside of {SMProductShortName}, but using an internal hostname, such as `example.default.svc.cluster.local`, is not encrypted. You can set up encryption for this path by creating another wildcard certificate and an additional gateway that uses a different `protocol` spec.
116122
+
117123
.Example `knative-local-gateway` object using HTTPS

0 commit comments

Comments
 (0)