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
Copy file name to clipboardExpand all lines: modules/serverless-ossm-enable-sidecar-injection-with-kourier.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ You can add the `sidecar.istio.io/inject="true"` annotation to a Knative service
13
13
Adding sidecar injection to pods in system namespaces, such as `knative-serving` and `knative-serving-ingress`, is not supported when Kourier is enabled.
14
14
15
15
ifdef::openshift-enterprise[]
16
-
If you require sidecar injection for pods in these namespaces, see the {ServerlessProductName} documentation on _Integrating {ProductShortName} with {ServerlessProductName} natively_.
16
+
If you require sidecar injection for pods in these namespaces, see the {ServerlessProductName} documentation on _Integrating {SMProductShortName} with {ServerlessProductName} natively_.
Copy file name to clipboardExpand all lines: modules/serverless-ossm-external-certs.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
[id="serverlesss-ossm-external-certs_{context}"]
7
7
= Creating a certificate to encrypt incoming external traffic
8
8
9
-
By default, the {ProductShortName} mTLS feature only secures traffic inside of the {ProductShortName} itself, between the ingress gateway and individual pods that have sidecars. To encrypt traffic as it flows into the {product-title} cluster, you must generate a certificate before you enable the {ServerlessProductName} and {ProductShortName} integration.
9
+
By default, the {SMProductShortName} mTLS feature only secures traffic inside of the {SMProductShortName} itself, between the ingress gateway and individual pods that have sidecars. To encrypt traffic as it flows into the {product-title} cluster, you must generate a certificate before you enable the {ServerlessProductName} and {SMProductShortName} integration.
This certificate is picked up by the gateways created when you integrate {ServerlessProductName} with {ProductShortName}, so that the ingress gateway serves traffic with this certificate.
64
+
This certificate is picked up by the gateways created when you integrate {ServerlessProductName} with {SMProductShortName}, so that the ingress gateway serves traffic with this certificate.
Copy file name to clipboardExpand all lines: modules/serverless-ossm-setup.adoc
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,9 @@
4
4
5
5
:_content-type: PROCEDURE
6
6
[id="serverless-ossm-setup_{context}"]
7
-
= Integrating {ProductShortName} with {ServerlessProductName}
7
+
= Integrating {SMProductShortName} with {ServerlessProductName}
8
8
9
-
You can integrate {ProductShortName} with {ServerlessProductName} without using Kourier by completing the following procedure.
9
+
You can integrate {SMProductShortName} with {ServerlessProductName} without using Kourier by completing the following procedure.
10
10
11
11
.Prerequisites
12
12
@@ -24,7 +24,7 @@ endif::[]
24
24
+
25
25
[IMPORTANT]
26
26
====
27
-
Do not install the Knative Serving component before completing the following procedures. There are additional steps required when creating the `KnativeServing` custom resource defintion (CRD) to integrate Knative Serving with {ProductShortName}, which are not covered in the general Knative Serving installation procedure of the _Administration guide_.
27
+
Do not install the Knative Serving component before completing the following procedures. There are additional steps required when creating the `KnativeServing` custom resource defintion (CRD) to integrate Knative Serving with {SMProductShortName}, which are not covered in the general Knative Serving installation procedure of the _Administration guide_.
28
28
====
29
29
* Install the OpenShift CLI (`oc`).
30
30
* 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}.
@@ -33,7 +33,7 @@ Do not install the Knative Serving component before completing the following pro
33
33
34
34
. 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.
35
35
36
-
. Add the namespaces that you would like to integrate with {ProductShortName} to the `ServiceMeshMemberRoll` object as members:
36
+
. Add the namespaces that you would like to integrate with {SMProductShortName} to the `ServiceMeshMemberRoll` object as members:
37
37
+
38
38
[source,yaml]
39
39
----
@@ -47,7 +47,7 @@ spec:
47
47
- knative-serving
48
48
- <namespace>
49
49
----
50
-
<1> A list of namespaces to be integrated with {ProductShortName}.
50
+
<1> A list of namespaces to be integrated with {SMProductShortName}.
51
51
+
52
52
[IMPORTANT]
53
53
====
@@ -61,7 +61,7 @@ This list of namespaces must include the `knative-serving` namespace.
61
61
$ oc apply -f <filename>
62
62
----
63
63
64
-
. Create the necessary gateways so that {ProductShortName} can accept traffic:
64
+
. Create the necessary gateways so that {SMProductShortName} can accept traffic:
65
65
+
66
66
.Example `knative-local-gateway` object using HTTP
67
67
[source,yaml]
@@ -118,7 +118,7 @@ spec:
118
118
targetPort: 8081
119
119
----
120
120
<1> Add the name of your wildcard certificate.
121
-
<2> The `knative-local-gateway` serves HTTP traffic. Using HTTP means that traffic coming from outside of {ProductShortName}, 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.
121
+
<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.
122
122
+
123
123
.Example `knative-local-gateway` object using HTTPS
124
124
[source,yaml]
@@ -206,7 +206,7 @@ spec:
206
206
----
207
207
<1> A namespace that is part of the Service Mesh member roll.
208
208
<2> Instructs Knative Serving to generate an {product-title} pass-through enabled route, so that the certificates you have generated are served through the ingress gateway directly.
209
-
<3> Injects {ProductShortName} sidecars into the Knative service pods.
209
+
<3> Injects {SMProductShortName} sidecars into the Knative service pods.
Copy file name to clipboardExpand all lines: serverless/admin_guide/serverless-ossm-setup.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ You must configure the wildcard certificate to match the domain of your {product
29
29
30
30
If you want to use any domain name, including those which are not subdomains of the default {product-title} cluster domain, you must set up domain mapping for those domains. For more information, see the {ServerlessProductName} documentation about xref:../../serverless/security/serverless-custom-domains.adoc#serverless-create-domain-mapping_serverless-custom-domains[Creating a custom domain mapping].
0 commit comments