Skip to content

Commit 4907272

Browse files
authored
Update best-practices-onboard-deploy.md
1 parent 7b265c6 commit 4907272

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

articles/operator-service-manager/best-practices-onboard-deploy.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Best practices for Azure Operator Service Manager
33
description: Understand best practices for Azure Operator Service Manager to onboard and deploy a network function (NF).
44
author: msftadam
55
ms.author: adamdor
6-
ms.date: 08/09/2024
6+
ms.date: 08/12/2024
77
ms.topic: best-practice
88
ms.service: azure-operator-service-manager
99
---
@@ -300,8 +300,9 @@ Any user trying to install cert-manager on the cluster, as part of a workload de
300300
### Other Configuration Changes to Consider
301301

302302
In addition to disabling the NfApp associated with the old user cert-manager, we have found other changes may be needed;
303-
1. If any other NfApps have DependsOn references to the old user cert-manager NfApp, these will need to be removed.
304-
2. If any other NfApps reference the old user cert-manager namespace value, this will need to be changed to the new azurehybridnetwork namespace value.
303+
1. If one NfApp contains both cert-manager and the CA installation, these must broken into two NfApps, so that the partner can disable cert-manager but enable CA installation.
304+
2. If any other NfApps have DependsOn references to the old user cert-manager NfApp, these will need to be removed.
305+
3. If any other NfApps reference the old user cert-manager namespace value, this will need to be changed to the new azurehybridnetwork namespace value.
305306

306307
### Cert-Manager Version Compatibility & Management
307308

0 commit comments

Comments
 (0)