Skip to content

Commit d185e05

Browse files
committed
OCPBUGS-57841 updated two istio modules
1 parent 53b0c51 commit d185e05

File tree

2 files changed

+20
-20
lines changed

2 files changed

+20
-20
lines changed

modules/cert-manager-istio-creating-issuer.adoc

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -16,11 +16,11 @@ Other supported issuers can be used, except for the ACME issuer, which is not su
1616
.Procedure
1717

1818
. Create a new project for installing Istio-CSR by running the following command. If you have an existing project for installing Istio-CSR, skip this step.
19-
+
20-
[source,terminal]
21-
----
22-
$ oc new-project <istio_csr_project_name>
23-
----
19+
+
20+
[source,terminal]
21+
----
22+
$ oc new-project <istio_csr_project_name>
23+
----
2424

2525
. Create a YAML file that defines the `Issuer` and `Certificate` objects:
2626
+
@@ -31,15 +31,15 @@ apiVersion: cert-manager.io/v1
3131
kind: Issuer <1>
3232
metadata:
3333
name: selfsigned
34-
namespace: <istio_csr_project_name> <2>
34+
namespace: <istio_project_name> <2>
3535
spec:
3636
selfSigned: {}
3737
---
3838
apiVersion: cert-manager.io/v1
3939
kind: Certificate
4040
metadata:
4141
name: istio-ca
42-
namespace: <istio_csr_project_name>
42+
namespace: <istio_project_name>
4343
spec:
4444
isCA: true
4545
duration: 87600h # 10 years
@@ -61,7 +61,7 @@ apiVersion: cert-manager.io/v1
6161
kind: Issuer <1>
6262
metadata:
6363
name: istio-ca
64-
namespace: <istio_csr_project_name> <2>
64+
namespace: <istio_project_name> <2>
6565
spec:
6666
ca:
6767
secretName: istio-ca
@@ -75,7 +75,7 @@ spec:
7575
+
7676
[source,terminal]
7777
----
78-
$ oc get issuer istio-ca -n <istio_csr_project_name>
78+
$ oc get issuer istio-ca -n <istio_project_name>
7979
----
8080
+
8181
.Example output

modules/cert-manager-istio-csr-installing.adoc

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -16,26 +16,26 @@ Use this procedure to install the Istio-CSR agent through {cert-manager-operator
1616
+
1717
[NOTE]
1818
====
19-
If you are using `Issuer` resource, create the `Issuer` and `Certificate` resources in the {SMProductName} or `Istiod` namespace. Certificate requests are generated in the same namespace, and role-based access control (RBAC) is configured accordingly.
20-
====
19+
If you are using `Issuer` resource, create the `Issuer` and `Certificate` resources in the {SMProductName} or `Istiod` namespace. Certificate requests are generated in the same namespace, and role-based access control (RBAC) is configured accordingly.
20+
====
2121
2222
.Procedure
2323

2424
. Create the `IstioCSR` custom resource to enable Istio-CSR agent managed by the {cert-manager-operator} for processing Istio workload and control plane certificate signing requests.
2525
+
26-
[NOTE]
27-
====
28-
Only one `IstioCSR` custom resource (CR) is supported at a time. If multiple `IstioCSR` CRs are created, only one will be active. Use the `status` sub-resource of `IstioCSR` to check if a resource is unprocessed.
26+
[NOTE]
27+
====
28+
Only one `IstioCSR` custom resource (CR) is supported at a time. If multiple `IstioCSR` CRs are created, only one will be active. Use the `status` sub-resource of `IstioCSR` to check if a resource is unprocessed.
2929

30-
* If multiple `IstioCSR` CRs are created simultaneously, none will be processed.
31-
* If multiple `IstioCSR` CRs are created sequentially, only the first one will be processed.
30+
* If multiple `IstioCSR` CRs are created simultaneously, none will be processed.
31+
* If multiple `IstioCSR` CRs are created sequentially, only the first one will be processed.
3232
* To prevent new requests from being rejected, delete any unprocessed `IstioCSR` CRs.
33-
* The Operator does not automatically remove objects created for `IstioCSR`. If an active `IstioCSR` resource is deleted and a new one is created in a different namespace without removing the previous deployments, multiple `istio-csr` deployments may remain active. This behavior is not recommended and is not supported.
34-
====
33+
* The Operator does not automatically remove objects created for `IstioCSR`. If an active `IstioCSR` resource is deleted and a new one is created in a different namespace without removing the previous deployments, multiple `istio-csr` deployments may remain active. This behavior is not recommended and is not supported.
34+
====
3535
3636
.. Create a YAML file that defines the `IstioCSR` object:
3737
+
38-
.Example `IstioCSR` CR
38+
.Example `IstioCSR` CR
3939
[source,yaml]
4040
----
4141
apiVersion: operator.openshift.io/v1alpha1
@@ -53,7 +53,7 @@ spec:
5353
istiodTLSConfig:
5454
trustDomain: cluster.local
5555
istio:
56-
namespace: istio-system
56+
namespace: <istio_project_name>
5757
----
5858
<1> Specify the `Issuer` or `ClusterIssuer` name. It should be the same name as the CA issuer defined in the `issuer.yaml` file.
5959
<2> Specify the `Issuer` or `ClusterIssuer` kind. It should be the same kind as the CA issuer defined in the `issuer.yaml` file.

0 commit comments

Comments
 (0)