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: articles/azure-arc/kubernetes/tutorial-arc-enabled-open-service-mesh.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -134,13 +134,13 @@ To ensure that the privileged init container setting is not reverted to the defa
134
134
### Install OSM with cert-manager for Certificate Management
135
135
[cert-manager](https://cert-manager.io/) is a provider that can be used for issuing signed certificates to OSM without
136
136
the need for storing private keys in Kubernetes. Refer to OSM's [cert-manager documentation](https://release-v0-11.docs.openservicemesh.io/docs/guides/certificates/)
137
-
and [demo](https://docs.openservicemesh.io/docs/demos/cert-manager_integration/) to learn more. Values to configure cert-manager must be passed in during OSM installation using the Azure CLI.
138
-
137
+
and [demo](https://docs.openservicemesh.io/docs/demos/cert-manager_integration/) to learn more.
139
138
> [!NOTE]
140
139
> Use the commands provided in the OSM GitHub documentation with caution. Ensure that you use the correct namespace name `arc-osm-system`.
141
140
142
-
To set cert-manager as the certificate provider, create a JSON file with the following `certificateProvider.kind` value.
143
-
Include and update the subsequent `certmanager.issuer` lines if you would like to change from default values specified in OSM documentation.
141
+
To install OSM with cert-manager as the certificate provider, create a JSON file with the `certificateProvider.kind` value set to
142
+
cert-manager as shown below. If you would like to change from default cert-manager values specified in OSM documentation,
143
+
also include and update the subsequent `certmanager.issuer` lines.
144
144
145
145
```json
146
146
{
@@ -154,16 +154,15 @@ Include and update the subsequent `certmanager.issuer` lines if you would like t
154
154
[Now, install OSM with custom values](#setting-values-during-osm-installation).
155
155
156
156
### Install OSM with Contour for Ingress
157
-
OSM provides multiple options to expose mesh services externally using ingress. OSM has been tested with[Contour](https://projectcontour.io/), which
157
+
OSM provides multiple options to expose mesh services externally using ingress. OSM can use[Contour](https://projectcontour.io/), which
158
158
works with the ingress controller installed outside the mesh and provisioned with a certificate to participate in the mesh.
159
159
Refer to [OSM's ingress documentation](https://docs.openservicemesh.io/docs/guides/traffic_management/ingress/#1-using-contour-ingress-controller-and-gateway)
160
-
and [demo](https://docs.openservicemesh.io/docs/demos/ingress_contour/) to learn more. Values to configure
161
-
Contour must be passed in during OSM installation using the Azure CLI.
160
+
and [demo](https://docs.openservicemesh.io/docs/demos/ingress_contour/) to learn more.
162
161
163
162
> [!NOTE]
164
163
> Use the commands provided in the OSM GitHub documentation with caution. Ensure that you use the correct namespace name `arc-osm-system`.
165
164
166
-
To set required values for configuring Contour, create the following JSON file.
165
+
To set required values for configuring Contour during OSM installation, create the following JSON file:
0 commit comments