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/cert-manager-istio-creating-issuer.adoc
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -16,11 +16,11 @@ Other supported issuers can be used, except for the ACME issuer, which is not su
16
16
.Procedure
17
17
18
18
. 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
+
----
24
24
25
25
. Create a YAML file that defines the `Issuer` and `Certificate` objects:
Copy file name to clipboardExpand all lines: modules/cert-manager-istio-csr-installing.adoc
+11-11Lines changed: 11 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -16,26 +16,26 @@ Use this procedure to install the Istio-CSR agent through {cert-manager-operator
16
16
+
17
17
[NOTE]
18
18
====
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
+
====
21
21
22
22
.Procedure
23
23
24
24
. 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.
25
25
+
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.
29
29
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.
32
32
* 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
+
====
35
35
36
36
.. Create a YAML file that defines the `IstioCSR` object:
37
37
+
38
-
.Example `IstioCSR` CR
38
+
.Example `IstioCSR` CR
39
39
[source,yaml]
40
40
----
41
41
apiVersion: operator.openshift.io/v1alpha1
@@ -53,7 +53,7 @@ spec:
53
53
istiodTLSConfig:
54
54
trustDomain: cluster.local
55
55
istio:
56
-
namespace: istio-system
56
+
namespace: <istio_project_name>
57
57
----
58
58
<1> Specify the `Issuer` or `ClusterIssuer` name. It should be the same name as the CA issuer defined in the `issuer.yaml` file.
59
59
<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