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/operator-service-manager/helm-requirements.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,7 +109,7 @@ The following `NFDV request payload` shows an example of how a publisher can pro
109
109
### Other considerations with Legacy method
110
110
Publisher should consider the following recommendations when using the legacy method:
111
111
* Avoid references to external registry
112
-
*Performa manual validations
112
+
*Perform manual validations
113
113
* Ensure static image repository and tags
114
114
115
115
#### Avoid references to external registry
@@ -167,7 +167,7 @@ global:
167
167
```
168
168
169
169
> [!NOTE]
170
-
> *If registryPath is left blank in underlying helm package, site network service (SNS) deployment fails while trying to download image.
170
+
> If registryPath is left blank in underlying helm package, site network service (SNS) deployment fails while trying to download image.
171
171
172
172
### Using injectArtifactStoreDetails method
173
173
To enable injectArtifactStoreDetails, set the installOptions parameter in the NF resource roleOverrides section to true, as shown in the following example.
@@ -209,7 +209,7 @@ global:
209
209
```
210
210
211
211
> [!NOTE]
212
-
> *If registryPath is left blank in underlying helm package, SNS deployment fails while trying to download image.
212
+
> If registryPath is left blank in underlying helm package, SNS deployment fails while trying to download image.
213
213
214
214
For information on using cluster registry, see the [concept documentation](get-started-with-cluster-registry.md).
0 commit comments