Skip to content

Commit 94b4db7

Browse files
committed
Fix inaccuracies in ingress dest CA cert docs
This commit fixes bug 2110059. https://bugzilla.redhat.com/show_bug.cgi?id=2110059 * modules/nw-ingress-creating-a-route-via-an-ingress.adoc: Change "oc `create`" to "`oc create`". * modules/nw-ingress-reencrypt-route-custom-cert.adoc: Change "an route" to "a route". Replace "certificate (CA)" with "destination CA certificate". State that the user *may* (not *must*) specify a certificate/key pair. Change "Annotations:" to "annotations:" in the example yaml.
1 parent 84702c5 commit 94b4db7

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

modules/nw-ingress-creating-a-route-via-an-ingress.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Some ecosystem components have an integration with Ingress resources but not wit
1010

1111
.Procedure
1212

13-
. Define an Ingress object in the {product-title} console or by entering the oc `create` command:
13+
. Define an Ingress object in the {product-title} console or by entering the `oc create` command:
1414
+
1515
.YAML Definition of an Ingress
1616
[source,yaml]

modules/nw-ingress-reencrypt-route-custom-cert.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,10 @@
66
[id="creating-re-encrypt-route-with-custom-certificate_{context}"]
77
= Creating a route using the destination CA certificate in the Ingress annotation
88

9-
The `route.openshift.io/destination-ca-certificate-secret` annotation can be used on an Ingress object to define an route with a custom certificate (CA).
9+
The `route.openshift.io/destination-ca-certificate-secret` annotation can be used on an Ingress object to define a route with a custom destination CA certificate.
1010

1111
.Prerequisites
12-
* You must have a certificate/key pair in PEM-encoded files, where the certificate is valid for the route host.
12+
* You may have a certificate/key pair in PEM-encoded files, where the certificate is valid for the route host.
1313
* You may have a separate CA certificate in a PEM-encoded file that completes the certificate chain.
1414
* You must have a separate destination CA certificate in a PEM-encoded file.
1515
* You must have a service that you want to expose.
@@ -42,7 +42,7 @@ apiVersion: route.openshift.io/v1
4242
kind: Route
4343
metadata:
4444
name: frontend
45-
Annotations:
45+
annotations:
4646
route.openshift.io/termination: reencrypt
4747
route.openshift.io/destination-ca-certificate-secret: secret-ca-cert
4848
spec:

0 commit comments

Comments
 (0)